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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unusual Sql log entries

Status
Not open for further replies.

phil22046

Programmer
Sep 12, 2001
154
US
I checked the logs on Server Case2 which is only being used as a backup device presently. I have disabled all the jobs the SQL agent had listed. Last night several of these messages appeared:

Date Source Message
2007-05-16 11:04.10.77 Server The scheduler 2 appears to be hung. SPID 0, ECID 0, UMS context 0x03B5EBF0

2007-05-16 11:04.10.77 Server Error 17883, severity: 1, state:0

within a few minutes I got the same message referencing scheduler 1,2 adn 3
 
Phil,
The scheduler has nothting to do with the Agent. You can think of a scheduler as a logical CPU used by SQL Server workers. Sometimes there could be a thread which does not yeild to other threads. There are some known issues with SQL Server 2000 SP3 and below with error 17883.

What version of SQL are you on.

Also some info on severity levels.

Your severity is 1.
Severity's 0-10 are informational only.
Errors resulting from programming errors in your SQL code have a severity level in the range 11-16.
Severity levels 17-25 indicate resource problems, hardware problems or internal problems in SQL Server
if the severity is 20 or higher, the process is terminated

- Paul
10qkyfp.gif

- If at first you don't succeed, find out if the loser gets anything.
 
Check your service pack. If it's not sp4 I would upgrade to sp4.
Also,
how is this the only time you have ever seen this message? If so I wouldn't worry about it. Like I said sometimes there are processes that don't want to yield.


- Paul
10qkyfp.gif

- If at first you don't succeed, find out if the loser gets anything.
 
I have service pack 4 installed. And it appeared yesterday in the logs for the first time. the only thing I did yesterday was disable some jobs in the agent that were doing backups and using batch files to rename and copy backup files, and delete old backup files.
 
That error isn't relaited to anything you did. I could be the log writter or number of processes where spid < 50.



- Paul
10qkyfp.gif

- If at first you don't succeed, find out if the loser gets anything.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top