SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Sql Server Services Will not Start


Sql Server Services Will not Start

Author
Message
elee1969
elee1969
SSC Journeyman
SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)

Group: General Forum Members
Points: 95 Visits: 754
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
Sreekanth B
Sreekanth B
SSChasing Mays
SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)

Group: General Forum Members
Points: 607 Visits: 2070
What does your Application log(From Event Viewer) and latest SQL Server Error Log says?
elee1969
elee1969
SSC Journeyman
SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)

Group: General Forum Members
Points: 95 Visits: 754
"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."
Sreekanth B
Sreekanth B
SSChasing Mays
SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)

Group: General Forum Members
Points: 607 Visits: 2070
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"?
elee1969
elee1969
SSC Journeyman
SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)

Group: General Forum Members
Points: 95 Visits: 754
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.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)

Group: General Forum Members
Points: 88391 Visits: 45282
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, MVP, M.Sc (Comp Sci)
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


elee1969
elee1969
SSC Journeyman
SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)SSC Journeyman (95 reputation)

Group: General Forum Members
Points: 95 Visits: 754
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
GilaMonster
GilaMonster
SSC Guru
SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)SSC Guru (88K reputation)

Group: General Forum Members
Points: 88391 Visits: 45282
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, MVP, M.Sc (Comp Sci)
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


dwalker-543874
dwalker-543874
Grasshopper
Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)

Group: General Forum Members
Points: 24 Visits: 190
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.
Bill (DBAOnTheGo)
Bill (DBAOnTheGo)
Right there with Babe
Right there with Babe (793 reputation)Right there with Babe (793 reputation)Right there with Babe (793 reputation)Right there with Babe (793 reputation)Right there with Babe (793 reputation)Right there with Babe (793 reputation)Right there with Babe (793 reputation)Right there with Babe (793 reputation)

Group: General Forum Members
Points: 793 Visits: 588
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.

.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search