This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(240, 99%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Hello, I have 9 separate SQL 2019 instances all on their own stand alone servers, 5 production, 4 Development, 1 of the 9 had this issue. While trying to apply CU 13 (SQLServer2019-KB5005679-x64.exe) the installation crashed and SQL would not start afterwards. Below is the error in the error log.
2021-12-10 08:22:44.35 spid13s Could not find stored procedure 'sys.sp_MSIsContainedAGSession'.
2021-12-10 08:22:44.35 spid13s Error: 912, Severity: 21, State: 2.
2021-12-10 08:22:44.35 spid13s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 2812, state 62, 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.
Steps I have already taken:
I started SQL from command line (NET START MSSQL$SQL01 /T902), and verified indeed 'sys.sp_MSIsContainedAGSession' does not exist in MSDB. I can see it in all my other instances, so I have the code, however I can not apply a sys schema stored proc to add it to the instance where it is missing. I ran the 'msdb110_upgrade.sql' manually after starting at the command line and confirmed the error.
Any workaround for this? I can't backout the CU because the OS doesn't think its installed, but if I try to re-run it it won't let me because it shows SQL is already upgraded, which it is, the version number is upgraded when I launched from command line.
Additional SQL Server features and topics not covered by specific categories
Hi @Mantini, Ronald M ,
Did you have the latest backup of MSDB?
Please try to start SQL server with trace flag 902, restore the latest MSDB backup, then stop SQL Service and start normally (without any trace flag)
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Hi..I tried that earlier but because the DB version is actually upgraded, it fails because the backup is from the previous version. I did find a solution..running a repair from the original installation hardware fixed the issue. MSFT recommended it.
I thought I had seen this before, so I went to Google. I did find https://www.sqlservercentral.com/forums/topic/missing-sys-sp_msiscontainedagsession-causing-failure-in-cu13-update-script, but I don't think was what I had in mind. Nevertheless, that poster was able to resolve the problem by uninstalling and re-installing.
I don't think this SP is in msdb, but I would expect it to be in the resource database. It could be that the install did not properly replace the resource database, and this instance was on a CU level that did not have an SP. (Something in the back of my mind tells me that this SP was added in a CU after the initial release of SQL 2019.)
Hi Erland, thanks for your reply, the SP is indeed in msdb, I can see it on my other nodes, all 8 ran this update no problem and the sproc is still there. However I can't apply it in the missing msdb unless you know a trick as its in the sys schema and we don't have access. We tried a workaround where we created the sp in dbo schema and edited the msdb110_upgrade.sql script to reference the dbo version but it didn't work, it kept complaining about the missing sproc from the sys schema even after we removed that reference to that version, pretty strange.
I found that link you posted too, his problem is my exact problem same CU and everything. It says they un-installed the CU..problem is the CU never successfully installed in my case, so its not listed as an option to un-install at the OS level. However the SQL engine did get updated to the new version, so if I re-launch the CU update it says there is nothing to do. So the OS thinks nothing is installed, but the CU installer thinks its done, bit of a pickle.
No, the SP is in the resource database. It may seem to be in msdb if you look there. But if you look for it in a user database, it will appear to be there as well.
I'm not sure how they were able to revert the CU, because they should have gotten stuck as the same place as you. But you could try taking mssqlsystemresource.mdf and .ldf from one of your instances and stick into this one. Note that these files are in the BINN folder. Make sure that you don't overwrite the existing files, in case the plot does not work out!
ahh I see what you mean now...I wondered as initially I looked for it by querying sysobjects and couldn't find it, but found it browsing. Got it.
I only found the 'msdb110_upgrade.sql' file here (C:\Program Files\Microsoft SQL Server\MSSQL15.SQL01\MSSQL\Install), don't see it in BINN. I saved a copy before playing with it. Thanks again for poking around on this, I'm talking to MSFT too no solution yet.
Yeah, the upgrade script is in the Install folder. I was talking about the resource database, which is in BINN. It is in BINN, because while it is a database, it is essentially the same thing as a DLL.
Opening a support case and get advice which by definition is supported that way is certainly better than trying untested ideas you get from a forum.
Erland, late Friday MSFT got back to me and recommended I run 'repair' from the Installation Center, and that fixed it. In fact it seems to have completed the CU update, I can see it listed in installed updates afterwards. Didn't occur to me to try this earlier I didn't realize the repair would work on CU's too. Thanks for your help-Ron
ok one last note..I can't see it in the 'installed updates' section under Control Panel, I was looking at the wrong node. So everything is working, SQL is starting but the CU13 is not listed as applied, although the SQL Version is at the updated level
I'm glad to hear that you got is sorted out!
I wasn't aware of that Repair applied to half-way installed CUs either, good to know!