Joby Mathew

My feedback

  1. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Joby Mathew commented  · 

    We encountered the error while do the CU#4 on SQL server 2016 SP2 Cluster instance. After CU#4 patch the Instance could not start.
    The transactional replication also enabled the instance.
    The error logged in the logs are,

    2018-12-18 04:36:55.620 Server Software Usage Metrics is enabled.
    2018-12-18 04:36:56.040 spid6s Attempting to copy article resolvers from SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL13.SQL1\Replication\ArticleResolver
    2018-12-18 04:36:59.570 spid6s The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).
    2018-12-18 04:36:59.570 spid6s Error executing sp_vupgrade_replication.
    2018-12-18 04:36:59.570 spid6s Saving upgrade script status to 'SOFTWARE\Microsoft\MSSQLServer\Replication\Setup'.
    2018-12-18 04:36:59.570 spid6s Saved upgrade script status successfully.
    2018-12-18 04:36:59.570 spid6s Database 'master' is upgrading script 'upgrade_ucp_cmdw_discovery.sql' from level 218108834 to level 218109041.
    2018-12-18 04:36:59.800 spid6s Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 218108834 to level 218109041.
    2018-12-18 04:36:59.800 spid6s ----------------------------------
    2018-12-18 04:36:59.800 spid6s Starting execution of PRE_MSDB.SQL
    2018-12-18 04:36:59.800 spid6s ----------------------------------
    2018-12-18 04:36:59.890 spid6s Error: 15002, Severity: 16, State: 1.
    2018-12-18 04:36:59.890 spid6s The procedure 'sys.sp_dbcmptlevel' cannot be executed within a transaction.
    2018-12-18 04:36:59.890 spid6s -----------------------------------------
    2018-12-18 04:36:59.890 spid6s Starting execution of PRE_SQLAGENT100.SQL
    2018-12-18 04:36:59.890 spid6s -----------------------------------------
    2018-12-18 04:36:59.900 spid6s Error: 226, Severity: 16, State: 6.
    2018-12-18 04:36:59.900 spid6s ALTER DATABASE statement not allowed within multi-statement transaction.
    2018-12-18 04:36:59.900 spid6s Error: 912, Severity: 21, State: 2.
    2018-12-18 04:36:59.900 spid6s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 226, state 6, 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.
    2018-12-18 04:36:59.900 spid6s Error: 3417, Severity: 21, State: 3.
    2018-12-18 04:36:59.900 spid6s 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.
    2018-12-18 04:36:59.900 spid6s SQL Server shutdown has been initiated

    The workaround- execute the sp: sp_vupgrade_replication manually works. Thanks a lots for the workaround

Feedback and Knowledge Base