January 14, 2020 at 11:42 am
Hi
rolling out the latest CU has stopped a SQL 2016 server from starting.
The following was logged in the event log
Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 574, state 0, 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.
I started SQL with the -T902 flag and manually ran the msdb110_upgrade.sql script. It failed with the following errors
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 574, Level 16, State 0, Procedure #sp_enable_component_________0000027F, Line 11 [Batch Start Line 64771]
CONFIG statement cannot be used inside a user transaction.
Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
Msg 574, Level 16, State 0, Procedure #sp_enable_component________0000027F, Line 13 [Batch Start Line 64771]
CONFIG statement cannot be used inside a user transaction.
Executing msdb.dbo.sp_syspolicy_create_purge_job
Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
Msg 574, Level 16, State 0, Procedure #sp_restore_component_state____0000027F, Line 9 [Batch Start Line 64771]
CONFIG statement cannot be used inside a user transaction.
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 574, Level 16, State 0, Procedure #sp_restore_component_state___0000027F, Line 11 [Batch Start Line 64771]
CONFIG statement cannot be used inside a user transaction.
post_dc100::Enabling Agent XPs before restoring data collector original state
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 574, Level 16, State 0, Procedure #sp_enable_component______0000027F, Line 11 [Batch Start Line 65039]
CONFIG statement cannot be used inside a user transaction.
Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
Msg 574, Level 16, State 0, Procedure #sp_enable_component____0000027F, Line 13 [Batch Start Line 65039]
CONFIG statement cannot be used inside a user transaction.
I have run EXEC sp_change_users_login 'Report' but can;t find any orphaned accounts.
I've googled the error and read and tried solution from thee articles
http://timwappat.info/post/2019/02/15/SQLUpgradeFailMsdb110_upgradesql
Any more ideas?
Alex
January 14, 2020 at 6:58 pm
Hello,
At the end of the article you posted from Microsoft he wrote to enable a trace flag to dig deeper into the issue, have you tried that?
If none of the above resolves the issue then you can use Trace flag -T3601 which causes the first 512 characters of each batch being executed to be printed to the error log. Identify the batch which is failling and troubleshoot the batch.
regards,
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply