Unable to connect to SQL Server 2008 instance after applying SP1

Unable to connect to SQL Server 2008 instance after applying SP1

  • Comments 4

Problem Description

===============

Not able to connect to SQL Server 2008 instance after applying SP1.

Connection would fail with the following error

TITLE: Connect to Server

------------------------------

Cannot connect to <Server name>

------------------------------

ADDITIONAL INFORMATION:

Login failed for user '<Domain Name>\<user name>'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. (Microsoft SQL Server, Error: 18401)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18401&LinkId=20476

------------------------------

BUTTONS:

OK

 

Cause

=====

Sqlagent100_msdb_upgrade.sql from SQL Server 2008 SP1 upgrade did not complete successfully. Following errors were reported in the ERRORLOG.txt

 

2010-03-26 20:09:45.33 spid7s      Error: 17750, Severity: 16, State: 0.

2010-03-26 20:09:45.33 spid7s      Could not load the DLL xpstar.dll, or one of the DLLs it references. Reason: 193(%1 is not a valid Win32 application.).

2010-03-26 20:09:45.33 spid7s      Uploading data collector package from disk: Install\SqlTraceCollect.dtsx

2010-03-26 20:09:45.34 spid7s      Uploading data collector package from disk: Install\SqlTraceCollect.dtsx

2010-03-26 20:09:45.34 spid7s      Error: 4861, Severity: 16, State: 1.

2010-03-26 20:09:45.34 spid7s      Cannot bulk load because the file "Install\SqlTraceCollect.dtsx" could not be opened. Operating system error code 3(The system cannot find the path specified.).

2010-03-26 20:09:45.34 spid7s      Error: 912, Severity: 21, State: 2.

2010-03-26 20:09:45.34 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.

 

Resolution

========

 

1)                   To begin with ensure that XPStar.dll, SQLTraceCollect.dtsx is located under -

<OS DRIVE>:\Program Files\Microsoft SQL Server\MSSQL10.<INSTANCENAME>\MSSQL\Install

2)                   If these files exist, then open xpstar.dll with dependency walker    

http://www.dependencywalker.com/

3)                   Check for missing dependencies for xpstar.dll

4)                   In our case dependency walker confirmed that ATL80.dll under 

C:\Windows\WinSxS\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.1833_none_8 a17faaf2edd3e00\ was failing to load.

5)                   Downloaded the latest “Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package

ATL Security Update from “http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en

6)                   Restarted SQL server services and the upgrade scripts could run this time.

 

 

Kumar Bijayanta
SE, Microsoft SQL Server.

Reviewed by
Shamik Ghosh & Amit banerjee
Technical Lead, Microsoft SQL Server.

 

Leave a Comment
  • Please add 7 and 5 and type the answer here:
  • Post
  • I had exactly this issue after attempting to reinstall sql 2008 and sp1 after installing another MS product where the ATL files where prerequisites of that software.

    SP1 would not install

  • I'm having a similar issue with SP2 - while I was applying SP2 on SQL 2008 our sql browser account became locked.  Which caused the install to fail.  When that issue was resolved I was not able to restart the sp2 install as it thought sp2 had been installed.  I was also unable to bring up the sql server service as the following message is in the log:

    Dropping existing Agent certificate ...

    2011-01-24 10:19:26.05 spid6s      DBCC TRACEON 4606, server process ID (SPID) 6. This is an informational message only; no user action is required.

    2011-01-24 10:19:26.05 spid6s      DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    2011-01-24 10:19:26.27 spid6s      DBCC TRACEOFF 4606, server process ID (SPID) 6. This is an informational message only; no user action is required.

    2011-01-24 10:19:26.27 spid6s      DBCC execution completed. If DBCC printed error messages, contact your system administrator.

    2011-01-24 10:19:26.27 spid6s      Error: 5133, Severity: 16, State: 1.

    2011-01-24 10:19:26.27 spid6s      Directory lookup for the file "F:\Microsoft SQL Server\MSSQL10.WDHN2008C125202\MSSQL\DATA\temp_MS_AgentSigningCertificate_database.mdf" failed with the operating system error 3(The system cannot find the path specified.).

    2011-01-24 10:19:26.27 spid6s      Error: 1802, Severity: 16, State: 1.

    2011-01-24 10:19:26.27 spid6s      CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

    2011-01-24 10:19:26.32 spid6s      Error: 912, Severity: 21, State: 2.

    2011-01-24 10:19:26.32 spid6s      Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 598, state 1, 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.

    2011-01-24 10:19:26.34 spid6s      Error: 3417, Severity: 21, State: 3.

    2011-01-24 10:19:26.34 spid6s      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.

    2011-01-24 10:19:26.34 spid6s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

    2011-01-24 10:19:26.44 Server      The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/wdh107nwsql02.bsc.bscal.com:WDHN2008C125202 ] for the SQL Server service.

    2011-01-24 10:19:26.44 Server      The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/wdh107nwsql02.bsc.bscal.com:1835 ] for the SQL Server service.

    There is no such directory on my server that it is referencing (Directory lookup for the file "F:\Microsoft SQL Server\MSSQL10.WDHN2008C125202\MSSQL\DATA\temp_MS_AgentSigningCertificate_database.mdf" failed with the operating system error 3(The system cannot find the path specified.).

    ) - any suggestion on how to fix this one?

  • Hi Kumar Iam facing the same issue.Iam unable to connect the instance after installting the sp1 on sql server 2008 r2(RTM).

    How ever after adding the trace flag 902 on the startup parameters i could able to connect to the instance however I feel that is not a fix

    Please help me in the issue

  • RATNA PRASASD,

    Can you please post ERRORLOG or better choice would be to open a thread on MSDN Forum

    social.msdn.microsoft.com/.../threads

Page 1 of 1 (4 items)