July 17, 2006 at 7:28 am
I see this message "SQL Server is terminating due to 'stop' request from Service Control Manager." in the SQL Server error log.
I see some login failures before this error has occoured. I don't see any reason why the server has stopped suddenly. There is microsoft security patch deployment done before the day it happened.
Is there any specific reason why this happens?
July 17, 2006 at 8:36 am
This means that SQL Server was stopped "gracefully" - either manually or by some process (scheduled job, maybe, or application of a service pack) that stops the service. If the login failures are from Windows logins, it could be that your network became unavailable as part of whatever it was that was going on. You should find some more clues in the Application and System event logs.
John
July 17, 2006 at 9:27 am
I saw the same error like login failed for same service account as in SQL Server error log.
I also observed in application log like resources changing from Cluster NOdeA to Node B and viceversa.
Also error like "
initerrlog: Could not open error log file 'E:\SQLData\MSSQL\log\ERRORLOG'. Operating system error = 3(The system cannot find the path specified.)."
Can any one tell why the above error occoured?
July 17, 2006 at 9:35 am
It sounds like either disk E failed or was unavailable, or the path to the error log was incorrect, and so the SQL Server resources failed over to the other node. If there was continual switching of nodes, then check the path to the log file. Does it exist?
John
July 17, 2006 at 10:05 am
There are certain things that can cause SQL Server to fail. I believe the error log failing is one of them. Did you run out of space or perhaps the disk failed?
July 17, 2006 at 2:41 pm
C drive full up as well can get you and is commonly over looked.
June 25, 2009 at 10:25 am
Had the same situation on one of our SQL Server 2000 servers today, where the Service Control Manager was restarting the SQL Server service. The clue was in the Event Viewer which showed that Backup Exec was restarting just before it. Checked with our backup guy and he was applying several Backup Exec patches at the time of the restarts. The reason SQL Server was affected is that Backup Exec itself is installed on this server and thus has it's BEDB database locally. Everytime he installed a patch, it needed to stop and start SQL Server.
June 8, 2011 at 3:46 pm
If we go through system log in Eventviewer we will find that service control manager will send the stop command to sqlserver agent and sqlserver engine.
This is acutally because of some windows update which inturn will affect Microsoft SQL Server.
Before that Service control Manager command, if checked we will find windows update agent category event. That event is for the security update of Microsoft SQL Server.
Because of it SCM will issue stop command to Microsoft SQL Server Agent and Engine.
Hope my explanation is usefull...
September 4, 2011 at 10:28 pm
HI,
Is there any workaround for this problem? I have been trying it for quite a long time but could not find any breakthru.
Details of Installation & Existing Applications
I have ORACLE 10 version installed.
I have installed and uninstalled other versions of SQL SERVER such as 2005 and 2008 successfully.
I am working over WINDOWS SERVER 2003 R2.
Please help me over with this.. quick response is much appreciated.
Thanks & Regards
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply