Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. "Delayed write failed" error message when .pst files are stored on a network file server that is running Windows Server 2008 R2

"Delayed write failed" error message when .pst files are stored on a network file server that is running Windows Server 2008 R2

View products that this article applies to.

Symptoms

Consider one of the following scenarios: 

Scenario 1:
  • You enable Remote Desktop on a computer (computer A) that is running Windows 7 or Windows Server 2008 R2.
  • You configure an Outlook 2010 client that is installed on computer A to save Personal Folder (.pst) files on another computer (computer B). Computer B is a file server that is running Windows Server 2008 R2.
  • You establish a remote connection to computer A from a client computer, and then start Outlook 2010 in the Remote Desktop session.
In this scenario, you receive the following error message that states that the .pst file is corrupted:
Delayed Write Failed
Windows was unable to save all the data for the file file path. The data has been lost. This error was returned by the server on which the file exists. Please try to save this file elsewhere.
Additionally, the following event is logged in the System log on computer A:Note This issue does not occur if you disable the Server Message Block version 2 (SMBv2) file sharing protocol on the file server.

Scenario 2:

  • You have mapped a network drive to a server share and you use offline files to make the data on this share available offline.
  • You have a MUP filter driver installed (e.g. disc encryption Software).
  • You try to open a file (e.g. a text file) of a given size from this share while you're connected to the Network, although the actual SMB Connection to the server is not yet established.

In this Scenario, you might get the this error message:

  Cannot open the %% file. Make sure a disk is in the drive you specified

If you click on OK the text file will be empty. If you now close and open the file again it might work.


↑ Back to the top

Cause

Scenario 1:
This issue occurs because the Outlook 2010 client tries to write data to an open SMBv2 file ID that has read-only access.


Scenario 2:
This issue occurs because the offline files client tries to read the file from the server before the actual SMB connection is established.



↑ Back to the top

Resolution

To resolve the issue, install the hotfix on the computer that Outlook 2010 is installed on (computer A) respectively on the Computer that Encounters the error while opening the file.

Note This update also fixes a regression issue in the Rdbss.sys file after the update 2775511 is installed. Install this update (2732673) after you install update 2775511. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2775511 An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1

Microsoft Catalog

This hotfix is available at Microsoft Update Catalog.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1). For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, you do not have to change the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    1.22xxx    		Windows 7 and Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MANIFEST files and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Rdbss.sys6.1.7601.22377246,78405-Jul-201303:00x86
For all supported x64-based versions of Windows Server 2008 R2 and Windows 7
File nameFile versionFile sizeDateTimePlatform
Rdbss.sys6.1.7601.22377316,41605-Jul-201302:53x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Rdbss.sys6.1.7601.22377737,79205-Jul-201302:16IA-64

↑ Back to the top

Status

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

↑ Back to the top

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot Applicable
File size2,136
Date (UTC)05-Jul-2013
Time (UTC)11:59
PlatformNot Applicable
File nameX86_a21940ecdabec4b7a05d3c7a6275d758_31bf3856ad364e35_6.1.7601.22377_none_fa284849e4227406.manifest
File versionNot Applicable
File size693
Date (UTC)05-Jul-2013
Time (UTC)11:59
PlatformNot Applicable
File nameX86_microsoft-windows-rdbss_31bf3856ad364e35_6.1.7601.22377_none_5c27e35ed8f73e40.manifest
File versionNot Applicable
File size21,803
Date (UTC)05-Jul-2013
Time (UTC)05:45
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_acd154283b63fb4391dd5231e4848111_31bf3856ad364e35_6.1.7601.22377_none_f201197aa1160793.manifest
File versionNot Applicable
File size697
Date (UTC)05-Jul-2013
Time (UTC)11:59
PlatformNot Applicable
File nameAmd64_microsoft-windows-rdbss_31bf3856ad364e35_6.1.7601.22377_none_b8467ee29154af76.manifest
File versionNot Applicable
File size21,809
Date (UTC)05-Jul-2013
Time (UTC)05:48
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,350
Date (UTC)05-Jul-2013
Time (UTC)11:59
PlatformNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_28d5ff1688714520cb2497be871c5a26_31bf3856ad364e35_6.1.7601.22377_none_86aa33a242d046e5.manifest
File versionNot Applicable
File size695
Date (UTC)05-Jul-2013
Time (UTC)11:59
PlatformNot Applicable
File nameIa64_microsoft-windows-rdbss_31bf3856ad364e35_6.1.7601.22377_none_5c298754d8f5473c.manifest
File versionNot Applicable
File size21,806
Date (UTC)05-Jul-2013
Time (UTC)05:33
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size1,447
Date (UTC)05-Jul-2013
Time (UTC)11:59
PlatformNot Applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseadvanced, kbsurveynew

↑ Back to the top

Article Info
Article ID : 2732673
Revision : 1
Created on : 1/7/2017
Published on : 11/13/2013
Exists online : False
Views : 820