none
SQL Server 2012 Standard Edition InPlace Upgrade to SQL Server 2017 standard edition Fails RRS feed

  • Question

  • Hi,

    I am having upgrade issues when attempting to perform an inplace upgrade from MS SQL Server 2012 SP3 (Running on Windows Server 2012 R2) to Windows Server 2017 (SW_DVD9_NTRL_SQL_Svr_Standard_Edtn_2017_64Bit_English_OEM_VL_X21-56945)

    The Installation fails during the upgrade process:

    Feature:                      Database Engine Services
    Status:                        Failed
    Reason for failure:        An error occurred during the setup process of the feature.
    Next Step:                   The upgrade process for SQL Server failed. Use the following information to resolve the error, and                                             then repair your installation by using this command line: setup /action=repair                                                                         /instancename=MSSQLSERVER
    Component name:                SQL Server Database Engine Services Instance Features
    Component error code:          0x851A001A
    Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential                                              causes.

    Error Log states:

    2019-03-19 16:14:27.18 spid5s      ---------------------------------------------
    2019-03-19 16:14:27.18 spid5s      Starting execution of ISServer_upgrade.SQL
    2019-03-19 16:14:27.18 spid5s      ---------------------------------------------
    2019-03-19 16:14:27.18 spid5s       
    2019-03-19 16:14:27.18 spid5s      Taking SSISDB to single user mode
    2019-03-19 16:14:27.18 spid5s      Setting database option SINGLE_USER to ON for database 'SSISDB'.
    2019-03-19 16:14:27.70 spid5s      Error: 1712, Severity: 16, State: 1.
    2019-03-19 16:14:27.70 spid5s      Online index operations can only be performed in Enterprise edition of SQL Server.
    2019-03-19 16:14:27.70 spid5s      Error: 917, Severity: 15, State: 1.
    2019-03-19 16:14:27.70 spid5s      An upgrade script batch failed to execute for database 'master' due to compilation error. Check the previous error message for the line which caused compilation to fail.
    2019-03-19 16:14:27.70 spid5s      Error: 912, Severity: 21, State: 2.
    2019-03-19 16:14:27.70 spid5s      Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 917, state 1, severity 15. 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.
    2019-03-19 16:14:27.70 spid5s      Error: 3417, Severity: 21, State: 3.
    2019-03-19 16:14:27.70 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.
    2019-03-19 16:14:27.70 spid5s      SQL Server shutdown has been initiated
    2019-03-19 16:14:27.70 spid5s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
    2019-03-19 16:14:28.73 spid5s      Error: 25725, Severity: 16, State: 1.
    2019-03-19 16:14:28.73 spid5s      An error occurred while trying to flush all running Extended Event sessions.  Some events may be lost.

    Details Log

    (01) 2019-03-19 16:20:14 Slp: Error result: -2061893606
    (01) 2019-03-19 16:20:14 Slp: Result facility code: 1306
    (01) 2019-03-19 16:20:14 Slp: Result error code: 26
    (01) 2019-03-19 16:20:14 Slp: WER: Application level consent value 'True' was mapped to consent status 'WerConsentApproved'
    (01) 2019-03-19 16:20:17 Slp: WER: Result of the submission:: 'WerReportUploaded'
    (01) 2019-03-19 16:20:17 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
    (01) 2019-03-19 16:20:17 Slp: SetupTelemetry: Closing Telemetry Session
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\SQMClient
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value MachineId
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\140
    (01) 2019-03-19 16:20:17 Slp: SetupTelemetry: Not creating telemetry audit log. Value 'UserRequestedLocalAuditDirectory' doesn't exist in 'HKLM\Software\Microsoft\Microsoft SQL Server\140'
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\140
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value CustomerFeedback
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value EnableErrorReporting
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey SQL
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value MSSQLSERVER
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\MSSQL14.MSSQLSERVER\CPE
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value CustomerFeedback
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to get registry value EnableErrorReporting
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey OLAP
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\Instance Names
    (01) 2019-03-19 16:20:17 Slp: Sco: Attempting to open registry subkey RS
    (01) 2019-03-19 16:20:17 Slp: SetupTelemetry: Telemetry has an active session with 157 events.

    Any help would be appreciated.

    Regards

    Lost

    Tuesday, March 19, 2019 11:29 PM

Answers

  • Hi Lost,

    >>Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 917, state 1, severity 15. 
    The 'ISServer_upgrade.sql' file is part of the DLL and it seems that the upgrade script always build index ONLINE and hence the failing.

    You can try to use the follows steps to fix this:
         1. Run your SQL Server instance with /902 flag
         2. Apply SQL Server 2017 CU13
         3. Remove /902 flag and restart your instance

    Here is a similar thread.
    Upgrade from SQL Server 2016 to SQL Server 2017 Fails on script 'ISServer_upgrade.SQL - SSISDB.

    Best Regards,
    Puzzle
    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


    Wednesday, March 20, 2019 2:34 AM
  • Hi,

    Try to use the SQLServerManager14.msc file to open the Configuration Manager.


    Best Regards,
    Puzzle
    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

    • Marked as answer by LostSoul001 Thursday, March 21, 2019 12:12 PM
    Thursday, March 21, 2019 1:03 AM

All replies

  • Hi Lost,

    >>Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 917, state 1, severity 15. 
    The 'ISServer_upgrade.sql' file is part of the DLL and it seems that the upgrade script always build index ONLINE and hence the failing.

    You can try to use the follows steps to fix this:
         1. Run your SQL Server instance with /902 flag
         2. Apply SQL Server 2017 CU13
         3. Remove /902 flag and restart your instance

    Here is a similar thread.
    Upgrade from SQL Server 2016 to SQL Server 2017 Fails on script 'ISServer_upgrade.SQL - SSISDB.

    Best Regards,
    Puzzle
    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


    Wednesday, March 20, 2019 2:34 AM
  • Hi Puzzle,

    Thanks for the suggestion.

    I went into the SQL Server Configuration Manager --> SQL Server Services --> however I no longer can see SQL Server (MSSQLSERVER) to add the /902 flag.

    The only entry available here is the SQL Server Integration Services 11.0.

    Kind Regards

    Lost


    Wednesday, March 20, 2019 11:27 AM
  • Hi,

    Try to use the SQLServerManager14.msc file to open the Configuration Manager.


    Best Regards,
    Puzzle
    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

    • Marked as answer by LostSoul001 Thursday, March 21, 2019 12:12 PM
    Thursday, March 21, 2019 1:03 AM
  • Hi Puzzle,

    I realized yesterday that was my problem, thanks for responding.

    I followed your recommendations the only difference is I patched to CU13.

    Appreciate your assistance and support.

    Kind regards

    Lost

    Thursday, March 21, 2019 12:11 PM