Exchange 2007 OWA – Error 404 – File or Directory not found.
Let me give you a brief background before we jump into the error.
We are in the middle of migrating Exchange 2003 to Exchange 2007. In order to make the migration as seamless as possible, we have setup an ISA 2006 Enterprise Array to service the new Exchange 2007 Exchange Web Services. We decided to use a redirect for https://owa.domain.com/exchange as on of the OWA Publishing Rules. It was setup as a deny rule, whereas all traffic to owa.domain.com would be redirected to https://owa.domain.com/exchange. This achieved several things.
1.) We are able to support multiple domains and URLs. The trick is to point all other DNS names, such as owa.domain1.com or webmail.domain3.com to the owa.domain.com IP. The redirector will take care of the rest.
2,) This allows us to support both Exchange 2003 or 2007 mailbox users. /OWA is the default directory for Exchange 2007, but it will support /Exchange for legacy servers. By using the /Exchange path, any user homed on either Exchange version will be able to login to Exchange. (I will have another post soon going into detail on how to setup ISA 2006 and Exchange 2007 Publishing Rules)
Having said all of this, we had an Exchange 2007-Windows 2008 CCR Cluster up and running. It was working as expected. One of our admins accidently deleted all of the WebDav or OWA virtual directories from the Backend server. Since we were using the /Exchange path, OWA stopped working on users homed on that server. It also affects Free/Busy and Calendaring.
Users would likely receive the following error:
The gotcha was OWA would work if we passed the /OWA path…..
This article goes into detail on the symptom:
Your mailbox is located on a server that is running Microsoft Exchange Server 2007. You use Windows Internet Explorer to try to connect to Microsoft Office Outlook Web Access against a server that has the Client Access Server (CAS) role installed by using the <server url>/exchange URL. However, you receive the following error message:
404 The page cannot be found.
The connection is successful if you connect to Outlook Web Access by using the /owa virtual directory.
If you try to connect by using Microsoft Entourage 2004 or a later version of Microsoft Entourage, the operation is unsuccessful. Additionally, you receive the following error message:
No resources found for this account.
The error is a direct result off the three OWA virtual directories not being present. Follow the recipe in the article to check and see if the HTTP virtual directory exists. If not, create the new msExchProtocolCfgHTTPContainer object and pass it the HTTP value mentioned in the article.
Once complete, on the Exchange 2007 backend server, issue these commands.
New-OWAVirtualDirectory -OwaVersion:Exchange2003or2000 -VirtualDirectoryType Mailboxes -Name "exchange" –website “Default Web Site”
New-OWAVirtualDirectory -OwaVersion:Exchange2003or2000 -VirtualDirectoryType PublicFolders -Name "public" –website “Default Web Site”
New-OWAVirtualDirectory -OwaVersion:Exchange2003or2000 -VirtualDirectoryType Exadmin -Name "exadmin" –website “Default Web Site”
You should now be able to log back into OWA using the /Exchange path for users homed Exchange 2007.