Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Sql Server Services Will not Start Expand / Collapse
Author
Message
Posted Friday, January 3, 2014 11:49 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, December 5, 2014 10:25 AM
Points: 57, Visits: 541
Hello - we had an issue where we had to pull a backup VM and now the sql server services will not start. The message i get is 'the service did not respond to the start or control request in a timely fashion'. I have tried the reg key solution on the web already but it does not work. i checked all the path for parameters master, mastlog, error and they are in the correct directory path. Does anyone have any ideas or suggestions?

Thanks
Post #1527677
Posted Friday, January 3, 2014 12:04 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, December 12, 2014 8:35 AM
Points: 309, Visits: 1,309
What does your Application log(From Event Viewer) and latest SQL Server Error Log says?
Post #1527681
Posted Friday, January 3, 2014 12:10 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, December 5, 2014 10:25 AM
Points: 57, Visits: 541

"The SQL Server (MSSQLSERVER) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."
Post #1527684
Posted Friday, January 3, 2014 12:28 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, December 12, 2014 8:35 AM
Points: 309, Visits: 1,309
Nothing more from Logs? The info provided doesn't look much useful to me for troubleshooting...Try investigating more Log entries(Both Windows App and SQL Error Logs) for clues.

Btw, what do you mean by "we had an issue where we had to pull a backup VM"?
Post #1527690
Posted Friday, January 3, 2014 12:41 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, December 5, 2014 10:25 AM
Points: 57, Visits: 541
sreekanth bandarla (1/3/2014)
Nothing more from Logs? The info provided doesn't look much useful to me for troubleshooting...Try investigating more Log entries(Both Windows App and SQL Error Logs) for clues.

Btw, what do you mean by "we had an issue where we had to pull a backup VM"?


It does not write anything onto the Sql Error log and for Windows i get:

"The SQL Server (MSSQLSERVER) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."


I have already tried increasing the ServicesPipeTimeout in the reg and doesnt work. For your last question we had disk failure and lost our VM so we had to pull a backup copy up.
Post #1527694
Posted Friday, January 3, 2014 2:06 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:13 AM
Points: 40,609, Visits: 37,070
See if this helps, or at least lets you narrow down the cause: http://www.simple-talk.com/sql/backup-and-recovery/the-sql-server-instance-that-will-not-start/


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1527722
Posted Friday, January 3, 2014 2:19 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, December 5, 2014 10:25 AM
Points: 57, Visits: 541
GilaMonster (1/3/2014)
See if this helps, or at least lets you narrow down the cause: http://www.simple-talk.com/sql/backup-and-recovery/the-sql-server-instance-that-will-not-start/


Hi Gail - i actually saw your information earlier today. Thanks again. The only thing i notice from your list below is the Sql error log is not logging. All the file paths are correct.

Unable to open the error log
Post #1527727
Posted Saturday, January 4, 2014 7:13 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:13 AM
Points: 40,609, Visits: 37,070
If that's the error you're getting, refer to the section in that article on SQL being unable to access the error log. Last section iirc


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1527811
Posted Monday, January 6, 2014 7:13 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, December 10, 2014 9:23 AM
Points: 8, Visits: 171
When I saw "VM" and "backup" and "SQL won't start" it reminds me of an incident a few months ago. I'll pass this along in case it helps.

One of our developers needed a test environment of an already existing production SQL Server. The production SQL Server was a VM, so the VM administrator made a clone of the production server, renamed it, and declared it ready to go. When the developer tried to use it, he couldn't access SQL Server. I logged in and saw that SQL Server looked like it was installed, but was not running. I got the same error mentioned here and also could not get anything meaningful from the SQL logs.

I tried a couple of things to get it running but couldn't get it to budge. I then tried a repair installation, which also failed. The end result was that I had to completely un-install SQL Server from this VM and re-install. Once it was re-installed and service packs applied, I was able to attach the databases and it has been working ever since.

It seemed to me like there was something about the "cloning" of the VM that missed something critical to SQL Server.
Post #1528084
Posted Monday, January 6, 2014 8:55 AM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Wednesday, November 26, 2014 2:06 PM
Points: 611, Visits: 516
Just to clear something up, I clone my VM's quite often. SQL starts up and has no issues. There may be an issue with how the cloning was done, but cloning it self works well and is safe. I use clones to test out major changes in design or theory with good data and not using a production box.

.
Post #1528133
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse