Error Installing 2008 R2 SP2

Recently I installed SP2 on my testing server and ran into an issue I think is very import to pass along.

After installing SP2 the server needed to reboot. I went through the process and let the server do its thing giving it a few minutes to come back up. After some time I tried to log in I got this error.

Login failed for user user_name. Reason: Server is in script upgrade mode. Only administrator can connect at this time.

I didn’t think this is a good sign, especially since it had been at least 30 minutes or more since I rebooted the server.

The investigation begins.

Reviewing the error log:

2011-06-21 08:28:21.08 spid6s      Error: 5123, Severity: 16, State: 1.

2011-06-21 08:28:21.08 spid6s      CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file ‘D:\SQLLogs\2008R2\temp_MS_AgentSigningCertificate_database_log.LDF’.

2011-06-21 08:28:21.09 spid6s      Error: 5123, Severity: 16, State: 1.

2011-06-21 08:28:21.09 spid6s      CREATE FILE encountered operating system error 3(The system cannot find the path specified.) while attempting to open or create the physical file ‘D:\SQLLogs\2008R2\temp_MS_AgentSigningCertificate_database_log.LDF’.

2011-06-21 08:28:21.09 spid6s      Error: 1802, Severity: 16, State: 4.

2011-06-21 08:28:21.09 spid6s      CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

2011-06-21 08:28:21.09 spid6s      Error: 912, Severity: 21, State: 2.

2011-06-21 08:28:21.09 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-06-21 08:28:21.10 spid6s      Error: 3417, Severity: 21, State: 3.

2011-06-21 08:28:21.10 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-06-21 08:28:21.63 spid6s      SQL Trace was stopped due to server shutdown. Trace ID = ‘1’. This is an informational message only; no user action is required.

2011-06-21 08:28:22.92 Server      The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/Server_name:MSSQL2008 ] for the SQL Server service.

2011-06-21 08:28:22.92 Server      The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/Server_name:57874 ] for the SQL Server service.

Reading the log what sticks out are the following errors.

Error: 5123, Severity: 16, State: 1.

CREATE FILE encountered operating system error…

Error: 1802, Severity: 16, State: 4.

CREATE DATABASE failed…

Error: 912, Severity: 21, State: 2.

Script level upgrade for database ‘master’ failed…

Error: 3417, Severity: 21, State: 3.

Cannot recover the master database…

Holly mackerel! What the heck happened here?

Root Cause

It was not the SP. Recently I had additional drives added to my server. I had moved the log and backup folders from their original location to the new drives but never changed the information within SQL Server. So when the server rebooted it could not find the folders or files on the server. After changing the location from ‘D:\SQLLogs\2008R2\temp_MS_AgentSigningCertificate_database_log.LDF’.

To ‘L:\SQLLogs\2008R2\temp_MS_AgentSigningCertificate_database_log.LDF’.

I restarted the server and everything started as expected.

Lessons Learned

When you change a configuration on a server make sure you complete the changes everywhere. This is my testing server, so no major harm done, but no excuse for my slack job on completing the tasks needed to finish the job.

Cheers!

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s