Select the product you need help with
FIX: Error message 17883 may be logged in the error log when you try to manually update table statistics in SQL Server 2000Article ID: 909380 - View products that this article applies to. Bug #: 474380 (SQL Server 8.0) Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release. On This PageSUMMARYThis article
describes the following about this hotfix release:
SYMPTOMSWhen you try to manually update table statistics in Microsoft SQL Server 2000, the
following message may be logged in the SQL Server error log:
DateTime
server Error: 17883, Severity: 1, State: 0
DateTime server Process 905:0 (19c4) UMS Context 0x0000000053E318F0 appears to be non-yielding on Scheduler 11. DateTime server Error: 17883, Severity: 1, State: 0 DateTime server Process 916:0 (2ca8) UMS Context 0x0000000053E612F0 appears to be non-yielding on Scheduler 24. DateTime server Error: 17883, Severity: 1, State: 0 DateTime server Process 643:0 (236c) UMS Context 0x0000000053E73EB0 appears to be non-yielding on Scheduler 39. Note Typically, this problem occurs on an IA-64 architecture-based computer. For a list of previous hotfixes, see the "Microsoft SQL Server 2000 Service Pack 4" section in the following Microsoft Knowledge Base article: 290211
(http://support.microsoft.com/kb/290211/
)
How to obtain the most recent SQL
Server 2000 service pack
RESOLUTIONThe installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesYou must have Microsoft SQL Server 2000 Service Pack 4 (SP4) installed to apply this hotfix. For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:290211
(http://support.microsoft.com/kb/290211/
)
How to obtain the latest SQL Server 2000 service pack
Restart informationYou do not have to restart the computer after you apply this hotfix. However, the hotfix installation stops and then restarts the MSSQLSERVER service.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. SQL Server 2000, 32-bit versionsCollapse this table
SQL Server 2000, Itanium architecture versionCollapse this table
STATUSMicrosoft has confirmed that this is a
bug in the Microsoft products that are listed in the "Applies to"
section. MORE INFORMATION
For more information about the naming
schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
For more information about the terminology that Microsoft uses when it corrects software after the software is released, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New
naming schema for Microsoft SQL Server software update packages
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe
Microsoft software updates
Properties |



Back to the top








