Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Cluster nodes may stop responding if you move cluster resources from one node to another after you upgrade a Windows Server 2003 SP1-based computer to Windows Server 2003 R2


View products that this article applies to.

Symptoms

After you upgrade a Microsoft Windows Server 2003 Service Pack (SP1)-based computer to Microsoft Windows Server 2003 R2, cluster nodes may stop responding if you move cluster resources from one node to another.

↑ Back to the top


Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information

A 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.To resolve this problem, apply this hotfix to all nodes of the cluster.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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.
Microsoft Windows Server 2003, x86-based versions with Service Pack 1
File nameFile versionFile sizeDateTimePlatformSP requirement
Ntkrnlmp.exe5.2.3790.25342,454,52823-Sep-200509:34Not ApplicableSP1
Ntkrnlpa.exe5.2.3790.25342,268,16023-Sep-200509:09x86SP1
Ntkrpamp.exe5.2.3790.25342,308,60823-Sep-200509:09Not ApplicableSP1
Ntoskrnl.exe5.2.3790.25342,416,64023-Sep-200509:34x86SP1

Microsoft Windows Server 2003, Itanium-based versions with Service Pack 1
File nameFile versionFile sizeDateTimePlatform
Ntkrnlmp.exe5.2.3790.25346,486,52823-Sep-200501:59IA-64

Microsoft Windows Server 2003, x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirement
Ntkrnlmp.exe5.2.3790.25344,418,56023-Sep-200502:00x64SP1
Ntoskrnl.exe5.2.3790.25344,446,20823-Sep-200502:00x64SP1

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows Server 2003 Service Pack 2.

↑ Back to the top


More information

This hotfix also addresses a crash condition that causes a "stop 0x50" error. The condition occurs because the configuration manager generates incorrect mappings after a coalesce operation.

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

Technical support for x64-based versions of Microsoft Windows

Your hardware manufacturer provides technical support and assistance for x64-based versions of Windows. Your hardware manufacturer provides support because an x64-based version of Windows was included with your hardware. Your hardware manufacturer might have customized the installation of Windows with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your x64-based version of Windows. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:

↑ Back to the top


Keywords: kbautohotfix, kbwinserv2003sp2fix, kbhotfixserver, kbqfe, KB908249

↑ Back to the top

Article Info
Article ID : 908249
Revision : 4
Created on : 10/9/2011
Published on : 10/9/2011
Exists online : False
Views : 500