NET dependency hell, so it’s a task best approached with a clear plan and an approved outage window…Ībsent that fix, there is a workaround for the issue. Exchange 20 both have a pretty messy case of.
The fix listed there is “Install CU11 or later”, which is good advice in general but also means “perform a significant maintenance task on your Exchange infrastructure”, which is generally not a task to undertake without preparation to resolve a service outage.
CANARY MAIL EXCHANGE MICROSOFT CODE
The specific support article describing the issue (which I didn’t find until a good while later, because the error message is vague and does not provide a specific error code or provide an obvious Event ID in relation to it) is here. Not all users would experience the problem, but sometimes it would also occur when accessing ECP – and when it did happen, it would affect enough users to count as a major incident, so absent a proper fix for the root cause, a quick-to-deploy workaround would have to suffice.Īfter some digging and head-scratching, we discovered that this is a known issue on Exchange environments running on a very old CU version. The problem symptoms were unhelpful – a user attempting to log into OWA would get a message reading “Something went wrong”, and not a lot more. This post is about a short script I wrote a few years ago to solve a problem I encountered periodically with OWA and ECP access on an Exchange 2013 environment.