A msdb upgrade error can stop the service at the last upgrade step. The post reads the ERRORLOG, shows a read-only owner check, and walks through the four steps that fix the owner of msdb. The fix is one ALTER AUTHORIZATION statement.
SQL SERVER – Fix Error – Login failed for user. Reason: Server is in script upgrade mode. Only administrator can connect at this time. (Microsoft SQL Server, Error: 18401)
I recently had a very simple and interesting error received while I was performing an upgrade mode with Docker and Persistence Storage for my upcoming workshop.
Listing Databases Below the Server’s Native Compatibility Level
Find databases below the native compatibility level, generate reviewable ALTER statements, and prepare Query Store checks safely.
SQL SERVER – Script Level Upgrade for Database ‘master’ Failed Because Upgrade Step ‘msdb110_upgrade.sql’ Encountered Error 8649, State 1, Severity 17
Patching SQL 2017 failed at msdb110_upgrade.sql with error 8649: the query cost exceeded the configured threshold. Here is the cause and the fix.
SQL SERVER – Cannot Drop the Assembly ‘ISSERVER’, Because it Does not Exist or You do not Have Permission
An upgrade could not start SQL Server: Cannot drop the assembly ‘ISSERVER’, because it does not exist or you do not have permission. Here is another way to fix it.
SQL SERVER – Script level upgrade for database ‘master’ failed because upgrade step msdb110_upgrade.sql encountered error 926, state 1, severity 25
An upgrade failed: Script level upgrade for database ‘master’ failed because upgrade step msdb110_upgrade.sql encountered error 926. I explain the cause and the fix.
SQL SERVER – Upgrade Blocked: The Specified Edition Upgrade is Not Supported
Upgrading SQL Server 2008 R2 Express to SQL Server 2012 Evaluation failed with: Upgrade Blocked: The specified edition upgrade is not supported. Let me explain why.