![]() I was able to replicate this issue in my own lab by setting my DatabaseCopyAutoActivationPolicy to Blocked on my two Exchange 2013 CU2 Mailbox Servers (also not in a DAG so the setting “should” not matter). However in this case it was causing CAS to break as it could not find the mailbox database. But again, no DAG so it should not matter. It would take an admin action to override this & activate the database. ![]() All this command should do is tell the DAG that no mailbox database copies can be automatically activated on this server. This customer did not have a DAG so this command was not needed but nonetheless this command should have absolutely no ill effect on the ability of CAS to proxy requests to the mailbox server components. One of them was running “Set-MailboxServer -Identity EXServerName -DatabaseCopyAutoActivationPolicy Blocked”. Before installing CU2 the customer had read a blog stating some maintenance steps he should perform on his Exchange Server beforehand. > .Cafe.MailboxServerLocatorException: The database with ID 5105a9bc-cfcd-4842-baaf-451561550e08 couldn’t be found”Īfter a night’s worth of troubleshooting we escalated to Tier 3 in Microsoft Support & our resolution came from a setting I would not at all have expected. “ServerLocatorError,POST, The database with ID 5105a9bc-cfcd-4842-baaf-451561550e08 couldn’t be found. This started after the customer installed CU2.Īlso, if you look in the HTTPProxy logs (C:\Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\Owa) you would see the following error: User’s would receive “The website cannot display the page” after authenticating to OWA. This issue comes fresh from a Microsoft Crit-Sit case I was just on for one of our customers.Īll client access was broken (specifically OWA) on a standalone Multi-Role Exchange 2013 CU2 Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |