Discussion Locked

Exchange 5.5 Information Store fails to

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The information store will not start. I am getting a Dr. Watson error, and in the event viewer, the error is 1067. All services that depend on the Store also will not start.
We are presently running The eseutil and isinteg utilities to check the stores.
We have Groupshield installed also.
Any Ideas?

6 replies

by 4u21der

I had the same issues and this worked for me.

==============================
To correct this behavior, start the Microsoft Exchange Administrator program, open the properties page of the IMC or IMS that is exhibiting this problem, and note which user is shown as the Administrator's Mailbox. Next, bring up the properties page of that user, click the E-Mail Addresses tab, and add an X.400 address.

Another way to correct this behavior is to specify a different user (who already has an X.400 address) in the Administrator's Mailbox box on the IMC or IMS properties page.
==============================

From MS Article: 149542

Hope this helps.

Good Luck!

by dwooming

The Dr. Watson error is on the store.exe.
The IMS and the Event services also will not start.

by mckaytech

There are a couple of possibilities. First of all, there is a known bug that will be fixed in SP5 for Exchange v5.5 (or you can obtain the hot fix sooner if this turns out to be the problem).

There is also a known bug with bad messages in the IMS causing this behavior but that was corrected in SP3.

Because the information provided about the error is relatively non-specific, it might be a good idea to head over to Microsoft's TechNet site and search using terms of "Exchange v5.5 and earlier" and "Dr. Watson on Information Store". You should come up with around 40 hits and very likely you'll find the answer within one of them. Many have to do with malformatted or corrupted messages causing the behavior you've seen, and the fix is toclear out the queue (MTA or IMS), re-start the service and then figure out which message is causing the grief.

paul

paul

This discussion is closed to new replies.