Files saved to a mapped network share from Windows XP are corrupted (885936)
The information in this article applies to:
- Microsoft Windows XP Professional
- Microsoft Windows XP Home Edition
- Microsoft Windows XP Professional Service Pack 2 (SP2)
- Microsoft Windows XP Home Edition Service Pack 2 (SP2)
- Microsoft Windows XP Service Pack 1
SYMPTOMSWhen you try to save a file from a Microsoft Windows XP-based computer to a network share on a Windows-based server, the saved file may be corrupted. Typically, the saved file contains zeros in the end of the file instead of the expected data.CAUSEThis problem may occur when you use a program that memory maps a file that is not flagged for write caching, and a set end of file is received from the program. This problem occurs when one of the following conditions is true for the client computer that you use to save the file: - Microsoft Windows XP Service Pack 2 is installed.
- The hotfix that is described in the following Microsoft Knowledge Base article is installed:
811169 Update to increase the performance of the Network Redirector
In this scenario, the cache is not flushed before the view of the file is unmapped. WORKAROUND To work around this problem, disable opportunistic locks on the server where you are saving the file. To do this, set the EnableOplocks registry value to "0" in the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters To do this, follow these steps: - Click Start, click Run, type regedit, and then press ENTER.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters - If the EnableOplocks value is not present in the right pane, you must create it. To do this, follow these steps:
- Right-click Parameters in the left pane, point to New, and then click DWORD Value.
- Type EnableOplocks to name the value, and then press ENTER.
- Right-click EnableOplocks, and then click Modify.
- In the Value data box, type 0, and then press ENTER.
- Quit Registry Editor.
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 XP 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. 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.
Date Time Version Size File name
------------------------------------------------------------
23-Nov-2004 23:33 5.1.2600.2569 174,592 Rdbss.sys
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: | 6/1/2006 |
---|
Keywords: | kbQFE kbHotfixServer kbWinXPsp2fix kbWinXPpreSP2fix kbfix kbbug KB885936 kbAudITPRO kbAudDeveloper |
---|
|