Re: Error: 17883, Severity: 1, State: 0

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

"Uttam Parui[MS]" wrote:

> 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
>
> This 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
>
>
>
.

Relevant Pages

  • Re: Error: 17883, Severity: 1, State: 0
    ... 17883 error message is a health detection message that can be triggered for many reasons. ... a MiniDump file is generated when SQL Server first detects a stalled scheduler. ... Review the minidump file or give it to Microsoft support to help determine the root cause of the problem. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Error: 17883, Severity: 1, State: 0
    ... Mike Epprecht, Microsoft SQL Server MVP ... >> MiniDump file for the life of the SQL Server process. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Win-2000 crashes
    ... I installed the windows debug tool and opened the minidump file. ... Copyright Microsoft Corporation. ... After setting your symbol path, use .reload to refresh symbol locations. ...
    (microsoft.public.win2000.general)
  • RE: Problem with OLAP
    ... Take the dbghelp.dll out of the sp3 for SQL server and put that into ... \microsoft analysis server\Bin\ folder. ... This will create a minidump file ...
    (microsoft.public.sqlserver.olap)
Loading