SQl Services not starting after installing CU3 on SQL 2025

Question

SQl Services not starting after installing CU3 on SQL 2025

Abhishek Gaddam 0

I have installed SQL Pacth on Failover cluster instance for SQL 2025.
After installing , SQL Services are not coming up.

Error
Error message -

Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 200, state 4, severity 25. 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 errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion. For more information, see https://go.microsoft.com/fwlink/?linkid=2322071.

Deepesh Dhake 1,165 Reputation points

2026-08-26T14:11:58.0666667+00:00

Can you provide the error log?

\MSSQL\Log\ERRORLOG
Abhishek Gaddam 0 Reputation points

2026-08-26T14:13:39.2066667+00:00

Database 'master' is upgrading script 'ISServer_upgrade.sql' from level 0 to level 500. 2026-08-26 02:11:27.67 spid27s --------------------------------------------- 2026-08-26 02:11:27.67 spid27s Starting execution of ISServer_upgrade.SQL 2026-08-26 02:11:27.67 spid27s --------------------------------------------- 2026-08-26 02:11:27.67 spid27s 2026-08-26 02:11:27.67 spid27s Taking SSISDB to single user mode 2026-08-26 02:11:27.67 spid27s Setting database option SINGLE_USER to ON for database 'SSISDB'. 2026-08-26 02:11:27.99 spid27s CREATE NONCLUSTERED INDEX [index_tasks_ReadyForDispatchTime] ON [internal].[tasks] ([ReadyForDispatchTime] ASC) INCLUDE ([CreatedTime], [CreateWorkerAgentId], [ExecutedCount], [ExpiredTime], [InputData], [IsCritical], [JobId], [LastUpdatedTime], [MaxExecutedCount], [Priority], [Status], [TaskType]) WITH (ONLINE = ON) 2026-08-26 02:11:28.04 spid27s CREATE NONCLUSTERED INDEX [index_tasks_Status] ON [internal].[tasks] ([Status]) INCLUDE ([ExecutedCount], [ExpiredTime], [IsCancelled], [MaxExecutedCount], [WorkerAgentId]) WITH (ONLINE = ON) 2026-08-26 02:11:28.12 spid27s Error: 208, Severity: 16, State: 1. 2026-08-26 02:11:28.12 spid27s Invalid object name 'internal.operation_os_sys_info'. 2026-08-26 02:11:28.12 spid27s Error: 912, Severity: 21, State: 2. 2026-08-26 02:11:28.12 spid27s Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 200, state 4, severity 25. 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 errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion. For more information, see https://go.microsoft.com/fwlink/?linkid=2322071. 2026-08-26 02:11:28.12 spid27s Error: 3417, Severity: 21, State: 3. 2026-08-26 02:11:28.12 spid27s 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, see https://go.microsoft.com/fwlink/?linkid=2322220. 2026-08-26 02:11:28.12 spid27s SQL Server shutdown has been initiated with exit code 17. 2026-08-26 02:11:28.12 spid27s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required

1 answer

Your answer

Deepesh Dhake 1,165 Reputation points

2026-08-26T14:11:58.0666667+00:00

Can you provide the error log?

\MSSQL\Log\ERRORLOG

Answer 1

Deepesh Dhake 1,165

Cause: The patch's ISServer_upgrade.sql referenced internal.operation_os_sys_info in your SSISDB and it's missing - your SSISDB schema is out of step with what the SQL 2025 script expects. Not the login (15151) case.

Fix:

If SSISDB is not used here:

Add -T902 to startup params (bring SQL up without the FCI restarting it mid-repair).

Drop SSISDB.

Remove -T902, restart normally.

If SSISDB is used:

Start with -T902.

Back up SSISDB + confirm you have the catalog master key password.

Run the SSIS Catalog Upgrade Wizard against the instance.

If that can't fix it, drop/recreate the catalog and redeploy from source. Then remove -T902, restart.

Abhishek Gaddam 0 Reputation points

2026-08-26T14:35:34.23+00:00

TITLE: SQL Server Integration Services

Cannot find the user 'ModuleSigner', because it does not exist or you do not have permission. (Microsoft.SqlServer.IntegrationServices.ISServerDBUpgrade)

BUTTONS:

OK
Deepesh Dhake 1,165 Reputation points

2026-08-26T15:01:39.6533333+00:00
You may try following:

Start SQL under -T902 (without the FCI restarting it mid-repair).

In SSMS then SSISDB, recreate the missing user(s):

USE [SSISDB]; GO CREATE USER [ModuleSigner] FOR CERTIFICATE [MS_SQLISSigningCertificate]; GO CREATE USER [##MS_SSISServerCleanupJobUser##] FOR LOGIN [##MS_SSISServerCleanupJobLogin##]; GO

Remove -T902, restart normally - ISServer_upgrade.sql completes.

Before step 2, confirm the cert exists: SELECT name FROM sys.certificates WHERE name = 'MS_SQLISSigningCertificate'; if it's also missing, this won't work (catalog rebuild / support case instead). Back up SSISDB while under -T902.