Article ID: 929410 - View products that this article applies to.
Bug: #50000592 (SQL Hotfix)
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.
This article describes the following about this hotfix release:
When you run a full-text query in SQL Server 2000 while a catalog merge operation also occurs, the result set may not return quickly. When this delay occurs, the SQL Server User Mode Scheduler (UMS) may stop responding. Additionally, you may experience stalled worker request behavior.
When this problem occurs, you may receive an error message that resembles the following:
For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, see the following article in the Microsoft Knowledge Base:
Error: 17883, Severity: 1, State: 0 The Scheduler %1!ld! appears to be hung. SPID %2!ld!, ECID %3! ld!, UMS Context 0x%4!p!
(http://support.microsoft.com/kb/810185/ )SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a
The 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:
PrerequisitesYou must have Microsoft SQL Server 2000 Service Pack 3 (SP3) installed to apply this hotfix.
For information about how to obtain SQL Server 2000 service packs, see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/ )How to obtain the latest SQL Server 2000 service pack
Restart informationIf the file is being used, you must restart the computer after you apply this hotfix.
Registry informationYou do not have to change the registry.
Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of 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 item in Control Panel.
SQL Server 2000 32-bit versions
Note Because of file dependencies, the most recent hotfix or feature that contains these files may contain additional files.
Collapse this tableExpand this table
To work around this problem, use the following guidelines when you maintain full-text catalogs.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
177eaea0 77f43741 77e41817 00000dd0 00000000 SharedUserData!SystemCallStub+0x4 177eaea4 77e41817 00000dd0 00000000 00000000 ntdll!NtWaitForSingleObject+0xc [d:\srv03rtm\base\ntdll\daytona\obj\i386\usrstubs.asm @ 2371] 177eaf14 77e4168f 00000dd0 ffffffff 00000000 kernel32!WaitForSingleObjectEx+0xac [d:\srv03rtm\base\win32\client\synch.c @ 1237] 177eaf24 77e5e9d5 00000dd0 ffffffff 14fd1f68 kernel32!WaitForSingleObject+0xf [d:\srv03rtm\base\win32\client\synch.c @ 1138] 177eaf34 14ec99fa 000027b0 14fd1f74 177eb01c kernel32!GetOverlappedResult+0x27 [d:\srv03rtm\base\win32\client\error.c @ 597] 177eaf68 14ec9e92 177eb020 00000014 177eb000 tquery!CPipeClient::TransactSync+0x5e [d:\s20_main\babylon\tripoli\common\crequest.cxx @ 283] 177eafd4 14ed204a 000000ed 00000014 177eb000 tquery!CRequestClient::DataWriteRead+0x15d [d:\s20_main\babylon\tripoli\common\crequest.cxx @ 1107] 177eb04c 14e9d543 00000001 177eb07c 14e47bb8 tquery!CSvcQueryProxy::GetRowsStatistics+0x43 [d:\s20_main\babylon\tripoli\bigtable\svcproxy.cxx @ 532] 177eb0ac 14e9f754 00000001 18c704d8 00000000 tquery!CSvcQuery::GetRowsetStatistics+0x12f [d:\s20_main\babylon\tripoli\icommand\svcquery.cxx @ 503] 177eb320 14642e29 18c704d8 00000000 177ec954 tquery!CRootQuerySpec::Execute+0x567 [d:\s20_main\babylon\tripoli\icommand\qryspec.cxx @ 884] 177ec0d4 00707378 18c704e0 00000000 15000064 sqlftqry!FTGetRowsetInterface+0x1219 [p:\sql\ntdbms\msql\fulltext\src\ftqry\sqlqry.cpp @ 957] 177ec948 00706b16 00000000 21c3f4c2 404f02df sqlservr!CFullTextRange::GetRowsetInterface+0x39e [T:\shiloh\sql\ntdbms\msql\utils\sqlftqry.cpp @ 1642] 177ed114 00706ed6 435b2020 000003e8 00000000 sqlservr!CFullTextRange::GetBinding+0x522 [T:\shiloh\sql\ntdbms\msql\utils\sqlftqry.cpp @ 1328] 177ed520 004855ea 435b2020 435b2a28 177ed5ac sqlservr!CFullTextRange::DoNormalize+0x27e [T:\shiloh\sql\ntdbms\msql\utils\sqlftqry.cpp @ 1438] 177ed530 00485809 435b2020 435b2a28 435b2188 sqlservr!COledbRange::Normalize+0x38 [T:\shiloh\sql\ntdbms\msql\utils\oledbrng.cpp @ 3370] 177ed5ac 0045e61b 435b23e8 00000000 00000000 sqlservr!CAlgTable::FBind+0x16e [T:\shiloh\sql\ntdbms\msql\norm\colnames.cpp @ 4595] 177ed5f0 0045e732 00000002 00000000 435b2140 sqlservr!FOpenAllRanges+0xdd [T:\shiloh\sql\ntdbms\msql\norm\colnames.cpp @ 4457]
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:
822499For 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
824684For more information about full-text queries in SQL Server, visit the following Microsoft Developer Network (MSDN) Web site:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
http://msdn2.microsoft.com/en-us/library/aa172861(SQL.80).aspxFor more information about how to optimize SQL Server full-text indexing, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/library/aa175787(SQL.80).aspxFor more information about this issue, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/319892/ )New concurrency and scheduling diagnostics have been added to SQL Server
(http://support.microsoft.com/kb/888666/ )You may receive a 17883 error message when you run full-text queries in SQL Server 7.0 or SQL Server 2000
Article ID: 929410 - Last Review: November 2, 2007 - Revision: 3.4