- 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.
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.
- 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:
If you click on OK the text file will be empty. If you now close and open the file again it might work.
This issue occurs because the Outlook 2010 client tries to write data to an open SMBv2 file ID that has read-only access.
This issue occurs because the offline files client tries to read the file from the server before the actual SMB connection is established.
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:
Microsoft CatalogThis hotfix is available at Microsoft Update Catalog.
Hotfix informationA 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: 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.
PrerequisitesTo 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:
Registry informationTo apply this hotfix, you do not have to change the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Article ID: 2732673 - Last Review: 13 Nov 2013 - Revision: 1