Microsoft KB Archive/929410

From BetaArchive Wiki

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:

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
File name File version File size Date Time Platform
Autoplt.dll 2000.80.1036.0 664,128 06-Dec-2006 04:10 x86
Console.exe 2000.80.1036.0 78,400 06-Dec-2006 04:10 x86
Ctasksui.dll 2000.80.1036.0 332,352 06-Dec-2006 04:10 x86
Custtask.dll 2000.80.1036.0 315,968 06-Dec-2006 04:10 x86
Dbmslpcn.dll 2000.80.1036.0 33,340 06-Dec-2006 04:10 x86
Distmdl.ldf Not Applicable 786,432 14-Apr-2005 09:17 Not Applicable
Distmdl.mdf Not Applicable 2,359,296 14-Apr-2005 09:17 Not Applicable
Drop_repl_hotfix.sql Not Applicable 180 14-Apr-2005 09:17 Not Applicable
Dtspkg.dll 2000.80.1036.0 1,905,216 06-Dec-2006 04:10 x86
Dtspump.dll 2000.80.1036.0 528,960 06-Dec-2006 04:10 x86
Dtsui.dll 2000.80.1036.0 1,557,052 06-Dec-2006 04:10 x86
Dtswiz.dll 2000.80.1036.0 639,552 06-Dec-2006 04:10 x86
Impprov.dll 2000.80.1036.0 102,992 06-Dec-2006 04:10 x86
Instdist.sql Not Applicable 747,927 14-Apr-2005 09:17 Not Applicable
Inst_repl_hotfix.sql Not Applicable 1,581 14-Apr-2005 09:17 Not Applicable
Isqlw.exe 2000.80.1036.0 352,828 06-Dec-2006 04:10 x86
Itwiz.exe 2000.80.1036.0 82,492 06-Dec-2006 04:10 x86
Msgprox.dll 2000.80.1036.0 90,692 06-Dec-2006 04:10 x86
Mssdi98.dll 8.11.41022.0 226,304 14-Apr-2005 08:59 x86
Odsole70.dll 2000.80.1036.0 62,024 06-Dec-2006 04:10 x86
Opends60.dll 2000.80.1036.0 25,144 06-Dec-2006 04:11 x86
Osql.exe 2000.80.1036.0 57,904 06-Dec-2006 04:10 x86
Pfutil80.dll 2000.80.1036.0 279,104 06-Dec-2006 04:10 x86
Procsyst.sql Not Applicable 551,012 14-Apr-2005 09:13 Not Applicable
Qfe469315.sql Not Applicable 12,305 14-Apr-2005 09:17 Not Applicable
Qfe469571.sql Not Applicable 19,195 14-Apr-2005 09:17 Not Applicable
Qfe472197.sql Not Applicable 5,157 14-Apr-2005 09:17 Not Applicable
Qrdrsvc.exe 2000.80.1036.0 143,940 06-Dec-2006 04:10 x86
Replmerg.sql Not Applicable 1,136,160 06-Dec-2006 03:01 Not Applicable
Replprov.dll 2000.80.1036.0 221,768 06-Dec-2006 04:10 x86
Replrec.dll 2000.80.1036.0 307,784 06-Dec-2006 04:10 x86
Replres.rll 2000.80.1036.0 159,813 06-Dec-2006 03:05 Not Applicable
Replsys.sql Not Applicable 1,088,240 14-Apr-2005 09:17 Not Applicable
Repltran.sql Not Applicable 986,746 14-Apr-2005 09:17 Not Applicable
Repl_uninstall.sql Not Applicable 55 14-Apr-2005 09:17 Not Applicable
Rinitcom.dll 2000.80.1036.0 287,304 06-Dec-2006 04:10 x86
Sdiclnt.dll 2000.80.1036.0 78,416 06-Dec-2006 04:10 x86
Semexec.dll 2000.80.1036.0 823,872 06-Dec-2006 04:10 x86
Semmap.dll 2000.80.1036.0 66,112 06-Dec-2006 04:10 x86
Semnt.dll 2000.80.1036.0 57,916 06-Dec-2006 04:10 x86
Semobj.dll 2000.80.1036.0 492,096 06-Dec-2006 04:10 x86
Semobj.rll 2000.80.1036.0 172,032 06-Dec-2006 03:20 Not Applicable
Snapshot.exe 2000.80.1036.0 53,832 06-Dec-2006 04:10 x86
Sp3_serv_uni.sql Not Applicable 125,540 14-Apr-2005 09:13 Not Applicable
Sqlagent.dll 2000.80.1036.0 28,672 06-Dec-2006 04:10 x86
Sqlagent.exe 2000.80.1036.0 311,872 06-Dec-2006 04:10 x86
Sqlakw32.dll 2000.80.1036.0 168,001 06-Dec-2006 04:10 x86
Sqlctr80.dll 2000.80.1036.0 33,344 06-Dec-2006 04:10 x86
Sqldiag.exe 2000.80.1036.0 90,112 06-Dec-2006 03:22 x86
Sqldmo.dll 2000.80.1036.0 4,215,360 06-Dec-2006 04:10 x86
Sqldumper.exe Not Applicable 25,172 06-Dec-2006 04:10 x86
Sqlevn70.rll 2000.80.1036.0 28,672 06-Dec-2006 03:00 Not Applicable
Sqlmaint.exe 2000.80.1036.0 156,224 06-Dec-2006 04:10 x86
Sqlmap70.dll 2000.80.1036.0 180,792 06-Dec-2006 04:10 x86
Sqlmmc.dll 2000.80.1036.0 188,992 06-Dec-2006 04:10 x86
Sqlmmc.rll 2000.80.1036.0 479,232 06-Dec-2006 03:22 Not Applicable
Sqlqry.dll 2000.80.1036.0 401,984 06-Dec-2006 04:10 x86
Sqlrepss.dll 2000.80.1036.0 57,920 06-Dec-2006 04:10 x86
Sqlservr.exe 2000.80.1036.0 7,725,137 06-Dec-2006 04:11 x86
Sqlsort.dll 2000.80.1036.0 590,396 06-Dec-2006 04:10 x86
Sqlvdi.dll 2000.80.1036.0 45,644 06-Dec-2006 04:10 x86
Sqsrvres.dll 2000.80.1036.0 106,588 06-Dec-2006 04:10 x86
Ssmsgnet.dll 2000.80.1036.0 33,340 06-Dec-2006 04:10 x86
Ssmslpcn.dll 2000.80.1036.0 33,340 06-Dec-2006 04:10 x86
Ssmsqlgc.dll 2000.80.1036.0 33,340 06-Dec-2006 04:10 x86
Ssnetlib.dll 2000.80.1036.0 82,492 06-Dec-2006 04:10 x86
Ssnmpn70.dll 2000.80.1036.0 25,148 06-Dec-2006 04:10 x86
Stardds.dll 2000.80.1036.0 123,456 06-Dec-2006 04:10 x86
Svrnetcn.dll 2000.80.1036.0 158,268 06-Dec-2006 04:10 x86
Svrnetcn.exe 2000.80.1036.0 76,416 06-Dec-2006 04:10 x86
Ums.dll 2000.80.1036.0 49,228 06-Dec-2006 04:11 x86
Xplog70.dll 2000.80.1036.0 74,304 06-Dec-2006 04:11 x86
Xpweb70.dll 2000.80.1036.0 98,872 06-Dec-2006 04:11 x86

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 "Applies to" section.

MORE INFORMATION

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]

REFERENCES

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 New naming schema for Microsoft SQL Server software update packages


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:

824684 Description of the standard terminology that is used to describe Microsoft software updates


For more information about full-text queries in SQL Server, visit the following Microsoft Developer Network (MSDN) Web site:

For more information about how to optimize SQL Server full-text indexing, visit the following MSDN Web site:

For more information about this issue, click the following article numbers to view the articles in the Microsoft Knowledge Base:

319892 New concurrency and scheduling diagnostics have been added to SQL Server


888666 You may receive a 17883 error message when you run full-text queries in SQL Server 7.0 or SQL Server 2000


Keywords: kbbug kbfix kbqfe kbhotfixserver KB929410