locked
"There has been a network or file permission error. The network connection may be lost." RRS feed

  • Question

  • I am looking for some help folks. I have a few users that have been recently been upgraded from Office 2003 to Office 2007 on Windows XP. When they try to save excel or word files to a network share they the get the error:

    "There has been a network or file permission error. The network connection may be lost."

    I have come accross suggested solutions which I have tried, but unfortunately solved my issue. Here are the sussested solutions that I have tried:

    http://support.microsoft.com/kb/983458. Disabled anti-virus software. http://support.microsoft.com/kb/212347  http://support.microsoft.com/kb/291156

    Has anyone seen a magic solution somewhere?


    TD
    Friday, May 13, 2011 5:32 PM

Answers

  • Hi,

     

    There are similar known issue occurs while the following conditions are true: 

    ·         The client machine is using Windows XP SP2 and Office 2007;

    ·         Check-out the file from WSS 3.0, make change and check-in the modification back. 

    The root cause of this issue is that a library file called Msdaipp.dll is reading a registry entry with information that Msdaipp.dll cannot read.

    To resolve this case, we need to delete related registry key. Please note to make a backup of the registry before the removing operation: 

    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

    1.       On the server side, run Regedit to open the Registry Editor;

    2.       Navigate to the following key:

    HKEY_CLASSES_ROOT\Software\Microsoft\MasterAggregatorForIPP\OleDbHandlers\{E1D2BF40-A96B-11d1-9C6B-0000F875AC61}

    Confirm that if there is a system sub-key under this key.

    a. If so, right-click the sub-key and click Export. This operation will back the sub-key to another place. Then delete the sub-key in the Registry Editor.

    b. If not, please check the same key on the client side, if it exists, backup and delete it as the operation above (a).

    3.       Check if the check-in operation is working correctly. If not, please restore the registry keys back and let us know the result.

     Best Regards,

     

    Sally Tang

    • Marked as answer by Sally Tang Friday, May 20, 2011 7:18 AM
    Tuesday, May 17, 2011 8:27 AM

All replies

  • Additional notes. I also came accross soething about adding a registry key for Csc, but no luck as well.

    http://www.online-it-support.co.uk/?p=641

    I also tried the Fixit tool, but no luck.


    TD
    Friday, May 13, 2011 5:48 PM
  • Hi,

     

    There are similar known issue occurs while the following conditions are true: 

    ·         The client machine is using Windows XP SP2 and Office 2007;

    ·         Check-out the file from WSS 3.0, make change and check-in the modification back. 

    The root cause of this issue is that a library file called Msdaipp.dll is reading a registry entry with information that Msdaipp.dll cannot read.

    To resolve this case, we need to delete related registry key. Please note to make a backup of the registry before the removing operation: 

    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

    1.       On the server side, run Regedit to open the Registry Editor;

    2.       Navigate to the following key:

    HKEY_CLASSES_ROOT\Software\Microsoft\MasterAggregatorForIPP\OleDbHandlers\{E1D2BF40-A96B-11d1-9C6B-0000F875AC61}

    Confirm that if there is a system sub-key under this key.

    a. If so, right-click the sub-key and click Export. This operation will back the sub-key to another place. Then delete the sub-key in the Registry Editor.

    b. If not, please check the same key on the client side, if it exists, backup and delete it as the operation above (a).

    3.       Check if the check-in operation is working correctly. If not, please restore the registry keys back and let us know the result.

     Best Regards,

     

    Sally Tang

    • Marked as answer by Sally Tang Friday, May 20, 2011 7:18 AM
    Tuesday, May 17, 2011 8:27 AM
  • Oops I had stepped away from this forum for a while. When you say "If not, please check the same key on the client side, if it exists, backup and delete it as the operation above (a)."  Are you saying the initial Registry Key change is on the file server?

    Thank you.


    TD
    Friday, June 3, 2011 3:32 AM