| Author |
Topic |
|
bmistry
Starting Member
17 Posts |
 Posted - 2006-04-26 : 10:52:51
|
| HiyaSince yesterday the sqlserver service has been falling over, my error logs says the below?006-04-26 11:28:41.64 spid51 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure 'sp_MSgetversion'.2006-04-26 11:28:41.92 spid51 Error: 15457, Severity: 0, State: 12006-04-26 11:28:41.92 spid51 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..2006-04-26 11:28:42.04 spid51 Using 'xplog70.dll' version '2000.80.2039' to execute extended stored procedure 'xp_msver'.2006-04-26 14:44:08.92 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.What do I need to do? Is is just a matter of running the reconfigure script? Yesterday night we had some monitoring installed on the server. Can anyone help?Thanks |
|
|
bmistry
Starting Member
17 Posts |
Posted - 2006-04-26 : 10:59:54
|
| when I do start the agent I get Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01bin the error log |
 |
|
|
druer
Constraint Violating Yak Guru
314 Posts |
Posted - 2006-04-26 : 11:00:13
|
| It appears from the message in the log that someone opened up the Service Control Manager and said "Stop" for the server process. They may have meant to stop and restart the SQL Job Agent and did that by mistake, or they may have done it intentionally. I'm not sure that the other messages are relevant but I could be wrong. |
|
|
|
bmistry
Starting Member
17 Posts |
Posted - 2006-04-26 : 11:14:31
|
| I dont know if anyone has the privs to do that apart from me and I havent stopped anything today..........anymore ideas? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-04-26 : 13:47:25
|
quote:
2006-04-26 14:44:08.92 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.
The above means either someone stopped the SQL Server service or a reboot occurred. You'll need to check Event Viewer to see which one actually occurred. You can check the Security Log to see who was logged in at the time as well.The other messages are typical message when SQL Server is starting up. This is normal.Tara Kizeraka tduggan |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-04-26 : 20:55:20
|
| if you are having difficulty identifying the reason,you can automatically start the sql servicesgo to control panel>administrative tools>services>mssqlserver>recovery taband change 1 to 2nd failure to start the servicei leave out the 3rd because this tells me to really look into a possible problem if failure occurs again--------------------keeping it simple... |
|
|
|
bmistry
Starting Member
17 Posts |
Posted - 2006-04-27 : 04:26:57
|
| Hi Thanks for thatWhere abouts can I find the event viewer and the security logThanks |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-04-27 : 05:52:38
|
| under computer management,right click your computer icon on your desktop and choose manage--------------------keeping it simple... |
|
|
|
bmistry
Starting Member
17 Posts |
Posted - 2006-04-27 : 06:05:36
|
| Thanks for your help |
|
|
|
kevindrys
Starting Member
7 Posts |
Posted - 2009-06-25 : 12:23:25
|
| 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. |
|
|
|
|
SQL Server is terminating due to 'stop' request fr