Unexpected error 500 :( when accessing Microsoft Exchange 2013

I didn’t see much information about this type of issue on the web, so I figured I share it here. Please excuse my lack or recent posts. 🙂

Issues:

A user logs into their mailbox via OWA and then hits the Option to modify his apps. He may be presented with the following error

Or you login to your ECP console with success, but some of your tabs so to speak do not work. For instance the “Servers” tab which gives you the ability to modify server details like certificates, virtual directories, etc.

The key to this issue is “YOU CAN LOGIN WITH SUCCESS!”. Most times when Exchange presents you with a Error 500 its due to a corrupt AD attribute which is easily fixed by deleting it then rebooting your Mailbox servers. But in this case that’s not the resolution.

Resolution:

This issue is caused by having .Net Framework 4.6.1 installed. To resolve open up the control panel, and uninstall windows update. Now look for KB3102467 and KB3098785 then uninstall them. Once they are both removed reboot your server. If you want you can also follow this article on how to clean up the MSExchCanaryData attribute for an added measure Here.

A good resource from the Exchange blog guys is Here. .Net Framework 4.6.1 isn’t compatible with Exchange 2013 at this time and Microsoft recommends blocking the update.

 

Happy Emailing.

About the Author

James Davis

My name is James Davis and i currently live in Colorado. I have been apart of the technology workforce for 10 years. I started out serving for the military in what was then called the Base Band Node. Since those days I have moved on and up in to the corporate world. I am now a Architect/Engineer for a top fortune 250 company.

You may also like these