We help IT Professionals succeed at work.

Issue accessing OWA Exchange 2013

When accessing OWA on Exchange 2013. We can enter our credentials, it accepts them. but we end up at a 404 can't find page - The page you're looking for couldn't be found on the server.

X-Clientid:
X-FEServer: ServerName
Date: todays date.

I can then click refresh the page and it loads owa just fine. Can anyone tell me why each mailbox gets a 404 error page first when signing in?

Thank you
Comment
Watch Question

Rajkumar DuraisamyRajkumar Duraisamy (Rajkumar-MCITP)
Top Expert 2012

Commented:
How many servers you have and accessing load balanced OWA url like https://mail.domain.com/owa ?

Or single server environment?

If LB url, try to put a host entry for mail.domain.com for one exchange server first and check the owa..

Do the same till you get the error to isolate the server having issue..

On the server have issue.. remove from lb and check the server health etc..
Server engineer
BRONZE EXPERT
Commented:
Go to IIS under default website and backend website check site bindings and make sure a valid certificate is present on both 443 and 444.

Causes of Exchange Admin Center Http 404 Error
The above error is caused due to incorrect authentication. When user set OWA or ECP Virtual directories with cmdlet New-OWAVirtualDirectory or New-ECPVirtualDirectory then Form or Basic Authentication is enabled in place of Windows Authentication. This error triggers issues, therefore user unable to open OWA and ECP Virtual Directory.

How to Solve Outlook Web Access and Exchange Admin Centre Http 404 Issue
To Solve above problem user need to follow two different ways to resume functioning of OWA and ECP Virtual directory.

For Outlook Web Access (OWA) Virtual Directory
Follow the Steps given below to remove outlook web access http 404 issue from virtual directories.


Open Exchange Management Shell.

Now, Copy paste or Type cmdlet given below and press Enter

set-Owavirtualdirectory -identity "E15MBX\owa (Exchange Back End)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false

Now, Run following cmdlet on Client Access and Mailbox Server.

iisreset /noforce

The Above command is used to restart Internet Information Services (IIS) at both ends.

Author

Commented:
Saif,

I'm assuming I replace E15MBX in this line with the name of my server, or no?

set-Owavirtualdirectory -identity "E15MBX\owa (Exchange Back End)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false
Saif ShaikhServer engineer
BRONZE EXPERT

Commented:
Yes you are correct...

You can take the identity by running command:

get-owavirtualdirectory | fl *ur*, name, identity.

Author

Commented:
Saif,

Since this is currently a co-existence environment with 2007/2013 - when issuing the above command, how can I tell which one is the back end that I need to be changing?

Thanks
Saif ShaikhServer engineer
BRONZE EXPERT

Commented:
You need to change 2013 one and that is from the identity parametric that needs to be changed.