I've got a strange problem. The problem occured 1 day after I uninstalled the Trend Micro client, I don't think there's a connection, but thats the only thing that has changed on the server.
The people using this server are using Remote Web Workplace. They log in to https://remote.domain.com and click on "Check E-mail", but the "Check E-Mail" link points to http://remote.domain.com/owa without the forward slash at the end. When I try to go to /owa without forward slash at the end the site just loads for a while and I get a message that the site could not be found. I've got the same problem both internally and externally.
I guess this is a IIS problem, but I can't figure it out. I have tried deleting the OWA pages and creating them again with the Exchange Powershell. Help would be greatly appretiated.
Having the slash on the end is actually correct - it's just that IIS sends a redirection response to your browser whenever you supply a directory name (which is what /owa/ is), rather than a document name (e.g. something that ends in .htm or .asp). The first thing I would check is the IIS logs to make sure that IIS responds to your request for /owa with a 302 response, which is its instruction to your browser to redirect to /owa/ .
_____________________________
Lee. ___________________________________
Outlook Web Access for PDA and WAP: www.leederbyshire.com ___________________________________
I have tried looking in the log files, but theres little information. Can I make the logs more verbose?
This line is what got logged when I tried accessing the site without an forward slash after owa: 2010-02-05 14:22:50 192.168.1.10 GET /owa - 443 - 1xx.2xx.xx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 301 0 1236 16033
When I try accessing the page with an forward slash at the end this gets logged: 2010-02-05 14:34:26 192.168.1.10 GET /owa/ - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 401 2 5 34 2010-02-05 14:34:26 192.168.1.10 GET /owa/auth/logon.aspx url=https://remote.domain.com/owa/&reason=0 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 116 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/themes/base/logon.css - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 38 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/themes/base/lgnbotl.gif - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 38 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/themes/base/lgntopr.gif - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 34 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/themes/base/lgnexlogo.gif - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 29 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/themes/base/lgnbotr.gif - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 133 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/themes/base/owafont.css - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 157 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/themes/base/lgntopl.gif - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 174 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/scripts/premium/flogon.js - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 214 2010-02-05 14:34:26 192.168.1.10 GET /favicon.ico - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 404 0 2 30 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/themes/base/lgntopm.gif - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 160 2010-02-05 14:34:26 192.168.1.10 GET /favicon.ico - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 404 0 2 29 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/themes/base/lgnleft.gif - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 231 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/themes/base/lgnright.gif - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 233 2010-02-05 14:34:26 192.168.1.10 GET /owa/8.2.234.1/themes/base/lgnbotm.gif - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 200 0 0 237 2010-02-05 14:34:29 192.168.1.10 GET /favicon.ico - 443 - 1xx.2xx.xxx.xxx Mozilla/5.0+(Windows;+U;+Windows+NT+6.1;+nb-NO;+rv:1.9.2)+Gecko/20100115+Firefox/3.6 404 0 2 29
The first line indicates that the server is asking your browser to redirect (301 or 302 is a redirect response), but since there is nothing following it, your browser isn't behaving as instructed. Have a look in your IE options, and see if redirects are allowed. The option may be listed as 'Allow META refresh'.
When you type the URL without a slash, and the browser eventually displays an error, has any part of the URL you typed into the address bar (e.g. the servername part after the https://) been changed to anything else without you noticing?
The URL does not change. I have installed wireshark now to see where the error occurs.
When I go to http://remote.domain.com/owa I get this reply: 1804 1330.255498 ServerIP MyIP HTTP HTTP/1.1 404 Not Found (text/html)
It doesn't look like I can see the response from the server in clear text when it is HTTPS encrypted.
As previously mentioned this is a SBS 2008 server with Exchange 2007 SP2.
According to the Microsoft SBS 2008 Best Practice analyzer the Exchange Websites is supposed to bee in the "SBS Applications" web site in IIS 7 manager. After I installed SP2 some of the Exchange Web sites is under the "Default Web site"
I have also noticed that if I type an URL I know doesn't exist, for exampe https://remote.domain.com/abc I get an 404 error immidiatly, and the page displayed is the 404 error from IIS If I go to https://remote/domain.com/owa it just loads for a long time and after a while it gives up, now it is the default Internet Explorer 404 error that is displayed.
So it looks like it is trying to redirect, but the URL it is redirecting to may be wrong. I can't see the conversation with wireshark since it is encrypted
< Message edited by glenng -- 8.Feb.2010 5:45:15 AM >
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)
<head><title>Document Moved</title></head> <body><h1>Object Moved</h1>This document may be found <a HREF="https://remote.domain.com/owa/owa">here</a></body>GET /owa HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)
<head><title>Document Moved</title></head> <body><h1>Object Moved</h1>This document may be found <a HREF="https://remote.domain.com/owa/owa">here</a></body>
Did you follow one of those documents that shows you how to redirect your default web site to /owa, so that your users don't need to type /owa on the end of the URL? It looks like that is what is happening, but they don't work with IIS7 - some kind of loop gets created.
_____________________________
Lee. ___________________________________
Outlook Web Access for PDA and WAP: www.leederbyshire.com ___________________________________
Now I only get the standard IIS 404 error when trying to go to http://ip/owa or owa/ http://ip gives me the IIS welcome page. The redirect is gone, but https://ip/owa still doesn't work
If there are several web sites in IIS on the server, I would now check that the Default Web Site (i.e. the one where you say the OWA VDir now is), is the site that's configured to listen on ports 80 and 443; and that the other sites are not.
The last ten or so lines indicate that the server is sending its redirect request, but the browser doesn't seem to be doing anything with it. I would suspect something in the browser's settings, but if all your clients are doing this, then it's obviously not that. Have you tried it from the server itself by going to https://localhost/owa ?
I'm concidering downgrading from SP2 to SP1. There are some known issues with Exchange 2007 SP2 and SBS 2008. How should I proceed to downgrade? If I uninstall Exchange, will all data be erased from the AD user objects?
I think maybe the mess in the IIS sites has something to do with this error. Right now there is some sites that are both in Default Web Sites and in SBS Web Applications, and some of them are just in one of them.
Default Web Site: Exadmin Exchange Exchweb Public
SBS Web Applications: Exadmin Exchange owa Public
I have allready tried deleting and re-generating the OWA sites with the Exchange Shell. After I deleted and "reinstalled" them they only appeared in SBS Web Applicaitons, but after a short period of time some got copied or moved to Default Web Site.
Now it is just confused, I think [PS] C:\Windows\system32>Get-OwaVirtualDirectory
Name Server OwaVersion ---- ------ ---------- owa (SBS Web Applications) DC01 Exchange2007 WARNING: Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directories. This can happen if Outlook Web Access virtual directories were deleted in Internet Services Manager. Verify that you have access to the metabase on the servers listed below. To correct this inconsistency, run the following command: Remove-OwaVirtualDirectory -Identity "Exchweb (SBS Web Applications)". Running this command will remove references to these virtual directories from the Active Directory directory service."Exchweb (SBS Web Applications)" Exchweb (SBS Web Applic... DC01 Exchange2003or2000 Exadmin (SBS Web Applic... DC01 Exchange2003or2000 Exchange (SBS Web Appli... DC01 Exchange2003or2000 Public (SBS Web Applica... DC01 Exchange2003or2000
I used this script to completely remove all OWA virtual directories and reinstall. I got the script on microsoft technet, I had to modify it, because it didn't remove all virtual directories. It's still no go with /owa even after the OWA reinstall
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2007] >> Outlook Web Access >> domain.com/owa not working, but domain.com/owa/ is working 
domain.com/owa not working, but domain.com/owa/ is working - 
RE: domain.com/owa not working, but domain.com/owa/ is ... - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
