OWA 500 error

I am getting a 500 error after logging into the OWA logon screen.  If i try to access OWA via the xxx.com/exchange url, i get an NT authentication box which will allow me to access my mailbox.  I am still in testing mode and have not yet uncovered any additional issues as of yet.
ABMSTechAsked:
Who is Participating?
 
ryansotoConnect With a Mentor Commented:
i guess i dont understand the only way to log onto OWA is through /exchange way
Now you can simply the URL so your users dont have to type in the /exchange just http://exchangeserver


To simplfy URL
http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx
0
 
ryansotoCommented:
So when you go to domain.com/exchange and log in it works OK?
When you go to domain.com is when the 500 error happens?
I would turn on forms based authentication
http://www.petri.co.il/configuring_forms_based_authentication_in_exchange_2003.htm
Also are you using SSL...
0
 
ABMSTechAuthor Commented:
not currently using SSL.  I am building a new environment and have not moved that over as of yet.
Also, Exchange is not installed on the www.domain.com server.  Should I install Exchange on the web server as well?  I am working on turning on forms-based authentication.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
ryansotoCommented:
No no need to install exchange twice.
What happens when you go to xxx.com/exchange
You should get a log in box put in domain\username and then the password does it work?

Also when you switch on forms based auth make sure to add the domain so your users dont need to the "domain\" anymore
http://www.msexchange.org/tutorials/OWA2003Forms-based-Authentication-default-domain.html
0
 
ABMSTechAuthor Commented:
Great.  I didn't think I needed to install Exchange on the www server.  You are correct regarding xxx.com/exchange.  I am not ready to setup SSL, for I do not have a CA signed certificate.  We had a self signed cert only in our current environment.
I do want to setup SSL, but don't think that will happen today.
Back to the issue at hand.  I had to create 2 Virtual Directories on my www server to point to /exchange (this works after basic authentication) and http://exchangeserver/exchweb/bin/auth/owalogon.asp.  This is were I get the OWA logon screen but after putting in my credentials, I get the 500 error.
I
0
 
ryansotoCommented:
You should nto have to create any new virtual servers.  If xxx.com/exchange works
then all you need to do is simplfy the URL
http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx
0
 
ABMSTechAuthor Commented:
this has been done with redirection via redirects.  The /exchange redirect works, but the other virtual directory that I created to access the owa login screen gives me the 500 error.  How can I fix that?
0
 
ABMSTechAuthor Commented:
I found another string on this site indicating that I should delete all of the owa virtual directories and then recreate them.  What do you think?
0
 
ryansotoCommented:
Thats not an issue at all.  When initially setting mine up I messed something up so I had to redo it.
I used this article though, I didnt just delete
http://support.microsoft.com/kb/883380
0
 
ABMSTechAuthor Commented:
I have completed the 883380 support article and still getting the same 500 error when trying to access exchweb.
0
 
ryansotoCommented:
Ok so going to http://exchangeserver/exchweb/bin/auth/owalogon.asp. is where you get the 500 error?
0
 
ABMSTechAuthor Commented:
correct.  I can get to that logon screen, but when I try to authenticate it fails with the 500 error.
0
 
ryansotoCommented:
Why are you going there instead of just
http://servername/exchange
0
 
ABMSTechAuthor Commented:
In the current SBS environment, that is the logon screen that the users see.  Plus, i feel that the other way I'm trying to do should work.
0
 
ryansotoCommented:
Yes but there is some redirecting that goes on.  You need to access it the way I showed.
You can shorten the url though but thats it
http://technet.microsoft.com/en-us/library/aa998359.aspx
0
 
ABMSTechAuthor Commented:
I am really sorry i just don't get it, if I can get to the OWA logon screen, regardless of how I got there, why shouldn't i be able to get past the 500 error and see my mailbox? When I point them to the /exchange path, they get a basic authentication window and then you click OK then wham, your in your mailbox within OWA.  No OWA logon screen.
0
 
ryansotoCommented:
http://exchangeserver/exchweb/bin/auth/owalogon.asp  <------ you
http://exchangeserver/exchange  <------ default
2 totally different virtual servers


You have to hit the exchange virtual server you cant go directly to the exchweb virtual server.





0
 
ABMSTechAuthor Commented:
so how can i get my users to get the OWA logon screen? and not the way /exchange logs you on?
0
 
ABMSTechAuthor Commented:
I got it to work finally.  I added the owalogon.dll to the Isapi filter, then added SSL.  All is good now.  Thank you so much for your assistance and patience with me.
Thanks,
Adam
0
All Courses

From novice to tech pro — start learning today.