大网数据广告活动
数据库与应用安全

SQL Server upgrade fails and returns error 6528

· 52CE 我爱测

Troubleshoots error 6528 that occurs when you install a cumulative update or service pack for SQL Server. The error occurs when database upgrade scripts are run.

This article helps you troubleshoot and solve error 6528 that occurs when you install a cumulative update (CU) or service pack (SP) for Microsoft SQL Server. The error occurs when database upgrade scripts are run.

Symptoms

When you apply a CU or an SP for SQL Server, you notice that the Setup program reports one of the following error messages in the SQL Server error log:

SQL server failed in 'Script level upgrade' with the following error:
Error: 50000, Severity: 16, State: 127.
Cannot drop the assembly 'ISSERVER', because it does not exist or you do not have permission.
Error: 50000, Severity: 16, State: 127.
Cannot drop the assembly 'ISSERVER', because it does not exist or you do not have permission.

Creating function internal.is_valid_name
Error: 6528, Severity: 16, State: 1.
Assembly 'ISSERVER' was not found in the SQL catalog of database 'SSISDB'.

Error: 912, Severity: 21, State: 2.
Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 6528, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous error log entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
Error: 3417, Severity: 21, State: 3.
Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
SQL Server shutdown has been initiated.

Cause

This issue may occur because the SQL Server instance where you try to apply a CU or an SP is missing assembly ISSERVER.

For more information about database upgrade scripts that run during a CU or an SP installation, see Troubleshoot upgrade script failures when applying an update.

Resolution

Follow these steps to solve the issue:

  1. Start SQL Server with trace flag 902.

  2. Check if the assembly ISSERVER is in the database SSISDB by using the following query:

    Use SSISDB
    GO
    SELECT * FROM sys.assemblies WHERE name = 'ISSERVER'
    

    Or, you can check it by expanding Databases > SSISDB > Programmability > Assemblies > ISSERVER in SQL Server Management Studio (SSMS).

  3. Check the location C:\Program Files\Microsoft SQL Server\<VersionNumber>\DTS\Bin to see if the assembly Microsoft.SqlServer.IntegrationServices.Server.dll is present in the SQL binary folder.

  4. If the assembly is in that folder but missing as an entry in the sys.assemblies view, re-create it by using the following query:

    DECLARE @asm_bin varbinary(max);
    SELECT @asm_bin = BulkColumn
    FROM OPENROWSET (BULK N'C:\Program Files\Microsoft SQL Server\<VersionNumber>\DTS\Binn\Microsoft.SqlServer.IntegrationServices.Server.dll',SINGLE_BLOB) AS dll
    CREATE ASSEMBLY ISSERVER FROM  @asm_bin  WITH PERMISSION_SET = UNSAFE
    ALTER DATABASE SSISDB SET TRUSTWORTHY ON
    

    This time the assembly ISSERVER is present.

  5. Remove trace flag 902 and start the services.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors (upstream author metadata: prmadhes-msft). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 08/11/2023
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。