The scenario that is described in this article applies to a select group of less than 200 customers worldwide who received 26 recent hotfixes for Microsoft Windows Server 2003 Service Pack 1 (SP1) between October 2006 and January 2007. These 26 hotfixes are incompatible with Microsoft Windows Server 2003 Service Pack 2 (SP2). These hotfixes should be replaced with new hotfixes before you install Windows Server 2003 SP2.
Typically, most customers will have only one or two of these specific hotfixes deployed in their environment.
Most customers who received these incompatible hotfixes have already been notified by Microsoft. This Knowledge Base article is published to make sure that customers who could not be contacted directly are informed so that they can take necessary action.
During the final testing for a service pack, it is not always possible to incorporate every individual hotfix into the service pack. If new hotfixes were incorporated every day, the final testing date would have to be reset. Additionally, it would lead to a situation in which the service pack final testing could never be completed. Instead, there is a short lockdown phase where newly issued hotfixes are not included in the service pack.
However, the service pack may contain a later version of a specific file than the hotfix. One option is to stop issuing hotfixes during the final phases of a service pack. This option has a significant business effect on corporations that require a new hotfix. A second option is to re-release these hotfixes after the service pack is released. This option incorporates any final service pack fixes and has a later version number than the service pack version of the file. Microsoft uses this second option. However, this second option means that some enterprises have to take extra steps when they deploy a new service pack. This is a one-time event for a service pack. It affects a fixed and well-defined set of hotfixes, and these hotfixes are documented at the release.
For Windows Server 2003 SP2, there are 26 specific hotfixes that must be reinstalled either before or after you install the service pack. To install Windows Server 2003 SP2, the recommended procedure is to first install the reissued hotfixes. Then, install Windows Server 2003 SP2 at a time that is convenient for you. The hotfixes will automatically migrate to the SP2 version of the hotfix.
If Windows Server 2003 SP2 is installed without replacing these hotfixes, the installation will complete successfully. However, the behavior fix that is previously provided by the hotfix will not be present after SP2 installation.
This issue does not affect any Windows Server 2003 hotfixes that are available publicly, either from the Microsoft Download Center or from the Windows Update Web site. This includes Windows Server 2003 security updates. This issue is limited to these 26 hotfixes that were made available only from Microsoft Customer Support to specific customers. Microsoft typically informs these customers when we deliver these hotfixes.
If you have been notified by Microsoft or if you know that you have installed any of the hotfixes that are listed in this article after October 2006, contact Microsoft to obtain the updated hotfix packages. The new hotfix packages can be deployed on a Windows Server 2003-based computer that has either SP1 or SP2 installed. You can install the hotfix packages either before you deploy SP2 or after SP2 is fully installed.
Before Windows Server 2003 SP2 was released, extensive testing was performed to make sure that all the included fixes and updates worked correctly. During the time before Windows Server 2003 SP2 was released, new customer-requested hotfixes were not incorporated into SP2 to enable the SP2 code base to be stabilized and released. For customers who needed solutions immediately in that time period, Microsoft released these fixes. These fixes were designed to be installed only in Windows Server 2003 SP1.
New packages for the 26 affected hotfixes are now available from Microsoft. The new hotfixes are suitable for installation together with both SP1 and SP2. After the affected hotfixes are replaced by the new packages, you can install SP2 at your convenience.
The following table lists the Microsoft Knowledge Base articles that correspond to versions of hotfixes that are incompatible with Windows Server 2003 SP2. Also, this table lists the Knowledge Base articles that correspond to the repackaged versions of the affected hotfixes.
Collapse this tableExpand this table
|Original article number||Replacement article number||Replacement article title|
||FIX: Internet Explorer 6 may unexpectedly close when you try to use digest proxy authentication to connect to secure (HTTPS) Web sites|
||The battery power drains more quickly than you expect from a Windows XP SP2-based portable computer or from a Windows Server 2003 SP1-based portable computer|
||You can no longer put the computer in standby or in hibernation after you disable a wireless network adapter's WakeUp feature in Windows Server 2003|
||Snapshot volumes do not mount successfully or the volume dismount operation reports an error when you use a Network Appliance storage device with the Windows Server 2003 Virtual Disk Service|
||You receive an error message when you try to open the Properties dialog box for a shared printer on a Windows Server 2003-based computer|
||The computer stops responding when you use a USB device on a multiprocessor computer that is running Windows Server 2003|
||You receive a warning message that does not correctly describe the password requirements when you set a new password that does not meet the requirements in Windows Server 2003|
||Error code when you run a network program that uses a Winsock connection on a computer that is running Windows Server 2003: "WSAECONNABORTED (10053)"|
||FIX: The AutoComplete box in an iframe object may not appear in the correct location in Internet Explorer 6|
||WMI does not clear event registrations when the corresponding sink becomes invalid in Windows Server 2003|
||Memory leak in the Lsass.exe process after you enable the Active Directory Lookup feature on a Windows Server 2003 R2-based computer|
||Windows Server 2003 may not start when the Volume Shadow Copy Service is enabled|
||Error message on a Windows Server 2003 SP1 or SP2-based computer that is configured to use the Network Address Translation (NAT) functionality: "STOP: 0x000000D1 (parameter1 , 0x00000002, 0x00000000, 0xf27b4e8e)"|
||SQL Server 2000 Service Pack 4 stops responding after you close a SQL Server connection on a computer that is running Windows Server 2003 Service Pack 1|
||Windows Server 2003 cluster node stops responding and failover to another node does not occur|
||Error message when you attach a device that loads the Serscan.sys driver to a computer that is running Windows Server 2003 Service Pack 2: "STOP: 0x000000c9 DRIVER_VERIFIER_IOMANAGER_VIOLATION"|
||The heavy use of Winsock programs may exhaust the "nonpaged pool memory" of a Windows Server 2003-based computer|
||Error message when you run a program that uses the QueryDosDeviceA function: “ERROR_MORE_DATA”|
||The "Dfsutil /import" command takes a long time to finish when you run this command to import DFS links to a stand-alone DFS root on a Windows Server 2003-based computer|
||The Local Security Authority Service (Lsass.exe) process shows extensive memory usage and then stops responding on Windows Server 2003-based domain controllers that are part of a cluster environment|
||You may experience increased paging to the hard disk when you run an SAP R/3 program on a Windows Server 2003-based computer|
||Error received when you deploy a security template together with an unattended installation of Windows Server 2003 R2: "-2147467259"|
||Claims that are added by a "claims transform" module on a Windows Server 2003 SP2-based computer are missing when you switch to a Windows NT token-based application|
||System calls that are made to serial devices may fail when you use the SUA UNIX interoperability component on a Microsoft Windows Server 2003 R2-based computer|
||Description of the Jet 4.0 Database Engine post-Windows Server 2003, post-Windows Server 2003 SP1, and post-Windows Server 2003 SP2 hotfix package: March 5, 2007|
Microsoft has released a tool that can be used to help customers who have deployed the incompatible hotfixes in their environments. The tool helps manage the detection and the deployment of the revised versions of these hotfixes. This tool can be used to detect specific servers that have one or more of these hotfixes installed. This tool can also be used to verify that all the replacement hotfixes have been fully redeployed. Do not run this tool if you have not installed any of the hotfixes that are identified in this article. If you have been explicitly notified by Microsoft or if you know that you asked for and received one of the incompatible fixes between October 2006 and January 2007, you may find this tool useful to manage and to track your remediation. Note
This article applies to less than 200 customers. Microsoft has already taken proactive steps to contact them directly.
Earlier versions of Windows, such as Microsoft Windows 2000, included this tool as a setup blocklist in the service pack installer. However, the service pack had to be deployed to individual servers to detect if the specific hotfixes were present. There was no easy way to verify that servers were compliant before you deployed the service pack. During a scheduled installation, if one of the hotfixes was encountered, the service pack installation would be stopped.
The separate tool provides a better solution in managed environments. Additionally, because this issue affects only some individual customers, building detection into the service pack for every customer adds increased complexity.
For more information about a tool to scan the computer for hotfixes that block the installation of Windows Server 2003 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
The Hotfix Scan Tool is available to scan for regressed hotfixes that are caused by the Windows Server 2003 Service Pack 2 installation