Win 7 + Office 2010 = Read-Only Documents After Resuming from Sleep

[SirDrewski]

Greetings,


I have an issue when resuming from sleep/standby/hibernation where I've left Word or Excel with a file open from a network drive. System comes back up and Word makes the document read only and shows the error:


"Word cannot establish a network connection with this document after the system resume from suspend mode. Save the document into a different file to keep any changes"


I've found and applied KB2413659 here Description of the Word 2010 hotfix package (Mso-x-none.msp, Word-x-none.msp): October 26, 2010 which offers a hotfix to sort it, but have applied that and still get the same problem.


I've also tried http://support.microsoft.com/kb/2434898


And Connection to a network document is lost in the 2007 Office system or in Office 2010 after the computer resumes from standby


None of the hotfixes or KB articles have resolved this issue. Any additional guidance you can offer would be much appreciated.

I realize that Office 2010 is a factor here but I believe this issue is being caused solely by the operating system as this problem does not occur in Windows XP. Additionally, when resuming from sleep, mapped network drives always display a red X in explorer. After clicking on a mapped drive, though, it displays the folder contents and the icon reverts back to the connected state.

This leads me to believe that Windows 7 does not immediately recognize the network connection when resuming from sleep, and because it believes the network share that the document is saved to is unavailable it places it in "Read-Only" and forces a save-as. I believe this to be a Windows 7 issue, not Office. Any insight you can provide would be greatly appreciated.

 

[Irene]

Hello SirDrewski, welcome to Seven Forums.

Did you explore the Additional Troubleshooting in this link?
Connection to a network document is lost in the 2007 Office system or in Office 2010 after the computer resumes from standby | Microsoft Knowledge Base Wiki

Please remember to backup your registry before making any changes (and only if you are familiar with and confident in that area).
.

If you continue to experience the issue after you apply the appropriate hotfix and configure the NetworkAvailableTimeInSeconds registry subkey, you may have to collect additional information to correctly enable the hotfix on your system.

To collect the additional information, follow these steps:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then select the following registry subkey:
   
   For the 2007 Office system:HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\TrustCenter
   
   For Office 2010:HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\TrustCenter
3. On the Edit menu, point to New, and then click Dword Value.
4. Type EnableLogging, and then press Enter.
5. Right-click EnableLogging, and then click Modify.
6. In the Value data box, type 1, and then click OK.
   Note This registry subkey creates a log file that can be found in the following folder: C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\OFFICE\TCDiag
7. Exit Registry Editor.
8. Reproduce the problem.
9. Locate and open the log file that is created.
10. Analyze the file. To do this, follow these steps:
    1. Open the WDTCD.LOG file that is generated in step 6.
    2. Search for the entry HrBindShellPistm:, and then note the error code such as, for example, 80070035.
    3. Revert every pair of two digits from this error code by writing them down from right to left. For example, revert 80 07 00 35 to 35 00 07 80.
11. Click Start, click Run, type regedit in the Open box, and then click OK.
12. Locate and then select the following registry subkey:
    
    For the 2007 Office system:HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Internet
    
    For Office 2010:HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Common\Internet
13. On the Edit menu, point to New, and then click Binary Value.
14. Type ResumeErrorCodes, and then press Enter.
15. Right-click ResumeErrorCodes, and then click Modify.
16. In the Value data box, type the value that you retrieved from the log file in step 10C, and then click OK.
17. In some cases, multiple, different error codes may be observed from step 9. In this case, convert all error codes as described in step 10C, and append them all serially to the ResumeErrorCodes registry entry.
18. Exit Registry Editor.