Microsoft KB Archive/929410

= FIX: Error message when you run a full-text query in SQL Server 2000: &quot;Error: 17883, Severity: 1, State: 0&quot; =

Article ID: 929410

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Desktop Engine (Windows)
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Workgroup Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition 64-bit

-



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.



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package
 * The prerequisites for installing the hotfix package
 * Information about whether you must restart the computer after you install the hotfix package
 * Information about whether the hotfix package is replaced by any other hotfix package
 * Information about whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
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:

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!

For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, see the following article in the Microsoft Knowledge Base:

810185 SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a



RESOLUTION
The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
 * The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.

Note This issue does not occur on systems that use the Intel Itanium processor architecture.
 * The system is running a 64-bit version of the Microsoft Windows Server operating system.
 * The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
You 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:

290211 How to obtain the latest SQL Server 2000 service pack

Restart information
If the file is being used, you must restart the computer after you apply this hotfix.

Registry information
You do not have to change the registry.

Hotfix file information
This 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.



WORKAROUND
To work around this problem, use the following guidelines when you maintain full-text catalogs.
 * Avoid incremental updates to the catalog. Instead, use change tracking to apply the full-text index changes.
 * Disable background updates. To do this, run the sp_fulltext_table stored procedure together with the stop_background_updateindex option. Do not use background updates. Instead, use the update_index option at a scheduled time to apply the full-text index changes.
 * Use the FULLTEXTCATALOGPROPERTY function to monitor the status of the catalog.
 * Use the sp_fulltext_service stored procedure together with the resource_usage option to increase the resource usage to a level of 5. The level specifies the resources that are used for the Microsoft Search Service (MSSearch). When you increase the resource_usage value, faster catalog builds occur.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



Stack information
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]

