Files are corrupted on a Windows Server 2003-based computer when you try to use the local UNC path to copy the files

Consider the following scenario. You try to use the local Universal Naming Convention (UNC) path to copy a file that is larger than 16,705 bytes from a local disk to a local share. You use a computer that is running Microsoft Windows Server 2003 with Service Pack 1 (SP1). The file that you copy to the share is then corrupted. The data corruption appears in the Server Message Block (SMB) header that is embedded in the data of the destination file.

Furthermore, only the destination file appears corrupted, not the source file. The content of the destination file shows the following characters: These characters translate to an "SMB WRITE AndX" request.

For example, this problem may occur when Microsoft CRM publishes changes to the local Web server by copying the files to the following folder: In this scenario, the published files that are copied into the Wwwroot folder may be corrupted, and the CRM application may stop working.

Note This problem is most likely to occur on CRM Web servers. However, the problem may also occur on any Windows Server 2003-based computer.

This problem may occur if you have installed Internet Protocol version 6 (IPv6) on a computer that is running Windows Server 2003 with SP1.

Update information

The following files are available for download from the Microsoft Download Center:

Update for Windows Server 2003 (KB911897)Update for Windows Server 2003 for Itanium-based Systems (KB911897)Update for Windows Server 2003 x64 Edition (KB911897)Update for Windows XP x64 Edition (KB911897) Release Date: December 12, 2006

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To apply this update, you must have Microsoft Windows Server 2003 SP1 installed.

Restart requirement

You must restart the computer after you apply this update unless you are running Windows Server 2003 Service Pack 1 (SP1). This update supports HotPatching. With HotPatching, you can install updates on a computer that is running Windows Server 2003 SP1 without restarting the computer. For more information about HotPatching and about how to deploy an update by using HotPatching, click the following article number to view the article in the Microsoft Knowledge Base: The update that is available on Windows Update, Microsoft Update, and Automatic Update uses HotPatching and does not require that you restart the computer. Notice that not all updates support HotPatching, and that some updates that support HotPatching might require that you restart the computer after you install the update. HotPatching is supported only if the files that are being replaced by the update are General Distribution Release (GDR) files.

Update replacement information

This update does not replace any other updates.

File information

The English version of this update 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.

Windows Server 2003, 32-bit editions

Windows Server 2003, 64-bit editions

Windows Server 2003, Itanium-based systems IA-64

To work around this problem, uninstall IPv6.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about this topic, click the following article number to view the article in the Microsoft Knowledge Base: