Anything for sysadmins!


Event 1007 – MSExchange Mailbox Replication

The Mailbox Replication service was unable to determine the set of active mailbox databases on a mailbox server.<br/>Mailbox server: Exchangeserver.spil.local<br/>Error: MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)<br/>Diagnostic context:<br/>    ......<br/>    Lid: 15000   dwParam: 0x6BA      Msg: EEInfo: prm[1]: Pointer val: 0x0000000000000000<br/>    Lid: 15000   dwParam: 0x6BA      Msg: EEInfo: prm[2]: Pointer val: 0x985CA8C000000000<br/>    Lid: 16280   dwParam: 0x6BA      Msg: EEInfo: ComputerName: n/a<br/>    Lid: 8600    dwParam: 0x6BA      Msg: EEInfo: ProcessID: 2256<br/>    Lid: 12696   dwParam: 0x6BA      Msg: EEInfo: Generation Time: 2010-09-24 11:32:34:750<br/>    Lid: 10648   dwParam: 0x6BA      Msg: EEInfo: Generating component: 18<br/>    Lid: 14744   dwParam: 0x6BA      Msg: EEInfo: Status: 10060<br/>    Lid: 9624    dwParam: 0x6BA      Msg: EEInfo: Detection location: 318<br/>    Lid: 13720   dwParam: 0x6BA      Msg: EEInfo: Flags: 0<br/>    Lid: 11672   dwParam: 0x6BA      Msg: EEInfo: NumberOfParameters: 0<br/>    Lid: 24060   StoreEc: 0x80040115<br/>    Lid: 23746  <br/>    Lid: 31938   StoreEc: 0x80040115<br/>    Lid: 19650  <br/>    Lid: 27842   StoreEc: 0x80040115<br/>    Lid: 20866  <br/>    Lid: 29058   StoreEc: 0x80040115

This seems to be related to the configuration of the NIC(s) in your Exchange server. I’ve seen a couple of causes for this problem. Confirm all of them are correct and the issue should be resolved.

  • Using DHCP for one or more NICs. Setting this NIC to static might solve the problem.
  • Setting multiple IP addresses on one NIC. Editing the DNS to only refer to 1 IP instead of both might solve the problem.
  • Having a disabled NIC set to DHCP. Editing the disabled NIC to use static IP might solve the problem.
  • Information Store service is not running. Start the Information Store service.
  • IPv6 is enabled and you’re not using it. Disable IPv6.

There are a couple of other possible solutions, but those have not been confirmed to work yet. If you found another possible solution, please comment below!

Interesting read:

Be Sociable, Share!

Posted by Mischa Oudhof

Comments (0) Trackbacks (0)
  1. I’m having this issue on Exchange 2010 running on Hyper-V (ProLiant DL380 G7).

    The error appears when I boot the VM, along with a couple other errors which are probable a result of the initial 1007 error.

    When I boot the VM and logon to the console immediately, I can see the network icon on the systray seems to be frozen. Also I cannot browse the network and sharing center for a short period of time.

    Hence, for some reason the VM takes very long to initialize and causes the issue. However, after the NIC is initialized Exchange seems to work fine.

    • The cause of the error is not having network connectivity.

      Unfortunately I don’t have much experience with Hyper-V, so I can’t really help there. You could try uninstalling the NIC on the VM and reinstalling. Perhaps it didn’t register properly and it’s forced to reinstall every time. Another option might be the virtual network which is not configured properly.

  2. Sorry, I meant… the NIC takes very long to initialize. The actuall VM is up in a couple seconds.

  3. I’ve been chasing this error (and the cascade of other errors caused by this) for most of this evening. Then I found your advise… and my Exchange server is happy again! Thank you, thank you, THANK YOU! If you were in the DC area I’d buy you a beer or a bowl of Pho!

Leave a comment

No trackbacks yet.