SQL Server Service will start but won't stay on

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2008 Forums

SQL Server Administration (2008)

SQL Server Service will start but won't stay on

Author

Topic

terraburn
Starting Member

1 Post

Posted - 2012-06-30 : 14:01:57

I just finished an SQL Server 2005 to 2008 in-place upgrade. I had some issues as described below, but a repair seems to have finally resolved the failures I was getting. However I'm still dealing with the service not starting. I'll turn it on, and anywhere from 5-10 seconds later it stops.

*Below is the previous issue. I ran the repair function and it completed successfully*

Firstly, thank you for taking the time to look.

I did an in-place upgrade from sql server 2005 standard to 2008 r2 standard. Everything went fine until the end when it give me a "Wait on the Database Engine recovery handle failed" error.

I tried logging onto the server via Server Management Studio but it can't find the server.

I notice the SQL Server 'service' was not started.

I tried to manually start the service from the SQL Server Configuration Manager, but when I start the service using the Administrator account on the domain, it won't stay on. I tried using "Network Service", "Local Service", etc. but it always says the account is the "wrong type".

Note the server is a SECONDARY domain controller. The install gave me the warning but I ignored it due to the nature of the server being a failover DC.

I've looked over the entire net but can't find anything that will help.

Here is the bottom bit of the ERRORLOG file:

2012-06-30 13:03:49.01 spid7s Error: 5133, Severity: 16, State: 1. 2012-06-30 13:03:49.01 spid7s Directory lookup for the file "H:\SQL_DB\temp_MS_AgentSigningCertificate_database.mdf" failed with the operating system error 3(The system cannot find the path specified.).
2012-06-30 13:03:49.01 spid7s Error: 1802, Severity: 16, State: 1.
2012-06-30 13:03:49.01 spid7s CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2012-06-30 13:03:49.01 spid7s Error: 912, Severity: 21, State: 2.
2012-06-30 13:03:49.01 spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent90_sysdbupg.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. 2012-06-30 13:03:49.02 spid7s Error: 3417, Severity: 21, State: 3. 2012-06-30 13:03:49.02 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it.

nigelrivett
Master Smack Fu Yak Hacker

3385 Posts

Posted - 2012-07-02 : 06:43:27

There are a lot of posts around about agentsigningcertificate.
Here's one from this site
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=85797

I wouldn't suggest an in-place upgrade as you don't have anything to go back to. Try a new installation and restoring backups.

==========================================
Cursors are useful if you don't know sql.
SSIS can be used in a similar way.
Beer is not cold and it isn't fizzy.

vivekinmadar
Starting Member

3 Posts

Posted - 2012-07-02 : 09:37:27

Hi
please try in test enviroment first after try in PRO
Firstly, we can check if this is a valid path. Since we are seeing an operating system error 3 the path is definitely not valid
· Please Note: We will not find this file anywhere on the machine as this is a temporary database that is created only for the sake of setup and will not persist after the setup
· The registry Key that we can check for the Default Data Path is
o HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.<Instance Name>\Setup\SQLDataRoot
· If this key has an erroneous path we can change that and restart the services for SQL Server to solve the issue
· Else if this key has the correct data path and still the error message shows an invalid path then we can visit the following registry hive
o HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.<Instance Name>\MSSQLServer
· I was able to identify the above registry hive by simply searching the registry for some portion of the path given in the error
· We might find keys like "backupdirectory", "defaultdata" and "defaultlog" having the invalid path in them. The most obvious ones that we need to change are "defaultdata" and "defaultlog"
· We have to change their values to the one we see under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.<Instance Name>\Setup\SQLDataRoot
· Now we should be able to start the services without any issues
· We can also look into the Errorlog and see if the upgrade script for the Master database was executed successfully.

vivekinmadar
Starting Member

3 Posts

Posted - 2012-07-02 : 09:37:35

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources