OWA - Outlook Web App isn't available.

I would recommend upgrading to SP3.

Cant do that right now -- any other ways around this?

Don't upgrade to any service pack, first you reboot your exchange server and check again. Look for errors in Application logs related to  OWA.

OK - rebooted and this is what I get when trying to login through OWA on EX-02.

The Client Access server "" attempted to proxy Outlook Web App traffic for mailbox "". This failed because no Client Access server with an Outlook Web App virtual directory configured for Kerberos authentication could be found in the Active Directory site of the mailbox. The simplest way to configure an Outlook Web App virtual directory for Kerberos authentication is to set it to use Integrated Windows authentication by using the Set-OwaVirtualDirectory cmdlet in the Exchange Management Shell, or by using the Exchange Management Console. If you already have a Client Access server deployed in the target Active Directory site with an Outlook Web App virtual directory configured for Kerberos authentication, the proxying Client Access server may not be finding that target Client Access server because it does not have an internalUrl parameter configured. You can configure the internalUrl parameter for the Outlook Web App virtual directory on the Client Access server in the target Active Directory site by using the Set-OwaVirtualDirectory cmdlet.

What does you output look like when you do a Get-OWAVirtualDirectory | FL

Also, are these 3 servers in the same AD Site?

OK I'm downloading the cumulative package now.

when I run get-owavirtualdirectory | fl I get a lot of output and cannot see all the information.  What am I looking for here?

2 Exchange server in 1 site - 1 exchange server in a different site -- All under the same domain name.

Are these errors in the Event Log always center around the server in its own site?

What roles are on each server?

Yes, centered around its own site.  If I'm on the DR site network and do a https://ex-03/owa  -- I can login just fine.

However, if I try to access https://ex-01/owa or https://ex-02/owa I cannot get logged in.

All servers have the HUB, CAS, Mailbox roles installed.

Results of:   GCM exsetup |%{$_.Fileversioninfo}


EX-01 (Main Site) -  14.02.0247.005 (ProdVer) -- 14.02.0247.005 -- (FileVersion -- C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe

EX-02 (Main Site) - 14.02.0298.004 (ProdVer) -- 14.02.0298.004 -- (FileVersion -- C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe

EX-03 (DR Site) - 14.02.0247.005 (ProdVer) - 14.02.0247.005  (FileVersion -- C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe

Friday last week, EX-01 had some problems and we had to rebuild.  We had equipment ready for EX-03 at the DR site.  Once we lost EX-01, we put it in high gear to get both EX-01 and EX-03 up and running.

Currently all DNS records are pointing to EX-02 for client access (external & internal) -- we don't have any LBs in our environment.

Seems like OWA was ok since then but then last night we noticed these problems.  Mobile devices can still connect via ActiveSync -- just OWA is hosed up.

Ya, because now you have different version of OWA directory. You can copy them from old server and paste it on Ex02 under binary path>CAS folder. If this sound bit complicated, upgrade other 2 to same version.

Any luck on getting CU2 installed yet?

The information provided was great! Thank you, I was in caught between a rock and a hard place and everyone's information would truly helpful!

Thank you!!!!

Glad you got it resolved!