Creating a 2nd OWA site kills the first - 500 Internal Error

Posted on 2010-01-09
Medium Priority
Last Modified: 2012-05-08

I have an Exchange 2007 server with SP2 sitting behing ISA 2006 and all is working fine. OWA is only using basic and windows authentication.
I need to create a 2nd owa website using just basic authentication. I have created the 2nd virtual directory through Power Shell (new-owavirtualdirectory -name owa2 -websitename 2ndsitename) with success and it shows in both Exchange console and IIS. However the first OWA dies with a 500 internal error. The only way to get the first OWA working again is to remove the 2nd OWA virtual directory in Power Shell.

Please help
Question by:CatsSolutions
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
LVL 15

Expert Comment

ID: 26272877
The first thing to check is the event logs.  Anything in application or system logs when the 500 error is generated?  Also, you can usually get additional details from a 500 error by disabling friendly HTTP error messages in IE.  Go to tool-->internet options--->advanced and clear the check box next to 'Show Friendly HTTP Error Messages.'  Restart your browser and hit the site again to see if you get a more detailed error message that will point you towards a resolution.
LVL 15

Expert Comment

ID: 26273175
Whay you want to create second OWA site ? any specific reason ?
It is happening becuase for OWA only one vertual directory can be used and that is something you define in ESM.

ESM > ORG config > CAS > OWA > and then set the url..

What is the need ?

Author Comment

ID: 26273695
We need one access to have Windows authentication and another access to be just basic authentication.

Author Comment

ID: 26273707
Microsoft states that multiple OWA sites can be used as long as none of them use forms based authentication, whihc we are not using as ISA does this for us.

Accepted Solution

CatsSolutions earned 0 total points
ID: 26277011
I have sorted this. It was a bit of a stupid mistake on my part.

Because we had two OWA websites we gave the server two IP addresses. ISA was routing to the server name and not specific IP address so did not know which website to go to.

Thanks for your comments anyway

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Preparing an email is something we should all take special care with – especially when the email is for somebody you may not know very well. The pressures of everyday working life stacked with a hectic office environment can make this a real challen…
New style of hardware planning for Microsoft Exchange server.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question