January 3, 2014 at 11:49 am
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
January 3, 2014 at 12:04 pm
What does your Application log(From Event Viewer) and latest SQL Server Error Log says?
January 3, 2014 at 12:10 pm
"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."
January 3, 2014 at 12:28 pm
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"?
January 3, 2014 at 12:41 pm
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.
January 3, 2014 at 2:06 pm
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
January 3, 2014 at 2:19 pm
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
January 4, 2014 at 7:13 am
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
January 6, 2014 at 7:13 am
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.
January 6, 2014 at 8:55 am
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.
.
January 6, 2014 at 10:29 am
Thanks for all the help guys. I was able to get it back up last week. The sqlservr.exe file was corrupted. Could not start it from command line. So I was able to take another sqlservr.exe file from another database server with the same service pack and got it working again.
January 7, 2014 at 3:47 am
Hi,
can you take a look on this link:
http://grumpydba.blogspot.de/2012/09/sql-2008-r2-reporting-services-wont.html
There might be a problem in the time a services needs for starting.
regards,
Andreas
January 9, 2014 at 11:25 am
elee1969 (1/6/2014)
Thanks for all the help guys. I was able to get it back up last week. The sqlservr.exe file was corrupted. Could not start it from command line. So I was able to take another sqlservr.exe file from another database server with the same service pack and got it working again.
How did you diagnose the corruption, and check for any other files with the same issue?
January 15, 2014 at 12:42 am
Hi. I'm a newbie to sql server 2008 R2 and I'm having an issue with sql services, it first says "Requesting data from WMI provider " then it returns the following error "The remote procedure call failed"
Please help.
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply