December 11, 2003 at 8:31 am
Hi there, just found the server was frozen. couldn't access the SQL server 2K on it, neither any other applications. had to reboot the machine. after reboot, it seems fine. then I found the following errors in the sql server log: Anyone has any clue???
The Scheduler 96 appears to be hung. SPID 0, ECID 2528, UMS Context 0x04F92BA0.
Error: 17883, Severity: 1, State: 0
Sleeping until external dump process completes.
Stack Signature for the dump is 0x00000000
Resuming after waiting on external debug process for 20 seconds.
Timeout while waiting for external dump.
The Scheduler 96 appears to be hung. SPID 0, ECID 2528, UMS Context 0x04F92BA0.
Error: 17883, Severity: 1, State: 0
The Scheduler 96 appears to be hung. SPID 0, ECID 2528, UMS Context 0x04F92BA0.
Error: 17883, Severity: 1, State: 0
The Scheduler 96 appears to be hung. SPID 0, ECID 2528, UMS Context 0x04F92BA0.
tons of all these.....
PS: the server is SQL 2K advanced server, has 4G RAM. THe sql server is configured AWE enabled. max memory 3G, min memory 2G....
December 11, 2003 at 9:07 am
This may be a real SQL Server bug.
Check out if this applies:
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B810885
Francis
December 11, 2003 at 10:02 am
I would call PSS if this happens again.
Steve Jones
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
December 11, 2003 at 10:45 am
Hi crab7,
Have you run 'dbcc checkdb' on all your db's ?, as I had a similar problem on our production servers recently that produced exactly the same scheduler errors you are reporting.
Basically two of our db's were corrupted after a server was not shut down cleanly, this resulted in errors when running 'dbcc checkdb', this indicated that some of the system tables in these db's were also corrupted and subsequently whenever certain server stored procs were run ( either by us or automaitcally by the server ) we received 'assertion file' errors and later in the day when some backups were trying to run the 'scheduler hung' error you reported ( in fact we had hundreds of 'scheduler hung' errors over night - a log file >150mb ).
We discovered that something as simple as clicking on the properties option of a db produced 'assertion file' errors and then following that the 'scheduler hung' errors.
So, what to do ?, well we tried to repair our data page errors in our db's, but to no avail as each time we ran a repair command it failed as it too would try to access the corrupted system tables in the corrupted db.
Result was we had to restore and since then ( fingers crossed ) we've had no 'assertion errors' or 'scheduler hung' errors.
Hope that might help in some way !?, check this link out to the post regarding my request for help; http://www.sqlservercentral.com/Forum/topic.asp?TOPIC_ID=19059&FORUM_ID=5&CAT_ID=1&Topic_Title=SqlServer+Stack+Dumps&Forum_Title=Administration
You won't see any reference the 'scheduler hung' error but this is because our error log was soo large I could only post the most relevant first errors & just hoped that the rest were a consequence of the first error!, but just to show you an example of our error messages similar to yours;
2003-12-10 12:20:21.23 spid53 SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
2003-12-10 12:20:21.25 spid53 clean_tables_xact: active sdes for tabid 3232003-12-10 12:20:21.26 spid53 clean_tables_xact: active sdes for tabid 68813812003-12-10 12:21:02.73 server Error: 17883, Severity: 1, State: 0
2003-12-10 12:21:02.73 server The Scheduler 0 appears to be hung. SPID 53, ECID 0, UMS Context 0x7C79E8B0.
2003-12-10 12:22:02.73 server Error: 17883, Severity: 1, State: 0
2003-12-10 12:22:02.73 server The Scheduler 0 appears to be hung. SPID 53, ECID 0, UMS Context 0x7C79E8B0.
2003-12-10 12:23:02.73 server Error: 17883, Severity: 1, State: 0
2003-12-10 12:23:02.73 server The Scheduler 0 appears to be hung. SPID 53, ECID 0, UMS Context 0x7C79E8B0.
2003-12-10 12:24:02.73 server Error: 17883, Severity: 1, State: 0
2003-12-10 12:24:02.73 server The Scheduler 0 appears to be hung. SPID 53, ECID 0, UMS Context 0x7C79E8B0.
2003-12-10 12:25:02.73 server Error: 17883, Severity: 1, State: 0
2003-12-10 12:25:02.73 server The Scheduler 0 appears to be hung. SPID 53, ECID 0, UMS Context 0x7C79E8B0.
2003-12-10 12:25:05.56 server SQL Server terminating because of system shutdown.
Hope that helps !?.
Regards.
j
December 11, 2003 at 11:25 am
should I apply SQL 'Server 2000 (32-bit) Security Patch MS03-031' or the lasted SP3a??
but on the MS site, it says: If customers have applied SP3, they do not need to apply SP3a...
I already applied SP3, our build now is Microsoft SQL Server 2000 - 8.00.765 (Intel X86) Feb 7 2003 17:33:51 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 2)
December 11, 2003 at 11:30 am
hi crab7,
we applied sp3a to our servers in the hope that it would fix the issue ( as reported on the Microsoft website ) but it did nothing to solve our problems !!!, & I don't think patching your NT will do it either, rather I'd look more at the consistency of your db's for the problem, have you any corruption reported from 'dbcc checkdb' in any db's including master, msdb etc ???
Regards.
j
December 11, 2003 at 11:45 am
Hi jima,
Thanks a lot for your posts. I am loading the last night's db dump to a development server to run dbcc there. I took the dump of production db there to run dbcc every weekdays. It has never reported any error.
Surprisedly, the last night's db dump and log backups following all succeeded.
well, I think I could run a dbcc on the production one later, when it is not that busy... and master, and msdb....
From the reboot this morning till now, however, it behaves rather normal... no errors till now...
December 11, 2003 at 4:30 pm
Yesterday afternoon I posted a topic titled
error 17883. It's the same error. It is microsoft sql 2k sp3 bug. My sql 2k is
8.00.818. No matter it's sp3 or sp3a or applied MS03-031. it's the same.
I checked all my databases (dbcc checkdb)
no error messages. Microsoft says we can call them for the hot fix.
Since rebooting, my server works fine. I haven't called Microsoft. Anybody else called Microfoft for Hot fix? Please advise.
Robert
December 12, 2003 at 9:00 am
hi thanks for all the replies. I did the dbcc on production db yesterday, didn't find any error....and no errors from the reboot of yesterday till today.... I think I'll wait and see....
Just some difference here, this error 17883 did cause our system 'hang', and had to be rebooted...
December 12, 2003 at 2:51 pm
Are you sure your system "hung" caused by the error 17883? are there any other applications on your server like veritas backup? That might cause "hung".
Thanks!
Robert
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply