Hello everyone, I've got myself quite the problem, I've been trying to figure this one out for weeks.
I am speaking, as the title implies, of OWA on Exchange 2003 running on Small Business Server 2003. What was happening when the problem first occurred is that certain users would get an HTTP/1.1 500 Internal Server error when trying to log in. When investigating things I noticed that this would only occur on user's whose mail box said that the user was the last one to log into the mailbox, and on the ones where it would actually work, such as the administrator account, it would say that it was last accessed by "NT AUTHORITY\SYSTEM". During my troubleshooting I tried the following methods in the links below to no avail.
Tried uninstalling Exchange Update 926666 as stated was the solution by a poster in this thread - http://forums.msexchange.org/m_1800431832/mpage_1/key_/tm.htm#1800488577
, the reference for the update is - http://support.microsoft.com/kb/926666/
At first this appeared to have worked, but it started messing up the following day, I discovered that restarting the HTTP SSL service would get it to work again, this lasted for 2 days, but that also stopped working and I'm back to square one, I checked to see if it had automatically reinstalled the update but its still gone
I've tried nearly every permutation of directory security on all 6 of the virtual directories.
I have also tried this as there were some active sync errors as well -
That article left me with a virtual directory called exchange2. It solved my activesync problems (as far as I know) but OWA is still out of commission.
But despite all of this very limited results which reverted back or none at all were encountered with all of the solutions. This morning at around 10 CST though nothing could be accessed from OWA, you couldn't even authenticate any more, it would just simply give the internal server error 500 as soon as you browse to the site, so I tried what I classified as last resort and did what this article said and deleted the 6 virtual directories and metabase key -
It behaved exactly as the article said it would, after deletion the directories were recreated and everything appeared
to be good. But when i tried to access OWA it was still the same 500 internal server error page before even asking to login. So I went back and retried all of the previously mentioned solutions to see if trying them on fresh virtual directories would make a difference. When I tried the one that had me add them all to the exchangeapplicationpool again this got the limited functionality that I had before back, where i could authenticate with users last logged onto by the "NT AUTHORITY\SYSTEM" but anyone who had their username or anyone else's username listed as the last logged on by is not able to access it. So basically I'm back at square one, and I'm not sure where to go from here. I thank everyone in advance for any help they can provide, and if I can provide any additional information please let me know.