Error patching SQL server 2019 with KB5040948 and not able to uninstall

Question

2024-10-20 14:23:40.94 spid17s Error: 912, Severity: 21, State: 2.

2024-10-20 14:23:40.94 spid17s Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 3602, state 251, 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.

2024-10-20 14:23:40.95 spid17s Error: 3417, Severity: 21, State: 3.

2024-10-20 14:23:40.95 spid17s 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.

2024-10-20 14:23:40.95 spid17s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Answer 1

Hi @Ung Seyha ,

Thank you for your reaching out and welcome to Microsoft Q&A!

The error may be encountered during an upgrade of SQL Server to a Cumulative Update or Service Pack. The upgrade scripts may fail due to an underlying issue and may cause the master database to not recover. Again the underlying cause is to be found in the latest SQL Server error log prior to this message.You could try the steps below:

• Restore backup of the master database. Or rebuild the system databases followed by attaching or restoring the remaining databases (msdb, user databases, SSISDB, etc.)
• If you see this error during an upgrade failure, refer to Troubleshoot common SQL Server Cumulative Update installation issues and error 912 - MSSQLSERVER_912.

In addition, this is the latest Cumulative Update KB5406060.

Best regards,

Lucy Chen

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

https://docs.microsoft.com/en-us/answers/support/email-notifications

Answer 2

Disabling sync is not enough. I believe you need to take SSISDB out of the AG, see https://techcommunity.microsoft.com/t5/sql-server-integration-services/ssis-with-alwayson/ba-p/388091.

Also, that GDR is a tad old now. I would suggest that you install KB5406060. The procedure with SSISDB would be the same.