Article ID: 2824408 - View products that this article applies to.
Consider the following scenario:
This issue occurs because the memory manager on the client computer holds executable objects and does not close them. However, the server considers the executable objects to be closed and reuses the file ID for another new file. This causes a file ID collision. Therefore, when the oplock break request is issued, the client computer processes the previous executable object instead of the new file.
Hotfix informationThe hotfix for this issue is included in update 2732673. To resolve the issue, install update 2732673 from the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/2732673/ )"Delayed write failed" error message when .pst files are stored on a network file server that is running Windows Server 2008 R2
PrerequisitesTo apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/976932/ )Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry informationTo apply this hotfix, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 2824408 - Last Review: August 16, 2013 - Revision: 4.0