XCLN: Error Occurs While Attempting to Access Personal Folders

 Last reviewed: October 31, 1997
Article ID: Q163626
The information in this article applies to:
  • Microsoft Exchange Windows 3.x client, version 4.0
  • Microsoft Exchange Windows 3.x client, version 5.0
  • Microsoft Exchange Windows 95 client, version 4.0
  • Microsoft Exchange Windows 95 client, version 5.0
  • Microsoft Exchange Windows NT client, version 4.0
  • Microsoft Exchange Windows NT client, version 5.0

SYMPTOMS

You may receive the following error message when you attempt to start the Microsoft Exchange client: 

   The set of folders could not be opened. The file
   <path>\<filename>.pst is in use and could not be accessed.
   Close any application that is using this file, and then try again.

WORKAROUND

This error can occur if the file is opened by another user or by the same user from another computer. To correct this problem, verify that no other user or computer has access to the Personal Folder file.

You may also need to verify if the drive or directory that the file is located in has been shared on the network. In this scenario, either disconnect any users connected to the computer or disable the share.

Additional query words:
Keywords : XCLN kbprb
Version : 4.0 5.0
Platform : WINDOWS
Issue type : kbprb
Solution Type : kbworkaround

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 31, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.