OWA on Production Server DIED (Full Version)

All Forums >> [Microsoft Exchange 2007] >> Outlook Web Access



Message

stefshuuj -> OWA on Production Server DIED (31.Dec.2007 4:56:33 AM)

Hi All,
 
I recently had a problem with .net framework on my exchange 2007 server.
I have Windows 2003 Server Standard Edition with IIS 6.0
 
I had to remove .net framework 2 and 3 from the server and then reinstall them.
 
Since re-installing, my email is up and running ok again, but webmail has stopped working. This is a problem as some remote staff use webmail for production purposes.
 
Webmail fails from both inside my network and from home.
 
Please any ideas would be greatly appreciated. The person who initially configured the servers is unavailable for the next week and I need to fix this asap.
 
The error i am getting is:
 
The page cannot be found
The page you are looking for might have been removed, had its name changed, or is temporarily unavailable.


Please try the following:
  • Make sure that the Web site address displayed in the address bar of your browser is spelled and formatted correctly.
  • If you reached this page by clicking a link, contact the Web site administrator to alert them that the link is incorrectly formatted.
  • Click the Back button to try another link.

HTTP Error 404 - File or directory not found.
Internet Information Services (IIS)


Technical Information (for support personnel)
  • Go to Microsoft Product Support Services and perform a title search for the words HTTP and 404.
  • Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled Web Site Setup, Common Administrative Tasks, and About Custom Error Messages



bhopkins -> RE: OWA on Production Server DIED (31.Dec.2007 10:21:41 AM)

My guess would be you need to register asp.nert since you unisntalled it. Go into Windows\Microsoft.Net\Framework\v2.0.xxxxx( replacing the xxxs with your 2.0 directory name) from the command line and run this command aspnet_regiis -i

This will recreate the asp.net maps to your OWA website. You may want to check afterwards in IIS manager and ensure you have the correct setting for Asp.Net in your owa virtual directory properties.

hth
Bruce



stefshuuj -> RE: OWA on Production Server DIED (4.Jan.2008 6:43:29 AM)

Hello,

Thanks for earlier reply. Sorry for the delay in responding. Went away to see family for holidays.

When I go into \Windows\Microsoft.Net\ - I have Framework and Framework64

Which of the two should I run the regiis against?

Thanks



stefshuuj -> RE: OWA on Production Server DIED (6.Jan.2008 2:17:48 AM)

I have tried the aspnet_regiis -i from the framework64 directory. It completed successfully but didn't correct anything.

The IIS Settings look correct, but I am not certain of them as I did not do the initial install.

Any ideas anyone?

Thanks



rvaglid -> RE: OWA on Production Server DIED (6.Jan.2008 7:55:38 AM)

Hi, do you get any errors or warnings in the eventlogs?

I've experinced OWA-trouble caused by IIS running in 32-bit mode, when OWA requires IIS in 64-bit mode.

Try this: http://support.microsoft.com/kb/894435

Cheers
Rolf



stefshuuj -> RE: OWA on Production Server DIED (8.Jan.2008 8:34:43 AM)

Hello again,

Sorry for the delay in reply posts all. I am trying to enjoy having family over for the holidays while trying to fix this. Fortunately the few staff using owa for production purposes are still on holidays.

I have been digging and I am part way there. In IIS there of a directory called "Web Service Extensions". In here the ASP.Net Extension was set to PROHIBITED.

Now that I have set that to ALLOW, I can get to the OWA Login Page.

However when I try to login, I receive the error:

***
The website declined to show this webpage
HTTP 403
Most Likely Causes:
This Website Requires you to login

This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.
For more information about HTTP errors, see Help
***

Any further ideas would be great. Appreciate the help thus far



rvaglid -> RE: OWA on Production Server DIED (8.Jan.2008 9:13:59 AM)

It seems your authentication settings are messed up. Take a look at these.
You might want to take a backup for the sites in iis.msc first.

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1456690&SiteID=17

http://technet.microsoft.com/en-us/library/bb124811.aspx

Cheers
Rolf



stefshuuj -> RE: OWA on Production Server DIED (8.Jan.2008 8:53:07 PM)

I have run the Get-OwaVirtualDirectory Command and I receive:

Name:                                                      OWA Version
 
owa (Default Web Site)                         Exchange 2007
Exchange (Default Web Site)               Exchange 2003or2000
Public (Default Web Site)                     Exchange 2003or2000
Exchweb (Default Web Site)                Exchange 2003or2000
Exadmin (Default Web Site)                 Exchange 2003or2000
owa (OWA)                                            Exchange 2007
 
The first owa sits under the Deault Web Site, the second owa sits parallel to the defaulty web site.

Before I run the remove-owavirtualdirectory, Is it standard to have the two OWA Virtual Directories or is something wrong here?



stefshuuj -> RE: OWA on Production Server DIED (11.Jan.2008 8:03:28 AM)

Hello again,
 
I am slowely figuring this out but still not quite there.
 
As stated above:
 * I have the "Default Web Site" with an OWA Virtual Directory under it.
 * I have an "OWA Web site" with an OWA Virtual Directory under it.
 
When I stop the OWA Web Site, I cannot even get a login screen. So I belive this is probably the one I am using for production.
 
Should I even have this OWA Web Site with an OWA Virtual Directory?



stefshuuj -> RE: OWA on Production Server DIED (12.Jan.2008 6:00:24 AM)

Hello all,
 
Problem is solved. I removed the OWA Virtual Directory within the OWA Website and re created it. This FIXED the problem.
 
I still do not understand why I have the owa under Default Web Site and OWA under OWA Web Site. So needless to say I will be setting up a test exchange server in the near future so that I can understand the whole process.
 
Thanks everyone for the posts.
Have a great 2008
 
Stephen



Page: [1]