Upgrade Error - SQL2K to SQL 2K8

  • Hello,

    I have SQL Server 2000 installed with version 8.00.2282.I am running SQL Server 2008 setup to upgrade the server. When the installation reaches almost 80% towards completion. I am getting the following error.

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

    I tried setting up user account to system / Network Security while running the setup but it did not work.

    Please help.

    Thanks in advance.

    Regards,

    Rohit

  • I have windows server 2003 as OS.

  • have you checked the error logs?

    have a look as there will be a more detailed error message that will give you a clue on why the upgrade failed

  • I am getting following error in SQL Server LOG

    Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 200, state 7, severity 25. 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 am not able to get any clue as why this error should come.

  • Maybe this link will help you.

    http://www.sqlservercentral.com/blogs/glennberry/archive/2009/10/04/stupid-dba-tricks.aspx

    datazulu.com/.../Sql2008-R2-Upgrade-Fail.aspx

  • Unfortunately both the solutions not working.

  • Creating procedure [dbo].[sp_syscollector_upload_instmdw]...

    2010-10-26 13:26:17.47 spid7s Error: 468, Severity: 16, State: 9.

    2010-10-26 13:26:17.47 spid7s Cannot resolve the collation conflict between "SQL_1xCompat_CP850_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the not equal to operation.

    2010-10-26 13:26:17.47 spid7s Error: 912, Severity: 21, State: 2.

    2010-10-26 13:26:17.47 spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 200, state 7, severity 25. 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.

    Is there any link with the previous error in creating the procedure sp_syscollector_upload_instmdw.Can I edit this script before I start the upgrade?

  • from that error it seems like there is a difference in the collation between the servers that the upgrade can't handle, what collation are you running on the sql 2000 machine?

  • Changing the collation at the time of installation worked. Thanks for the help.

  • I hope I will not face any such issue when I will upgrade actual server.

  • SQL_1xCompat_CP850_CI_AS is an upgrade collation, so i would look at possibly changing this before you do the upgrade on live.

  • Now when I am trying to migrate the packages to SQL Server 2008 it is giving an error

    Execution cannot continue as the language dependent resource file

    C:\Program Files\Microsoft SQL Server\80\Tools\Binn\Resources\1033\dtspkg.rll could not be loaded

  • Rohit Chitre-274613 (10/26/2010)


    I hope I will not face any such issue when I will upgrade actual server.

    Oh i'm sure you will. I haven't run into the same problems your having but on my test server i have yet to figure out why i'm not able to install/upgrade the management console. Going from SQL 2000 to 2008 doesn't appear to go as smoothly as MS lead me to believe. I think i'm going to try upgrading to 2005 then to 2008 to see if that goes any smoother.

Viewing 14 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply