Error 17883 in SQL error log

Hello,
We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
the following error recently:
Sleeping until external dump process completes.
Resuming after waiting on external debug process for 12 seconds.
Stack Signature for the dump is 0x00000000
Error: 17883, Severity: 1, State: 0
Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
Scheduler 0.
We also get error like below daily:
SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
than 15 seconds to complete on file [E:\Microsoft SQL
Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
handle is 0x0000053C. The offset of the latest long IO is: 0x00000000010000
The SQL server is used as data warhouse server, so there are a lots of IO.
I appreciate any suggestions or comments.
Thanks!
Sugarhigh,
For 17883 here is a whitepaper
http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx#ELDAC
For your IO issues:
http://support.microsoft.com/kb/897284
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx
Basically, you need to investigate your hardware utilization, particularly
(as you might expect) measuring your IO subsystem which sounds like it is
strained. Most likely you will need to do some upgrades to your equipment.
RLF
"Sugarhigh" <sugarhigh@.community.nospam> wrote in message
news:EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com...
> Hello,
> We have a SQL server 2000 enterprise edition on SP4 on windows NT, and got
> the following error recently:
> Sleeping until external dump process completes.
> Resuming after waiting on external debug process for 12 seconds.
> Stack Signature for the dump is 0x00000000
> Error: 17883, Severity: 1, State: 0
> Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
> Scheduler 0.
> We also get error like below daily:
> SQL Server has encountered 5359 occurrence(s) of IO requests taking longer
> than 15 seconds to complete on file [E:\Microsoft SQL
> Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
> handle is 0x0000053C. The offset of the latest long IO is:
> 0x00000000010000
> The SQL server is used as data warhouse server, so there are a lots of IO.
> I appreciate any suggestions or comments.
> Thanks!
|||Hello,
Thank you for posting here.
To better understand the error message, you must first understand how SQL
Server uses a User Mode Scheduling (UMS) Ums.dll helper file.
Microsoft SQL Server 2000 use logical schedulers. These schedulers help to
make sure that SQL Server maximizes operating system resource usage in
relation to key database action paths. The UMS layer makes sure that SQL
Server correctly uses Win32 events to strictly control thread and fiber (or
both) scheduling visibility to the operating system. By strictly
controlling the threads or fibers that can run, SQL Server can maximize CPU
usage as it relates to database primitives such as locking.
For example, logical scheduling permits lock waiters to sleep
(WaitForSingleObject on a Win32 event) until the lock owner releases the
lock and signals (SetEvent) them to wake up.
For more information, please refer to the following article:
New concurrency and scheduling diagnostics added to SQL Server (319892)
http://support.microsoft.com/default.aspx?scid=KB;EN-US;319892
Note: The format of the 17833 message is different for separate versions of
the SQL Server product; however, the meaning is the same.
However, to find out the root cause of this issue we may need to analyze
memory dumps, this work has to be done by contacting Microsoft Product
Support Services. Therefore, we probably will not be able to resolve the
issue through the newsgroups. If the issue is urgent, I recommend that you
open a Support incident with Microsoft Product Support Services so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
At the same time, please also ensure that latest update for SQL Server 2000
Service Pack 4 has been installed. We can download it from the following
website:
Cumulative Hotfix for SQL Server 2000 Service Pack 4 - Build 2187 for x86
and x64 Based Systems
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=9c9a
b140-bdee-44df-b7a3-e6849297754a
More related information:
=======================
892840FIX: 17883 errors may be written to the SQL Server error log when
you run a query that generates many floating point exception errors in SQL
Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;892840
810885High-end disk subsystems may experience error 17883
http://support.microsoft.com/default.aspx?scid=kb;EN-US;810885
888666You may receive a 17883 error message when you run full-text queries
in SQL Server 7.0 or SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;888666
890730FIX: You receive a 17883 error message when you perform large
in-memory sort operations in SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;890730
Have a nice day!
Best regards,
Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Error 17883 in SQL error log
| thread-index: AcfVM7K5Tj5qumliSs2GiuzWV3+hMQ==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?U3VnYXJoaWdo?= <sugarhigh@.community.nospam>
| Subject: Error 17883 in SQL error log
| Date: Thu, 2 Aug 2007 11:34:02 -0700
| Lines: 23
| Message-ID: <EBD8AFCC-B391-4E6C-A341-0BD5A4D62903@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.sqlserver.server
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.server:21828
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Hello,
|
| We have a SQL server 2000 enterprise edition on SP4 on windows NT, and
got
| the following error recently:
|
| Sleeping until external dump process completes.
| Resuming after waiting on external debug process for 12 seconds.
| Stack Signature for the dump is 0x00000000
| Error: 17883, Severity: 1, State: 0
| Process 1:0 (9d4) UMS Context 0x002977F8 appears to be non-yielding on
| Scheduler 0.
|
| We also get error like below daily:
| SQL Server has encountered 5359 occurrence(s) of IO requests taking
longer
| than 15 seconds to complete on file [E:\Microsoft SQL
| Server\Data\DBAUtility.mdf] in database [DBAUtility] (14). The OS file
| handle is 0x0000053C. The offset of the latest long IO is:
0x00000000010000
|
| The SQL server is used as data warhouse server, so there are a lots of
IO.
|
| I appreciate any suggestions or comments.
|
| Thanks!
|