locked
Error 15116 when upgrading SQL2000 to 2008, with "wait on the database engine recovery handle failed." error RRS feed

  • Question

  • HELP.  SQL2000 SP4 to SQL2008 on Server 2003 SP2.  Getting error "Wait on the Database Engine recovery handle failed." error during upgrade. 

    Log files show Event ID 912, "Script level upgrade for databse 'master' failed because upgrade step 'sqlagent90_msdb_upgrade.sql' encountered error 15116, stat 1, severity 16."

    I've seen KB960781 (http://support.microsoft.com/default.aspx/kb/960781) and I don't think it applies to me since I have not renamed SA nor am I getting error 515.  Irregardless, I tried the fix anyway.  When i run 'sqlcmd', I encounter "Login Failed... only only 1 administrator can connect at this time."

    Please help, production server is down now!!!!
    Monday, February 8, 2010 5:56 PM

Answers

  • Hi Joe,
    Before you perform an in-place upgrade from SQL Server 2000 to 2008, it is recommended that you first run SQL Server 2008 Upgrade Advisor to analyze the instances for preparation:
    Microsoft SQL Server 2008 Upgrade Advisor
    http://www.microsoft.com/downloads/details.aspx?FamilyID=f5a6c5e9-4cd9-4e42-a21c-7291e7f0f852&displaylang=en

    Joe, to make an effective upgrade, I recommend that you install a pure new SQL Server 2008 instance instead of a in-place upgrade and then move the existing databases on your SQL Server 2000 instance to your new instance. This is easy and has less impact on the existing instance. You can refer to this article:
    How to move databases between computers that are running SQL Server
    http://support.microsoft.com/kb/314546

    Best regards,
    Carles Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help
    • Marked as answer by Alex Feng (SQL) Wednesday, February 24, 2010 10:00 AM
    Wednesday, February 10, 2010 12:39 PM

All replies

  • I'm able to login to sqlcmd now.  I know SA has not been renamed since I just used that account.  I also reset the SA password to complex.  Still upgrade fails.

    I tried this fix:

    http://social.msdn.microsoft.com/Forums/en/sqlsetupandupgrade/thread/116cb02f-81f0-456b-ab7b-2c2dc157e99e

    ...did not help. DB owner of master is already SA (0x01).
    Monday, February 8, 2010 8:49 PM
  • Hi Joe,
    Before you perform an in-place upgrade from SQL Server 2000 to 2008, it is recommended that you first run SQL Server 2008 Upgrade Advisor to analyze the instances for preparation:
    Microsoft SQL Server 2008 Upgrade Advisor
    http://www.microsoft.com/downloads/details.aspx?FamilyID=f5a6c5e9-4cd9-4e42-a21c-7291e7f0f852&displaylang=en

    Joe, to make an effective upgrade, I recommend that you install a pure new SQL Server 2008 instance instead of a in-place upgrade and then move the existing databases on your SQL Server 2000 instance to your new instance. This is easy and has less impact on the existing instance. You can refer to this article:
    How to move databases between computers that are running SQL Server
    http://support.microsoft.com/kb/314546

    Best regards,
    Carles Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help
    • Marked as answer by Alex Feng (SQL) Wednesday, February 24, 2010 10:00 AM
    Wednesday, February 10, 2010 12:39 PM
  • This issue has been resolved.  It still goes back to the complex password issue.  I had to turn off complex password policy on my domain, run the install repair, and it worked successfully.  It does not help to just make the SA password complex.  There are many blogs out there that point to an account being used in the install script that does not meet the complex password.  I could not find that account in my case, so I had to turn off my policy temporarily.
    Wednesday, February 24, 2010 5:02 PM