Microsoft KB Archive/913991

= FIX: Hotfix files may not be copied to remote nodes when you install a 32-bit hotfix, and hotfix files may not be removed from remote nodes on a computer that is running SQL Server 2000 in an MSCS environment =

Article ID: 913991

Article Last Modified on 6/19/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Enterprise Edition

-



Bug: #317 (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 applying the hotfix package
 * Information about whether you must restart the computer after you apply 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 after you apply the hotfix package
 * The files that are contained in the hotfix package



SYMPTOMS
When you install a 32-bit hotfix on a computer that is running SQL Server 2000 in a Microsoft Cluster Service (MSCS) environment, the Sqlservr.exe file and other hotfix files may not be copied to the remote nodes in the SQL Server 2000 cluster. When this problem occurs, you may not receive any error messages. Additionally, when you try to uninstall a 32-bit hotfix, the installed files may not be removed from the remote nodes. This problem causes different versions of the Sqlservr.exe file to exist on each cluster node.

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

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 SP4



CAUSE
This problem occurs because the remote nodes cannot run the Task Scheduler Service task that is created by the hotfix installer. The SQL Server 2000 32-bit hotfix installer creates the Task Scheduler Service task on remote nodes to install and to uninstall the hotfix files. The task cannot run on remote nodes because the user name to run the task is corrupted.



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.

To resolve this problem, install a hotfix on all cluster nodes.

Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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:

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 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 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 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.



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



MORE INFORMATION
For more information, 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

Keywords: kbexpertiseadvanced kbtshoot kbfix kbhotfixserver kbqfe kbpubtypekc KB913991

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.