Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Why SQL Server is teminating abnormaly?

Status
Not open for further replies.

nomi2000

ISP
Feb 15, 2001
676
0
0
CA
Hi Guys
SQL Server 2000 with Service Pack 3.0
Windows NT 5.2
One of our SQL Server is terminating abnormally everyday and when we saw the SQL Server Logs the following two line are we found in th Log

Warning: override, autoexec procedures skipped
SQL Server is terminating due to 'stop' request from Service Control Manager

Any Idea why this is happening
Regards
Nouman


Nouman Zaheer
Software Engineer
MSR
 
Someone is stopping the services from the Service Manager.

There is a job that is stopping the services.

Something else is unexpectedly crashing SQL Server in which case Service Manager will attempt to stop the services.

Have you checked the Windows Event Viewer logs for any related error messages?

Does this happen at the same time every day? You could run Profiler to see what's happening at that time of day.

-SQLBill
 
Hi SQL Bill
Thanks alot for your reply

what do you mean by
"There is a job that is stopping the services."
which job?

"Does this happen at the same time every day?"
Yes it happens everytime around same time

How i can run "Profiler"?
Regards
Nouman


Nouman Zaheer
Software Engineer
MSR
 
I don't know which job or if there is one....you'll have to look at the jobs that run at that time and see if any of them cause/require the services to stop.

By the way, is the server rebooting? Or is it just SQL Server that is stopping?

What is happening at that time of day? On the server? On the network?

Profiler: Go to Start>Programs>Microsoft SQL Server>Profiler
I don't use this a lot, so I won't be a great help...you can look at the options for what you can trace and pick the ones you think will help. You should run a test trace....get it to where it works, then script the trace. Then run the trace as a job. You can set a job to start the trace, then another job to stop and clear the trace (both of these steps need to be done to view the trace later - clear doesn't mean erase it).

Refer to the BOL for more information on doing Traces.

-SQLBill

BOL=Books OnLine=Microsoft SQL Server's HELP
Installed as part of the Client Tools
Found at Start>Programs>Microsoft SQL Server>Books OnLine

Posting advice: FAQ481-4875
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top