none
SQL Server 2016 SP2 CU11 Patch failed. RRS feed

  • Question

  • HI Team,

    We have applied CU11 on one of production server, post CU11, sql services was offline, then we bring online with T912 trace, post we ran msdb110_upgrade.sql on server. then we got below error massage. Please help me

    Thanks in advance

    ------------------------------------------

    Execution of POST_SQLAGENT100.SQL complete

    ------------------------------------------

    ------------------------------------

    Moving 2005 SSIS Data to 2008 tables

    ------------------------------------

    Mapping SSIS yukon roles to katmai roles...

    Moving package folders...

    Moving packages...

    Moving logs...

    Dropping yukon stored procedures...

    Dropping yukon tables...

    Creating sysdtslog90 view...

    Database name 'tempdb' ignored, referencing object in tempdb.

    Database name 'tempdb' ignored, referencing object in tempdb.

    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____________________________________________________________________________________________________00000F59, Line 11 [Batch Start Line 64771]

    CONFIG statement cannot be used inside a user transaction.

    Configuration option 'Agent XPs' changed from 1 to 1. Run the RECONFIGURE statement to install.

    Msg 574, Level 16, State 0, Procedure #sp_enable_component____________________________________________________________________________________________________00000F59, 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 1. Run the RECONFIGURE statement to install.

    Msg 574, Level 16, State 0, Procedure #sp_restore_component_state_____________________________________________________________________________________________00000F59, 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_____________________________________________________________________________________________00000F59, 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____________________________________________________________________________________________________00000F59, Line 11 [Batch Start Line 65039]

    CONFIG statement cannot be used inside a user transaction.

    Configuration option 'Agent XPs' changed from 1 to 1. Run the RECONFIGURE statement to install.

    Msg 574, Level 16, State 0, Procedure #sp_enable_component____________________________________________________________________________________________________00000F59, Line 13 [Batch Start Line 65039]

    CONFIG statement cannot be used inside a user transaction.

    Data Collector Status

    CollectorEnabled:0

    Collection set status

    Uid:7B191952-8ECF-4E12-AEB2-EF646EF79FEF, Name:Disk Usage, IsRunning:0

    Uid:49268954-4FD4-4EB6-AA04-CD59D9BB5714, Name:Server Activity, IsRunning:0

    Uid:2DC02BD6-E230-4C05-8516-4E8C0EF21F95, Name:Query Statistics, IsRunning:0

    Uid:ABA37A22-8039-48C6-8F8F-39BFE0A195DF, Name:Utility Information, IsRunning:0

    post_dc100::uploading instmdw.sql to msdb ...

    Uploading instmdw.sql from disk: C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Install\instmdw.sql

    Loaded 1332276 bytes from 'C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Install\instmdw.sql'

    post_dc100::Checking if collection set status were captured in temp table...

    post_dc100::Restoring collection set running status...

    The state of the collection set has changed, but it will not start or stop until the collector is enabled.

    post_dc100::Checking if Data collector was enabled before upgrade...

    post_dc100::Current data collector state is same as pre-upgrade state

    Data Collector Status

    CollectorEnabled:0

    Collection set status

    Uid:7B191952-8ECF-4E12-AEB2-EF646EF79FEF, Name:Disk Usage, IsRunning:0

    Uid:49268954-4FD4-4EB6-AA04-CD59D9BB5714, Name:Server Activity, IsRunning:0

    Uid:2DC02BD6-E230-4C05-8516-4E8C0EF21F95, Name:Query Statistics, IsRunning:0

    Uid:ABA37A22-8039-48C6-8F8F-39BFE0A195DF, Name:Utility Information, IsRunning:0

    Configuration option 'Agent XPs' changed from 1 to 1. Run the RECONFIGURE statement to install.

    Msg 574, Level 16, State 0, Procedure #sp_restore_component_state_____________________________________________________________________________________________00000F59, Line 9 [Batch Start Line 65039]

    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_____________________________________________________________________________________________00000F59, Line 11 [Batch Start Line 65039]

    CONFIG statement cannot be used inside a user transaction.

    Restored implicit transactions state to OFF

    Upgrading Database Mail related objects...

    Completed upgrade of Database Mail related objects...



    Wednesday, February 12, 2020 12:43 AM

Answers

  • Hi Erland,

    domain\account is owner of sql job, and login doesn't exists, now i have changed job owner to SA. I hope issue might resolve. We have to wait for one week to check.

    once again thanks for your help

    Thanks,

    Thiruveedhula 

    • Marked as answer by Thiruveedhula Tuesday, February 18, 2020 5:21 PM
    Friday, February 14, 2020 8:48 PM
  • Issue has been resolved. after changing job owner to SA.

    Once again thank you Erland.

    THanks,

    Thiruveedhula

    Saturday, February 15, 2020 12:57 AM

All replies

  • Do you get those errors after running msdb110_upgrade.sql?

    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    Wednesday, February 12, 2020 4:57 AM
    Answerer
  • Hi Dimant,

    yes after running msdb110_upgrade.sql, we got error. which i have uploaded 

    Thanks in advance

    Wednesday, February 12, 2020 5:18 PM
  • Can you post the output of

    sp_configure 'user options'

    This seems familiar, but it was a while since I saw this.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Wednesday, February 12, 2020 10:34 PM
  • name minimum maximum config_value run_value
    user options 0 32767 0 0
    Thursday, February 13, 2020 12:28 AM
  • name -user options
    minimum -0
    maximum -32767
    config_value -0
    run_value -0
    Thursday, February 13, 2020 12:29 AM
  • Hi BB5515523,

    Could you please share us more detailed error message which is located at Program Files\Microsoft SQL Server\MSSQL13. \MSSQL\Log\ERRORLOG about your issue?

    You could try to restore last known backup of MSDB database, restart SQL Server without any trace flag and rerun CU11 again. Please refer to this blog for more details.

    Hope this could help you.

    Best Regards,

    Amelia


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, February 13, 2020 3:27 AM
  • 2020-02-08 18:55:14.05 spid5s      -------------------------------------------
    2020-02-08 18:55:14.05 spid5s      Execution of MSDB_POST_INSTALL.SQL complete
    2020-02-08 18:55:14.05 spid5s      -------------------------------------------
    2020-02-08 18:55:14.07 spid5s       
    2020-02-08 18:55:14.07 spid5s      Populate syssubsystem table...
    2020-02-08 18:55:14.47 spid5s       
    2020-02-08 18:55:14.47 spid5s      Revoke any permission to public role...
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.47 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.48 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.49 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.50 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.51 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.52 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.53 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.53 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.53 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.53 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.53 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.53 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.53 spid5s      The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
    2020-02-08 18:55:14.91 spid5s       
    2020-02-08 18:55:14.91 spid5s      Granting login access'domain\account' to msdb database...
    2020-02-08 18:55:14.92 spid5s      A problem was encountered granting access to MSDB database for login '(null)'. Make sure this login is provisioned with SQLServer and rerun sqlagent_msdb_upgrade.sql 
    2020-02-08 18:55:14.92 spid5s      A problem was encountered granting access to MSDB database for login '(null)'. Make sure this login is provisioned with SQLServer and rerun sqlagent_msdb_upgrade.sql 
    2020-02-08 18:55:14.92 spid5s       
    2020-02-08 18:55:14.92 spid5s      Adding user 'Domain\account' to SQLAgentUserRole msdb role...
    2020-02-08 18:55:14.93 spid5s      Performing replication job security meta-data upgrades...
    2020-02-08 18:55:16.04 spid5s       
    2020-02-08 18:55:16.04 spid5s      Upgrading SQL Server Log Shipping...
    2020-02-08 18:55:16.23 spid5s      Upgraded SQL Server Log Shipping successfully.
    2020-02-08 18:55:16.25 spid5s       
    2020-02-08 18:55:16.25 spid5s      ------------------------------------------
    2020-02-08 18:55:16.25 spid5s      Execution of POST_SQLAGENT100.SQL complete
    2020-02-08 18:55:16.25 spid5s      ------------------------------------------
    2020-02-08 18:55:16.25 spid5s      ------------------------------------
    2020-02-08 18:55:16.25 spid5s      Moving 2005 SSIS Data to 2008 tables
    2020-02-08 18:55:16.25 spid5s      ------------------------------------
    2020-02-08 18:55:16.25 spid5s      Mapping SSIS yukon roles to katmai roles...
    2020-02-08 18:55:16.26 spid5s      Moving package folders...
    2020-02-08 18:55:16.27 spid5s      Moving packages...
    2020-02-08 18:55:16.27 spid5s      Moving logs...
    2020-02-08 18:55:16.28 spid5s      Dropping yukon stored procedures...
    2020-02-08 18:55:16.32 spid5s      Dropping yukon tables...
    2020-02-08 18:55:16.33 spid5s      Creating sysdtslog90 view...
    2020-02-08 18:55:16.34 spid5s      Database name 'tempdb' ignored, referencing object in tempdb.
    2020-02-08 18:55:16.34 spid5s      Database name 'tempdb' ignored, referencing object in tempdb.
    2020-02-08 18:55:16.36 spid5s      Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
    2020-02-08 18:55:16.36 spid5s      Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
    2020-02-08 18:55:16.36 spid5s      Error: 574, Severity: 16, State: 0.
    2020-02-08 18:55:16.36 spid5s      CONFIG statement cannot be used inside a user transaction.
    2020-02-08 18:55:16.36 spid5s      Error: 912, Severity: 21, State: 2.
    2020-02-08 18:55:16.36 spid5s      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.
    2020-02-08 18:55:16.37 spid5s      Error: 3417, Severity: 21, State: 3.
    2020-02-08 18:55:16.37 spid5s      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.
    2020-02-08 18:55:16.37 spid5s      SQL Server shutdown has been initiated
    2020-02-08 18:55:16.37 spid5s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

    Thursday, February 13, 2020 7:11 PM
  • I've been looking at this log file, as well as the script, and I have not been able to find any good answer. However, there is this message:

     Granting login access'domain\account' to msdb database...
    2020-02-08 18:55:14.92 spid5s      A problem was encountered granting access to MSDB database for login '(null)'. Make sure this login is provisioned with SQLServer and rerun sqlagent_msdb_upgrade.sql 

    Maybe you should try to address this issue and see if it helps.

    Not that I see why this would leave an open transaction, but is the only thing I can see.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Thursday, February 13, 2020 10:54 PM
  • Hi Erland,

    Thanks for reply, But the account doesn't exist in sql server. it was disabled in  AD four years back. Do you want me to create login and grant permission?

    Thank,

    Thiruveedhula

    Friday, February 14, 2020 1:11 AM
  • Hi Erland,

    Thanks for reply, But the account doesn't exist in sql server. it was disabled in  AD four years back. Do you want me to create login and grant permission?

    That is incredible are you triple sure. If that is not much of a problem can you enable the login, add that into sql server and try. But again its hard to believe. I just hope you are not hitting any bug

    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    Friday, February 14, 2020 7:28 AM
    Moderator
  • Thanks for reply, But the account doesn't exist in sql server. it was disabled in  AD four years back. Do you want me to create login and grant permission?

    To be honest I don't know what I want. Well, I want your upgrade to succeed. But I don't know what you should do to reach that goal.

    It could help to create the account in SQL Server. Then again, if has been missing for many years, you must have been able to run a few more upgrades since. So try adding the login, but don't be surprised if the upgrade fails again.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Friday, February 14, 2020 7:42 AM
  • Hi Erland,

    Thanks for your help. Hence it's production server, so i can try coming weekend or 22nd feb. I will let you know the result. SQL is running with T912 flag.

    Thanks,

    Thiruveedhula

    Friday, February 14, 2020 2:54 PM
  • Hi Erland,

    domain\account is owner of sql job, and login doesn't exists, now i have changed job owner to SA. I hope issue might resolve. We have to wait for one week to check.

    once again thanks for your help

    Thanks,

    Thiruveedhula 

    • Marked as answer by Thiruveedhula Tuesday, February 18, 2020 5:21 PM
    Friday, February 14, 2020 8:48 PM
  • Issue has been resolved. after changing job owner to SA.

    Once again thank you Erland.

    THanks,

    Thiruveedhula

    Saturday, February 15, 2020 12:57 AM
  • Glad to hear that it worked out!


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Saturday, February 15, 2020 10:17 AM
  • Hi Thiruveedhula,

    I am glad to know that your problem has been solved. In order to close this thread, please mark useful replies as answers. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.

    Best Regards,

    Amelia


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, February 17, 2020 1:14 AM
  • I did some further analysis of the upgrade script,and I found that there is a passage that creates users in msdb for job owners who are not in sysadmin, something I find dubious in itself.

    I found that there is a flaw in an error handling in the script. The script calls a system procedure to create the users, but the surrounding CATCH handler does not consider the possibility that the procedure starts a transaction (which it does), so when there is an error the transaction remains open, and the script fails later.

    I have filed two feedback items. This is a bug about the failure as such:

    https://feedback.azure.com/forums/908035-sql-server/suggestions/39750742-poor-transaction-handling-causes-cu-upgrade-to-fai

    And this is a suggestion to remove the dubious section entirely:

    https://feedback.azure.com/forums/908035-sql-server/suggestions/39750766-cu-upgrades-should-not-create-users-in-msdb-for-jo

    Votes are welcome!


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    17 hours 22 minutes ago