 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Clustering / August 2005Error: 17883, Severity: 1, State: 0
? All of the sudden our server was totally sown. The communication to it was down down. The errors from the SQL Serve Log were: -- Process 0:0 (a2c) UMS Context 0x125669D0 appears to be non-yielding on Scheduler 0. -- Error: 17883, Severity: 1, State: 0 Any articles?, any reasons whay this hapen? Thanks ------------------------------------ Arturo Hi One of the error checkers that was introduced in SQL Server 2000 SP3 to identify when one of the internal processes has not responded. It is a sign of a bug, and though this new error report, Microsoft has been able to track down most of the issues that would have resulted in a suspicious hang. A famous one is when a SAN device is so fast in initializing disk space when creating a DB, or growing it, that specific SPID just keeps looping and requesting more space, without giving up processing time to other SPIDS. There are a lot of fixes in post SP3 hot fixes, but it would be best for you to go directly to SP4. If you can not go to SP4, 8.00.0878 would be an option (http://support.microsoft.com/default.aspx?scid=kb;en-us;838166), but not really high enough. You need a hotfix over 8.00.0950, but those are only available from Microsoft Support. Regards -------------------------------- Mike Epprecht, Microsoft SQL Server MVP Zurich, Switzerland IM: mike@epprecht.net MVP Program: http://www.microsoft.com/mvp Blog: http://www.msmvps.com/epprecht/ > ? > All of the sudden our server was totally sown. The communication to it [quoted text clipped - 10 lines] > ------------------------------------ > Arturo Hello Arturo, 17883 error message is a health detection message that can be triggered for many reasons. You must determine the root cause of the 17883 error message if you want to avoid an unwanted reoccurrence of the error. Error 17883 is introduced in SQL Server 2000 SP3. The following information is the text of error 17883: Error: 17883 - The Scheduler %1!ld! appears to be hung. SPID %2!ld!, ECID %3! ld!, UMS Context 0x%4!p! In SQL Server 2000 build 8.00.765, the message text has been modified and is now more descriptive. The following information is the modified text of error 17883: Error: 17883 - Process %1!ld!:%2!ld! (%3!lx!) UMS Context 0x%4!p! appears to be non-yielding on Scheduler %5!ld! This fix has been included with the security patch for Microsoft Security Bulletin MS03-031 and Service Pack 4 for SQL Server 2000. Starting with build 8.00.765, a MiniDump file is generated when SQL Server first detects a stalled scheduler. To prevent continued generation of the MiniDump files for these error messages (17883 and17884), the default behavior is to produce a single MiniDump file for the life of the SQL Server process. To enable a MiniDump file for every occurrence of the messages, turn on trace flag -T1262. The MiniDump file is generated in the LOG folder and is SQLDmpr###.mdmp. Recommendation: 1. Apply security patch MS03-031 or SP4 for SQL Server 2000. This will produce minidump file when SQL Server first detects a stalled scheduler. 2. Review the minidump file or give it to Microsoft support to help determine the root cause of the problem. Additional Resource New concurrency and scheduling diagnostics added to SQL Server http://support.microsoft.com/default.aspx?scid=kb;en-us;319892 HTH, Best Regards, Uttam Parui Microsoft Corporation  SignatureThis posting is provided "AS IS" with no warranties, and confers no rights. Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security. Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites: http://www.microsoft.com/protect http://www.microsoft.com/security/guidance/default.mspx Hey Uttam, FYI.. We had a similar issue then we applied 818 patch didn't fix the problem.. Assuming this is fixed in SP4. Sree > Hello Arturo, > [quoted text clipped - 42 lines] > way to do this is to visit the following websites: http://www.microsoft.com/protect > http://www.microsoft.com/security/guidance/default.mspx Hi FYI, We saw a reduced number of these errors when going to 878, and even less with 952. Those servers will get 2040 next week so then time will only tell. Regards -------------------------------- Mike Epprecht, Microsoft SQL Server MVP Zurich, Switzerland IM: mike@epprecht.net MVP Program: http://www.microsoft.com/mvp Blog: http://www.msmvps.com/epprecht/ > Hey Uttam, > [quoted text clipped - 68 lines] >> http://www.microsoft.com/protect >> http://www.microsoft.com/security/guidance/default.mspx Sree, 17883 error message is a health detection message that can be triggered for MANY REASONS. Once we get the 17883 message, we need to determine the root cause of the 17883 message. 17883 message does not necessarily indicate that the issue is a SQL issue. It could be due to various reasons. Yeah, if it was due to a SQL issue and that issue is fixed in SP4 then you will not see it for that issue after applying SP4. So, coming to your qs "We ha d a similar issue then we applied 818 patch didn't fix the problem..Assuming this is fixed in SP4" --- What do you mean by a similar issue? Do you mean that you got the 17883 message? If yes, then that itself does not mean you have similar issue. This is a just a health detection message. To find the root cause, we will need to review the minidump that gets created after you have 818 patch. So, 818 patch does not fix the 17883 message because 17883 message is not an issue -- it is just an indicator. 818 did fix many other bugs and gave better error message and created mini dump when 17883 was generated. The mini dump is a starting point for troubleshooting. HTH, Best Regards, Uttam Parui Microsoft Corporation SignatureThis posting is provided "AS IS" with no warranties, and confers no rights. Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security. Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites: http://www.microsoft.com/protect http://www.microsoft.com/security/guidance/default.mspx When we had 17883 issue on our prod server we opened a ticket with MS and recommended to apply 818 that fixed the bug appraently that didn't fix the problem. When you say all sql issues are fixed in 17883 do you have list of things that triggers 17883 that are fixed in SP4? are they reproducable? Thanks, > Sree, > [quoted text clipped - 23 lines] > to do this is to visit the following websites: http://www.microsoft.com/protect > http://www.microsoft.com/security/guidance/default.mspx 818 build did have fix for some bugs in SQL that caused this message. Also, 818 creates a mini dump when the message is generated which helps in troubleshooting the issue. Sometimes minidumps are enough to find the root cause and sometimes it is not and in such a case we will need to take full dump. If you search Microsoft Knowledge base (http://support.microsoft.com) on error 17883, you will find a list of known issues that we know cause 17883 message. Again, is this a complete list of all possible things that can cause 17883 error ? 17883 is not an Error it is an indicator of an error and the root cause can be due to various reasons - thirdparty dlls, filter drivers, SQL bug <one can get a list of sql bugs that cause 17883 in Microsoft knowledge base and AFAIK all of them have been fixed>, etc. Best Regards, Uttam Parui Microsoft Corporation SignatureThis posting is provided "AS IS" with no warranties, and confers no rights. Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security. Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites: http://www.microsoft.com/protect http://www.microsoft.com/security/guidance/default.mspx |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.