Hi all, We are experiencing problems logging on to our OWA website. When you go to the page, the logon screen appears, you type in your credentials, it starts loading and then IE displays the "HTTP 500 internal server error" message. Everytime when I try this, the application log of the server displays following message : DAVEX to be shutdown. Version: 6.5.7654.12 (event ID 101) I tried it from different clients, inside and outside the LAN, even from the server itself, nothing works. Rebooting the Exchange server did not work either. Also tried a lot of solutions I found online, like recreating the virtual directories or clearing the IIS Temporary Compressed Files folder, but no solution yet. Funny thing is, it worked for a brief period during my troubleshoot process, but stopped working again. And I can't get it back running. Very frustrating! The server operates on SBS 2003 SP2 with Exchange 2003 SP2 (build 7638.2). What strikes me is the difference in build number compared to the Davex dll. Could this maybe cause the problem? I tried searching for a same version on the server, but found nothing. All help and hopefully a solution for this issue would be extremely appreciated. Greetings and thanks in advance, Johan

Give this a try: https://www.testexchangeconnectivity.com/Default.aspx.

Give this a try: https://www.testexchangeconnectivity.com/Default.aspx.

Thanks for the link, looks very useful but it doesn't work for Exchange 2003.

Another thing that I noticed: When I look in the IIS Temporary Compressed Files folder, I only see files with version 6.5.7651.60 in the file name. This is yet another version number than Davex and the Exchange build number (watch first post). Is this normal??

Allright cool, after recreating the virtual directories again (http://support.microsoft.com/?id=883380) I can access OWA again. But there's still a little problem : When I access the site from within the network with http, everything is ok. If I try to access the site with https (from internal), it also seems to be working but I get an error about the certificate not being valid. When I retry, I get the HTTP 500 error again, also when I try to access the site with http. If I restart IIS, it's working again. You think if I install a new and valid certificate things will keep working? Thanks!

Hi Johan, Yes, you can request a certificate and install it on the server. If you have an internal CA, you can apply the certificate as follow: SSL Enabling OWA 2003 using your own Certificate Authority http://www.msexchange.org/tutorials/SSL_Enabling_OWA_2003.html A 3rd party certificate is better.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Johan, Any updates?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Frank, I ordered a new SSL certificate but I still have to install it on the server. When it's done I'll post an update. Thanks for your help!

Hi Johan, How about your question now?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Frank, Still waiting for the license I ordered... Hope to give an update asap.

Hi Frank, Finally an update about this : The SSL certificate is in place and is working correctly, but at first I still had the same problem as before. After disabling "forms based authentication" in the Exhange System Manager, eveything is working fine. But this implies that I now log on with a password popup screen instead of the OWA webform. Is this bad? Greetings, Johan