XCLN: Replacing a Damaged Offline Folder (OST)

Last reviewed: July 10, 1997
Article ID: Q165327

The information in this article applies to:
  • Microsoft Exchange Windows 3.x client, version 4.0
  • Microsoft Exchange Windows NT client, version 4.0
  • Microsoft Exchange Windows 95 client, version 4.0

SUMMARY

To create a new Offline Folder file (OST) to replace a damaged or corrupted one, follow these steps:

  1. Exit and log out of the Microsoft Exchange client.
2. Rename any *.ost files to an "xxx" extension. 3. Restart the Microsoft Exchange client online. Your profile settings will need
   to be changed it defaults to start offline.
4. Upon starting the Microsoft Exchange client, the following prompt will be
   displayed:

      The file "c:\<exchangedir>\xxx.ost could not be found.

   Click OK to continue.
5. The Offline Folder File Settings dialog box will be displayed. Click OK or
   change the path and/or OST filename.
6. Select YES at the following prompt:

      The file c:\<exchangedir>\xxx.ost could not be found. Would you like to
      create it?

  • From the Microsoft Exchange client Tools menu, select Sync All Folders. The new OST is now synchronized with the server and the Microsoft Exchange client may be started offline.


  • KBCategory: KBUSAGE
    KBSubcategory: WIN16 WIN95 WINNT XCLN
    Additional reference words:
    Version : 1.00
    Platform : IDEAS


    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: July 10, 1997
    © 1998 Microsoft Corporation. All rights reserved. Terms of Use.