Sqlserver services failed to start after applying patch KB5040948

Avyayah 1,271

Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 15151, 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 errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.

We have started the database with T902 flag and used this article: https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/install/windows/sql-server-upgrade-failed-error-15151

Open SQL Server Configuration Manager.

· In SQL Server Configuration Manager, click SQL Server Services.

· Double-click the SQL Server service.

· In the SQL Server Properties dialog box, click the Advanced tab.

· On click the Advanced tab, locate the Startup Parameters item.

· Add ;-T902 to the end of the existing string value, and then click OK.

· Restart the SQL server service

Did anyone else have this similar issue? Is this the parameter added to the end of of the startup parameter: ;-T902

MikeyQiaoMSFT-0444 2,630 Reputation points

2024-08-20T02:49:36.85+00:00

Hi，Avyayah

We have not received a response from you. Did the reply could help you? If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.

2 answers

Erland Sommarskog 109.8K Reputation points MVP

2024-08-17T09:02:50.46+00:00

First of all, have you checked the SQL Server error to see why the upgrade script failed? You refer to a specific article, but there are many reasons why that script can fail.

As for applying the trace flag, the description you give appears to be outdated. In modern versions of SQL Server Configuration Manager there is a tab Startup Parameter, and you would add the parameter as in this example:

But observe that 902 is nothing you should keep enabled. You would only apply it so that you can repair whatever that caused the script to fail.
Please sign in to rate this answer.
Avyayah 1,271 Reputation points

2024-08-18T12:38:28.11+00:00

This is the error we got after applying patch KB5040948, and this patch failed to install as well

Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 15151, 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 errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.

Erland Sommarskog 109.8K Reputation points MVP

2024-08-18T13:14:47.5366667+00:00

Some notes on forum behaviour: I posted a comment that included a question. You answered by posting an Answer. However, Answers are for answers to the original question. You would only post Answer if you find the solution yourself.

Next, your answer only repeats what you said in the original post. I asked if you had looked in the SQL Server errorlog. So that task remains: look in the SQL Server errorlog to find out more exactly why that script failed. If you are not prepared to make any effort yourself, your chances to get help are small.

I observe now that this is the upgrade script for SSISDB that I'm not well acquainted with, since I don't use SSIS. (There is another, more general, upgrade script that they also run which does all sorts of ugly tings.) Nevertheless, I think a look in the SQL Server errorlog is necessary.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
MikeyQiaoMSFT-0444 2,630 Reputation points

2024-08-19T02:14:21.74+00:00

Hi，Avyayah

By checking the error, you can obtain more detailed information. Most of the time, the cause of this issue is missing SQL login and connect to hte SSISD.

If you don’t create SSISDB locally (you attach by migration), the SQL login will missing.

Steps to resolve the Script Upgrade error:

•Apply trace flag /T902 and start the SQL Server Services

•Create the [##MS_SSISServerCleanupJobLogin##] login

•Stop the SQL Services and remove the /T902 trace flag

•Start the SQL services normally using Configuration Manager

•The SSIS upgrade script completes successfully

Refered to

https://blog.sqlauthority.com/2019/04/06/sql-server-script-level-upgrade-for-database-master-failed-because-upgrade-step-ssis_hotfix_install-sql-encountered-error-15151/

https://www.sqlservice.se/script-level-upgrade-for-database-master-failed/

Regards

Mikey Qiao

If you're satisfied with the answer, don't forget to "Accept it," as this will help others who have similar questions to yours.
Please sign in to rate this answer.
Avyayah 1,271 Reputation points

2024-08-19T19:24:41.1133333+00:00

Since we got this error message: Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 15151, 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 errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.

We were able to resolve using the following steps:

https://learn.microsoft.com/en-us/answers/questions/1879762/sqlserver-services-failed-to-start-after-applying?page=1#answer-1671071

But I really wanted to know is that we have 70 database server and applying this solution to 70 server is not an option. So how can we successfully apply this patch to the database server KB5040948 without issues. or did Microsoft came up with a fix to this patch.

Erland Sommarskog 109.8K Reputation points MVP

2024-08-19T20:06:04.6833333+00:00

How did you conclude that the issue is related to the patch? I would suspect that the case that it's rather was an anomaly on that particular instance.

But if you think that the patch is really broken and you need a fix, there is only one way to go and that is to open a support case. If it is indeed a bug, the support case will be at no cost for you.

By the way, do all these 70 instances have a SSISDB?

Avyayah 1,271 Reputation points

2024-08-19T21:36:32.6533333+00:00

Not all 70 instances have SSISDB and the issue was found after patching the server.

Erland Sommarskog 109.8K Reputation points MVP

2024-08-19T21:39:34.2333333+00:00

So those without SSISDB should not be a problem. For those that have SSISDB, as I've said before check the SQL Server errorlog to see what the error was, and the check a couple of the others to see if they have the same problem.

Avyayah 1,271 Reputation points

2024-08-20T14:30:54.6366667+00:00

How does SSISDB get added to 2019 sqlserver. Microsoft SQL Server 2019 (RTM-CU26) (KB5035123) - 15.0.4365.2 (X64) Mar 29 2024 23:02:47 Copyright (C) 2019 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor) - current server is this version

other 2019 instance: Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) Sep 24 2019 13:48:23 Copyright (C) 2019 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor)

Avyayah 1,271 Reputation points

2024-08-20T14:38:36.0933333+00:00

Do we need to upgrade to https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2019/cumulativeupdate28 to prevent 'ISServer_upgrade.sql' encountered error 15151

Erland Sommarskog 109.8K Reputation points MVP

2024-08-20T21:03:28.4833333+00:00

SSISDB gets added to the instance because you do something in SQL Server Integration Services. Exactly what action I don't know, since I don't use SSIS myself. But it is certainly not added by the patch as such.

Do we need to upgrade to https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2019/cumulativeupdate28 to prevent 'ISServer_upgrade.sql' encountered error 15151

You need to check the SQL Server errorlog to see more exactly why got error 15151. The text of this message is: *Cannot %S_MSG the %S_MSG '%.ls', because it does not exist or you do not have permission. So it seems that the upgrade script is attempting an operation on an object which it assumes to be there, but which is not.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Sqlserver services failed to start after applying patch KB5040948

2 answers

Your answer