Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 295
  • Last Modified:

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

HI,

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
0
CatsSolutions
Asked:
CatsSolutions
  • 3
1 Solution
 
Tray896Commented:
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.
0
 
Narayan_singhCommented:
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 ?
0
 
CatsSolutionsAuthor Commented:
We need one access to have Windows authentication and another access to be just basic authentication.
0
 
CatsSolutionsAuthor Commented:
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.
0
 
CatsSolutionsAuthor Commented:
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
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now