SQL Server 2017 Upgrade Fail RRS feed

  • Question

  • SQL Server 2016 Std Edition upgrade to SQL Server 2017 Std Edition.

    Upgrade fails, see below excerpt from errorlog

    2017-10-16 13:27:00.47 spid4s      Database 'master' is upgrading script 'ISServer_upgrade.sql' from level 0 to level 500.
    2017-10-16 13:27:00.47 spid4s      ---------------------------------------------
    2017-10-16 13:27:00.47 spid4s      Starting execution of ISServer_upgrade.SQL
    2017-10-16 13:27:00.47 spid4s      ---------------------------------------------
    2017-10-16 13:27:00.47 spid4s       
    2017-10-16 13:27:00.47 spid4s      Taking SSISDB to single user mode
    2017-10-16 13:27:00.47 spid4s      Setting database option SINGLE_USER to ON for database 'SSISDB'.
    2017-10-16 13:27:05.53 spid4s      Error: 1712, Severity: 16, State: 1.
    2017-10-16 13:27:05.53 spid4s      Online index operations can only be performed in Enterprise edition of SQL Server.
    2017-10-16 13:27:05.53 spid4s      Error: 917, Severity: 15, State: 1.
    2017-10-16 13:27:05.53 spid4s      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.
    2017-10-16 13:27:05.53 spid4s      Error: 912, Severity: 21, State: 2.
    2017-10-16 13:27:05.53 spid4s      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.
    2017-10-16 13:27:05.53 spid4s      Error: 3417, Severity: 21, State: 3.
    2017-10-16 13:27:05.53 spid4s      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.
    2017-10-16 13:27:05.53 spid4s      SQL Server shutdown has been initiated

    Thoughts and advice welcome.

    Tuesday, October 17, 2017 6:56 AM

All replies

  • Hi Graham,

    Try to use trace flag 902 to bypass script upgrade mode, then you can try to see what is going on 

    This can help (similar issue, older sql version)
    SQL 2012 to SQL 2014 upgrade problem

    and post from Pinal Dave

    SQL SERVER – Script level upgrade for database ‘master’ failed

    Tuesday, October 17, 2017 11:32 AM
  • Hi Graham,

    Did you solve this problem?

    I have the exact same issue and would be so helpful to know if you found a solution.



    Wednesday, October 18, 2017 2:21 PM
  • I want to add that I have experienced the exact error listed above. I have also tried Lin Leng's response of using the startup parameter (-T902).

    My instance starts and I can logon, but there are no errors that I can see other than the Database SSISDB still in Single-User Mode and not accessible.  The problem appears to be an error updating 'master' from the script 'ISServer_update.sql'. I cannot find this script to investigate what the error might be. I have also attempted deleting the SSISDB database as suggested in Pinal Dave's post. No matter what I do, restarting the instance without the startup parameter (-T902) fails.

    Even removing the SSIS feature has no effect on the problem. It still attempts to use the above script to update 'master'.

    There was an additional post with this issue and the requester closed the case saying that he had to reinstall the SQL instance. I find this workaround unacceptable. 

    Friday, March 16, 2018 2:14 PM
  • After trying to revert and fix, uninstall/install, update I found the only thing that worked to do a new full installation is:

    -Revert to snapshot, update the current SQL version.

    -Uninstall shared feature SSIS 

    -Backup database and move to a different location and delete the database

    -Upgrade: SUCCESS - FINALLY

    -install SSIS

    Wednesday, June 6, 2018 8:58 AM