Tuesday, February 1, 2005

Fixing an Information Store could not be opened error

OUTLOOKPOWER ANSWER TEAM

By Francine Otterson

Outlook can be configured to access your mailbox folders offline from the Exchange Server. This provides the functionality and features of being connected to an Exchange server, but also the ability to work on your mailbox items offline if need be.

One of the common errors received when working with Offline Folders is, "The information store could not be opened," and not being able to work offline, as experienced by Jan Schaafsma.

Jan Schaafsma writes:

I've got a problem with MS Outlook 2000. The information store could not be opened, and I can't work offline. Do you know a solution for this?

"The Information Store Could Not Be Opened" error is often associated with a problem in the .ost file (offline storage). If the file is corrupt, or not setup correctly, this type of error can occur. The .ost file needs to be configured in order for the offline setup to work. For Outlook 2000, check to confirm that an .ost file has in fact been set up by navigating to Tools->Server->Microsoft Exchange->Advance.

If there's a file listed, then it may have become corrupted. A common cause of corruption is the Send/Receive (synchronization) being stopped prematurely and/or frequently, of course, there are other causes as well. If you suspect a corruption issue with your .ost file, then it's best to have Outlook recreate it.

Close Outlook, then do a complete search (hidden files included) for all files with a .ost extension (wildcard search *.ost), then delete all returned files. Next, open Outlook and do a fresh Send/Receive (synchronization), this will force a new offline storage (.ost) file to be created.

If the problem still arises, then the profile or program itself may need to be checked for possible causes. Creating a new profile is a great test to see if it's program related. If the Send/Receive work fine on a new profile, there's no need to go further. If it doesn't, then I'd consider doing a Detect and Repair on the program, and possibly reinstalling it. Also, make sure your system is completely up to date with all the latest patches and updates.