We had a problem this week when Exchange 2003 Server ActiveSync decided to break after we did a couple of Windows Updates. The funny thing is that the ActiveSync stopped working on a SINGLE Backend Server, and none of the updates were Exchange or even IIS updates!
Users on the affected backend server just started getting the dreaded HTTP_500 error messages.
So, after loads of troubleshooting, re-applying service packs and even going as far as removing some of the applied updates, David Seymour had the brilliant idea to do a side-by-side comparison of the authentication settings with another backend server.
What we found is that one of the WindowsUpdates (or at least I'm hoping it was!!) removed the Integrated Authentication from the EXCHANGE and PUBLIC virtual folders in IIS. After re-enabling Intergrated Authentication and a quick IISRESET all was back to normal.
Yes. It was as simple as that!
Thanks Dave
- Marlon
*Update:
- I noticed last week that MSExchange.org has released a more in-depth article here that explains exactly how to reset the permissions on the Exchange IIS folders.
- I have to stress that HTTP 500 errors are not just caused by permissions either. A few weeks ago I was working on an SBS2003 Exchange installation - turned out that a previous cowboy deleted the original IIS Virtual folders and didn't re-create them properly. If you are thinking about doing it, check out this SearchExchange.com article that explains how to repair Exchange IIS Folders. (Free registration required)