Solved

Exchange 2003 Server: MAPI call OpenMsgStore failed when trying to rebuild Offline Address Book, Event 9175

Posted on 2004-09-23
12
10,407 Views
Last Modified: 2011-08-18
MY OAB has stopped updating.  I have installed nothing new on this server, except Windows Updates.  This server is not an AD server and only functions as an Exchange 2003 Enterprise server.  When I go into the ESM, then go to Offline Address Lists, right click on my Offline Address Book, then select Rebuild, I get a message that pops up stating:
"MAPI or an unspecified service provider
ID no: 00000000-0000-00000000
ID no: c1050000
Exchange System Manager"

I also get two identical events immediately logged:
Event ID: 9175
Source: MSExchangeSA
Category: MAPI Session
Type: Error
User: N/A

Description:
The MAPI call 'OpenMsgStore' failed with the following error:
The information store could not be opened.
The logon to the Microsoft Exchange Server computer failed.
MAPI 1.0
ID no: 80040111-0286-00000000

Can anyone please help me?  I used to be able to clear this error by first rebooting my Exchange server, then rebooting my AD controllers, but now it doesn't work anymore.  I'm presuming some Microsoft update that was installed is now preventing this particular solution.

I have several remote users that sychronize and work offline, so the Offline Address Book is critical for them since it changes so much.

Thanks!
0
Comment
Question by:EvilPeppard
  • 8
  • 4
12 Comments
 
LVL 24

Assisted Solution

by:David Wilhoit
David Wilhoit earned 500 total points
Comment Utility
http://support.microsoft.com/default.aspx?scid=kb;en-us;315250

No, this isn't an update problem, it's a DSAccess problem. Can you still view permissions, and check properties of all the objects in the ESM? Or is this the only thing happening?

D
0
 

Author Comment

by:EvilPeppard
Comment Utility
The only other thing I have noticed is this:

If I go into the ESM under Folders, right click and select Show System Folders, drill down to OFFLINE ADDRESS BOOK, find my OAB (called Offline Global Address Book), expand the folder and select OAB Version 2, right click and select Properties, then hit the Permissions Tab and try to view Client Permissions, I get the popup error message:

"The Information Store could not be opened.
The logon to the Microsoft Exchange Server computer failed.
MAPI 1.0
ID no: 80040111-0286-00000000

ID no: c1050000
Exchange System Manager"

I then get this event logged 4 times in a row:
Event ID: 9175
Source: EXAdmin
Category: (14)
Type: Error
User: N/A
"The description for Event ID ( 9175 ) in Source ( EXAdmin ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: OpenMsgStore, The information store could not be opened.
The logon to the Microsoft Exchange Server computer failed.
MAPI 1.0
ID no: 80040111-0286-00000000"

Hope this helps. :)
0
 
LVL 24

Assisted Solution

by:David Wilhoit
David Wilhoit earned 500 total points
Comment Utility
Looks like you're reading the error from a different machine, that doesn't have the proper event log dlls to see the messages. You on your workstation with the ESM installed?
0
 

Author Comment

by:EvilPeppard
Comment Utility
No, I took that information straight from the Event Manger on my Exchange Server.  That is where I'm using the ESM as well.
0
 

Author Comment

by:EvilPeppard
Comment Utility
Incidentally, I looked up the above mentioned MS KB Article http://support.microsoft.com/default.aspx?scid=kb;en-us;315250 and I don't have a "DS Server" entry in the specified Registry path.  Plus, that article says it applies to Exchange Server 2000 and I mentioned I am running Exhange 2003 Enterprise Server.
0
 
LVL 24

Assisted Solution

by:David Wilhoit
David Wilhoit earned 500 total points
Comment Utility
Doesn't matter, you still need it, I'll check my 2003 server when I get home this eve. If you check the DSAccess tab on the server properties in the ESM, does it show your GCs and DCs properly?

Also, something is wrong because:
The description for Event ID ( 9175 ) in Source ( EXAdmin ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: OpenMsgStore, The information store could not be opened.
The logon to the Microsoft Exchange Server computer failed.

This should read like your first post; instead, the event viewer can't seem to find the dll to read the event and describe it properly.

D
0
Do email signature updates give you a headache?

Do you feel like all of your time is spent managing email signatures? Too busy to visit every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

 

Author Comment

by:EvilPeppard
Comment Utility
I want to make sure I'm looking the correct spot.  In ESM, under Administrative Groups, I right click on my server (GOLIATH), choose Properties, then select the Directory Access tab?  If so, I see both my AD controllers listed there with info regarding Type and LDAP ports.  Everything appears in order on that tab.
0
 

Author Comment

by:EvilPeppard
Comment Utility
P.S. I appreciate your help with this.
0
 
LVL 24

Accepted Solution

by:
David Wilhoit earned 500 total points
Comment Utility
I'm sorry man, I went home, and then took my kids to football :)

Ok, the deal is, you're in the right spot. Hit the drop-down, and check the GC lists. Make sure what's listed can respond. What about DNS on the Exchange server? Is it pointed to your internal AD DNS server?
0
 

Author Comment

by:EvilPeppard
Comment Utility
Ok, I am really getting confused.  While working on this issue yesterday, I noticed there was a critical update available for the .NET Framework (this Exchange Server is running on Windows 2003 Standard Server).  I installed the critical update, then scheduled the server to reboot at 4:00 am this morning.  While checking the server this morning to make sure it came back up ok, I decided to try rebuilding the OAB and this time it worked!

This is the kind of problem I've been persuing.  It will seem to stop working after I have to reboot my servers, then it will start working again after an undetermined amount of time.  Usually the sequence is, I have to reboot my AD servers first, then the Exchange server, then the AD servers again.  In the past, that sequence has made the OAB error stop.  This last time I was not able to get the OAB rebuild error to go away no matter what I did, but now it is working ok again with no errors being reported in the Event Viewer.  WTF?

Also, to answer your question: Yes: my Exchange Server (GOLIATH) is pointing its primary DNS internally at the main AD server.  I believe it had to be this way all alone or Exchange would function improperly with Active Directory.

Thanks.
0
 

Author Comment

by:EvilPeppard
Comment Utility
Incidentally, I now can view Cleint permissions when I go into the ESM under Folders, right click and select Show System Folders, drill down to OFFLINE ADDRESS BOOK, find my OAB (called Offline Global Address Book), expand the folder and select OAB Version 2, right click and select Properties, then hit the Permissions Tab. :S
0
 

Author Comment

by:EvilPeppard
Comment Utility
I seem to have (possibly) found how to correct this error.  The resolution derives from the correct sequence of booting my servers, as I originally thought.

In order for the error to go away and the Offline Address Book to start working again properly, I have to reboot my main (or parent/primary) Active Directory server first.  This server is identified as being the original or first Active Directory Domain Controller.  Once that has server has come back up, I reboot my secondary (or backup) Active Directory controller.  Once it has come back up, I can reboot the Exchange Server and the OAB error will be gone.

There must be some sequence where the primary AD controller has to be up first, before the backup one can fully authenticate to other machines on the domain.  If I reboot the backup AD server first, then the primary, then the Exchange Server, I will most likely get the OAB error message back.  I tested this sequence of events this morning (had to go in anyway cause of an 8 hour power outage at our building) and these are the results I've found.

Hope it helps someone else. :)
0

Featured Post

Want to promote your upcoming event?

Is your company attending an event or exhibiting at a trade show soon? Are you speaking at a conference? Spread the word by using a promotional banner in your email signature. This will ensure your organization’s most important contacts are in the know.

Join & Write a Comment

Suggested Solutions

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now