failed to connect to information store service on the server
-
Monday, March 12, 2007 11:42 AMHi. I managed to get my Exchange server up and going and was able to send and receive internal email. I tried to configure the Exchange server and get the MX records set up so that I could send and receive externally. Unfortunately I went by the book and set up a NAT Server (big mistake)! I wanted it to sit between the Internet and the Exchange Server and forward emails into Exchange. But it did not. After changing the IP settings on the 2 servers, it just mucked the whole network up (with its security mad settings) to the extent that the NAT server would not communicate with anything. As the network is live, and becuase I dont have the LIVE time to configure all the security settings (there are other services on the NAT server that were ESSENTIAL for the business), I had to stop the service and remove it.
I am now just trying to use the Internet Router's NAT facilities for port forwarding SMTP to the Exchange Server - less impact on the network.
I was led to believe this is a reasonable alternative after reading: http://www.petri.co.il/configure_mx_records_for_incoming_smtp_email_traffic.htm (the bit on using a NAT router).
Unfortunately the changes I made to the Exchange Server and the MX records now prevent me even accessing the server internally or setting up new email accounts.
If anyone can tell me what this error message is about I would appreciate it:
Warning:
Failed to connect to information store service on the server "SERVER.mydomain.COM". The exception message is "MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
......
Lid: 10648 dwParam: 0x6D9 Msg: EEInfo: Generating component: 2
Lid: 14744 dwParam: 0x6D9 Msg: EEInfo: Status: 1753
Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location: 501
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: 4200SERVER.NIID.COM
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
Lid: 15000 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Pointer val: 0x0x1c788410 (UnknownPtag)
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115".
get-PublicFolderDatabase
Completed
Warning:
Failed to connect to information store service on the server "SERVER.mydomain.COM". The exception message is "MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
......
Lid: 10648 dwParam: 0x6D9 Msg: EEInfo: Generating component: 2
Lid: 14744 dwParam: 0x6D9 Msg: EEInfo: Status: 1753
Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location: 501
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: 4200SERVER.NIID.COM
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
Lid: 15000 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Pointer val: 0x0x1c788410 (UnknownPtag)
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115".
--------------------------------------------------------
OK
--------------------------------------------------------
Also, do you agree with the suggested A and MX records in http://www.petri.co.il/configure_mx_records_for_incoming_smtp_email_traffic.htm
Thanks,
All Replies
-
Monday, May 07, 2007 7:06 PM
Hi,
I came across an identical error but in my case the System Attendant service on the remote server didn't start for which that error was popping up when ever I connect from an Exchange Management Console, once I started the service the error vanished.
Thanks,
Srini
-
Thursday, September 13, 2007 9:58 AM
First disable your anti-virus & then start Microsoft Exchange Information Store service it should start
Regards
DEV -
Tuesday, December 11, 2007 5:44 PM
I'm receiving essentially the same error:
--------------------------------------------------------
Microsoft Exchange Warning
--------------------------------------------------------
The following warning(s) were reported while loading topology information:
get-MailboxDatabase
Completed
Warning:
Failed to connect to information store service on the server "XXX.yyy.com". The exception message is "MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
......
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[1]: Pointer val: 0x0x00000000 (PR_NULL)
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[2]: Pointer val: 0x0x00000000 (PR_NULL)
Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 8336
Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2007-12-10 18:06:02:897
Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 8
Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115".
[snip]
--------------------------------------------------------
OK
--------------------------------------------------------
In my case, I have only recently begun to receive this error. It occurs on both nodes of my first CCR cluster, but only when using the Exchange Management Console from those two servers. If I use EMC to view the status of these mailbox servers from my other CCR cluster nodes or from either of my CAS boxes, it's fine. EMC shows mount status as "Unknown" but shows the copy status as "Healthy." I also get this error when running (if I recall) get-mailboxdatabase from either node of the first CCR cluster.
The event viewer doesn't throw an error. Are there other logs that may provide relevant info? My systems are otherwise fully functional, as shown by running the tools on other nodes and by the ability to send/receive.
Best regards,
Dan
- Edited by Daniel Schultz Monday, December 12, 2011 4:14 PM editing for brevity

