Article ID: 890043
Article Last Modified on 11/2/2007
APPLIES TO
- Microsoft SQL Server 2000 Enterprise Edition 64-bit
- 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
BUG #: 473094 (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.
SUMMARY
This article describes the following about this hotfix release:
- The issues that are fixed by the hotfix package
- The prerequisites for installing the hotfix package
- Whether you must restart the computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix package
SYMPTOMS
Consider the following scenario:
- You run Microsoft SQL Server 2000 together with the full-text search component.
- You start the Microsoft PKM Search Filter Daemon (Mssdmn.exe) to parse Microsoft Office Word documents.
In this scenario, the PKM Search Filter Daemon may unexpectedly crash. The PKM Search Filter Daemon may crash whenever a partial catalog population is started. Therefore, Word documents are not successfully filtered.
For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
810185 SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a
CAUSE
This problem occurs because the PKM Search Filter Daemon crashes when the PKM Search Filter Daemon tries to filter certain corrupted Word documents. In this scenario, when the PKM Search Filter Daemon tries to filter certain Word documents, the PKM Search Filter Daemon recursively calls a particular Office filter method. This method is called in an unending loop until the PKM Search Filter Daemon crashes.
In this scenario, temporary documents from the SQL binary stream remain on the hard disk. These temporary documents remain because the Mssdmn.exe process crashes before the code to remove the temporary documents is reached.
Note If you experience this problem, a .doc file remains in the folder that is specified in the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\FullTextDefaultPath
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, but it is only intended to correct the problem that is described in this article. Only apply it 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 SQL Server 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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
- Microsoft SQL Server 2000 Service Pack 3 (SP3)
For information about how to obtain SQL Server 2000 SP3, click the following article number to view the article in the Microsoft Knowledge Base:290211 How to obtain the latest SQL Server 2000 service pack
Restart information
You do not have to 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 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.
Date Time Version Size File name -------------------------------------------------------- 04-Aug-2004 04:33 6.1.9.0 20,480 Sprecovr.exe 04-Aug-2004 04:33 6.1.9.0 15,872 Spupdsvc.exe 29-Nov-2004 23:54 11.0.6715.19 125,136 Offfilt.dll 18-Nov-2004 17:45 6.1.22.0 371,936 Updspapi.dll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about the naming schema for 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 Microsoft corrects software after it 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
Additional query words: FTS Full-Text Search Population
Keywords: kbbug kbfix kbqfe kbhotfixserver KB890043
