2

  • Windows Server 2016 - Fully Patched

  • Sql Server 2016 SP2 CU3 -> Upgrade to 2017

In place upgrade fails with error message:

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes

See this in the event log:

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.

I'm able to recover from backup, but I need to get this server upgraded.

What am I missing here?

Here is what I'll be trying in a bit (from here)

1) Execute Diff backup in SQL Safe
2) Create Snapshot in VCD
3) Perform Upgrade
4) When fails add -T902 flag to startup parameters
5) Start SQL Server
6) Install CU 11
7) Remove -T902
8) Start SQL Server
Improve this question
4
  • 1
    is sql server running as domain account ? If yes, try changing service account to NT Authority\system and proceed. See dba.stackexchange.com/questions/71797/… Also, post error sql server and windows logs.
    – Kin Shah
    Oct 7, 2018 at 1:35
  • 2
    Look at the errorlog and see what it's complaining about (the error occurring) and post that, please.
    – Sean Gallardy
    Oct 7, 2018 at 2:27
  • Recently I was on thread which helped OP solve similar issue. Please refer to This and This. Basically you have to locate SQL Server errorlog and post its content in the question. The errorlog would have reason why the script for the upgrade failed.
    – Shanky
    Oct 7, 2018 at 5:53
  • Sorry, the error log didnt have much other than what I already posted. Would seem there is an issue with the install process that is resolved in a later CU. Hopefully a SP will be issued soon to help us address this.
    – Wjdavis5
    Oct 8, 2018 at 14:08

2 Answers 2

Reset to default
2

Upgraded from sql 2014 standard edition to sql 2017 standard edition. Seems there is a bug in the initial 2017 edition for standard.

Used the steps ( as Wjdavis5 wrote and others )

  • add -T902 to the startup parameters and started the service ! Great the service is starting
  • Install CU 16 , this was the latest update in August 2019 ! All ok , CU 16 was installed successfully !
  • stop SQL service and remote -T902. Restart Service ! All ok

In case a server restart is needed don't forget to restart

Improve this answer
1
  • Had this problem from SQL 2016. "Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 917, state 1, severity 15." Apparently the RTM installer tries to do an online index rebuild in the SSIS database, which isn't supported by SQL Standard (social.msdn.microsoft.com/Forums/en-US/…)
    – Mark Sowul
    Aug 20, 2021 at 21:51
1

Here is what resolved the error, copied lovingly from a Microsoft forum

Here is what I'll be trying in a bit (from here)

1) Execute Diff backup in SQL Safe
2) Create Snapshot in VCD
3) Perform Upgrade
4) When fails add -T902 flag to startup parameters
5) Start SQL Server
6) Install CU 11
7) Remove -T902
8) Start SQL Server

The key here was to start up sql server with the -T902 parameter and then install the latest CU (which is 11 right now)

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.