OWA on exchange 2007, 500 - Internal server error.

Server Error
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.

Please help me with Exchange 2007 running on windows 2008 STD box, when I try to access Https://mail.mydomain.com/owa i get the above error?

This is a standalone server (single server) running Windows 2008 STD with Exchange 2007 STD, email is working fine and so are a few web sites hosted on the same box.
Who is Participating?

Improve company productivity with a Business Account.Sign Up

ctrunk514Connect With a Mentor Author Commented:
Ok i found the problem is was not the SLL Cert!


this fix it and its working now

Thank you everone...
Hello ctrunk514,

Check to see if your IIS service is running.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Make sure you are using a valid SSL certificate and that it is propagating to all child nodes in IIS. Error 500 will occur in HTTPS when the SSL certificate is not valid and propagated correctly.
and this one specifically- http://www.petri.co.il/forums/showthread.php?t=29077.  The previous one was for 2003 instead of 2007.
ctrunk514Author Commented:
Thanks everone for all the fast replys, im still geting the error :-(
I do not have a SSL Cert and i dont want to pay for one do i really need one?
ctrunk514Author Commented:
When i try to access OWA from the server it self i get a diffrent error

HTTP Error 500.0 - Internal Server Error
Calling LoadLibraryEx on ISAPI filter "C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\auth\owaauth.dll" failed

Module IIS Web Core
Notification Unknown
Handler StaticFile
Error Code 0x800700c1
Requested URL https://2008mail:443/owa 
Physical Path C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa
Logon Method Not yet determined
Logon User Not yet determined

Most Likely Causes
IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
IIS was not able to process configuration for the Web site or application.
The authenticated user does not have permission to use this DLL.
The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.

If you dont plan on using a SSL Cert then you will need to use http or RPC.
and http will tranfer user information in plain text. This options is not recommended for external access.
ctrunk514Author Commented:
do you really think this is my problem? is there a way to test that is it the true problem befor paying for a cert?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.