Files are corrupted on a Windows Server 2003-based computer when you try to use the local UNC path to copy the files (911897)
The information in this article applies to:
- Microsoft Windows Server 2003 SP1, when used with:
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, 64-Bit Enterprise Edition
SYMPTOMSConsider 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 Microsoft Windows Server 2003 Service Pack 1(SP1)-based computer. 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: "FF 53 4D 42 2F." 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: \\Server_Name\C$\Inetpub\Wwwroot 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. CAUSEThis problem may occur if you have installed Internet Protocol version 6 (IPv6) on a Windows Server 2003 SP1-based computer.RESOLUTIONHotfix informationA 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 Windows Server 2003 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. PrerequisitesMicrosoft Windows Server 2003 Service Pack 1 Restart requirementYou must restart your computer after you apply this hotfix. Hotfix replacement informationThis 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. Windows Server 2003, 32-bit editions
|
| Smb.sys | 5.2.3790.2596 | 59,392 | 20-Dec-2005 | 02:34 | x86 |
Windows Server 2003, 64-bit editions
|
| Smb.sys | 5.2.3790.2596 | 99,328 | 19-Dec-2005 | 19:46 | x64 |
Windows Server 2003, Itanium-based systems IA-64
|
| Smb.sys | 5.2.3790.2596 | 193,024 | 19-Dec-2005 | 19:46 | IA-64 |
WORKAROUNDTo work around this problem, uninstall IPv6.STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
| Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
|---|
| Keywords: | kbHotfixServer kbExpertiseInter kbWinServ2003preSP2fix kbBug kbfix kbQFE kbpubtypekc KB911897 kbAudITPRO |
|---|
|