I'm going through my Exchange Server's logs and checking out warnings and errors, and I haven't been able to find anything helpful on this one in the application log of the Windows Server 2012 R2 virtual machine running Exchange Server 2013 SP1 only:

Event ID 3154 error, source MSExchangeRepl:

Active Manager failed to mount database Mailbox Database 0738684499 on server <Server.Name.com>. Error: An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)

Apparently the error really is "transient" and the server retries the operation successfully, because everything seems to be working OK, but I'd still like to know why this error appears every time the server starts up, and what I can do to prevent the error from occurring.  Thanks!

Hi,

Thank you for your question.

We could make sure the database 0738684499 is mount and the service which is Microsoft Exchange Information Store is running, if it is running, we could restart them to check if the issue persist.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Thanks Jim.  The database definitely mounts, w/o any assistance from me, and the Info Store service starts up fine. This issue only occurs once, on startup.  One theory I got from someone on another site is that the issue is that the virtual machine running Exchange Server has slightly wrong time when it first starts, so it's unable to communicate w/the Active Directory database on any of the DCs.  The theory goes further and says the virtual machine must then get a good time sync as it continues its boot, then Exchange Server re-tries connecting to Active Directory and it succeeds because now the machine has correct time.  I will check this theory the next time I restart the Exchange Server virtual machine.

I restarted the server this morning, and the 3154 event recurred.  The Time Service started 59 seconds *after* the 3154 occurrence.  If the time were off, then I'd say it would be better to delay the info store mount, but looking at the logs, the time could not have changed more than a few seconds when it did sync, so I don't think time sync is the problem. Whatever it is, despite this message the database mounts just fine 50 seconds after the error event (and 9 seconds before time sync begins).  I have to think there's something about where the database mount is in the startup sequence that's causing this, but whatever the cause, it seems safe to ignore since the database does consistently mount less than a minute after the error event.  Unless you can see a reason not to, I'm going to add this event to my growing list of events which are safe to ignore.  Exchange 2013 seems ridiculously verbose.