When trying to access OWA from internal network (external access is working):

:-(

something went wrong

Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.

X-ClientId: NTAW - FMWI - PEOS - SRAWOFA
X-OWA-Error: Unknown;handle boot error failed
X-OWA-Version: undefined
X-FEServer: <server_name>
X-BEServer: undefined
Date: 2/23/2015 6:47:33 PM

T

Do you have set up mail record in AD DNS which points to Exchange server?

Clear cache in DNS, Restart, and also restart IIS..

Yes I have a A record (mail.domain.com) which points to Exchange.

DNS resolution is ok. I have restarted IIS on the server.

It's Exchange 2013 with CU7.

Thanks.

The date information is calculated based on the date of the Exchange server to which the user is connected. In some scenarios (such as network connectiivy failure), the Outlook Web App client-side script is unable to connect to the server to obtain the correct date.

Please download the update

http://www.microsoft.com/en-us/download/details.aspx?id=44022

This update resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

Yes I saw this article, the update to apply is CU6, I have CU7.

Thanks.

Cumulative Update 7 for Exchange Server 2013 (KB2986485)

• Edited by Bulent Sahin 15 hours 56 minutes ago link edited

Yes both users (ext and int) are redirected to the same Exchange server. I applied CU7 2 weeks ago. And yes, It has been working since we installed the server.

For External users we have a ISA Server 2006 SP1.

Also I tried to reset OWA Virtual Directory and it didn't fix it (obviously if it works externally...).

ECP is working...

Cumulative Update 7 for Exchange Server 2013 (KB2986485)

• Edited by Bulent Sahin Monday, February 23, 2015 7:55 PM link edited

Cumulative Update 7 for Exchange Server 2013 (KB2986485)

• Edited by Bulent Sahin Monday, February 23, 2015 7:55 PM link edited

Cumulative Update 7 for Exchange Server 2013 (KB2986485)

• Edited by Bulent Sahin Monday, February 23, 2015 7:55 PM link edited

Hi Dario,

I have seen some people have the same issue with yours. In your case, please try to reboot the ISA server and check the result. Sometimes, ISA servers are not able to interact with each other. Rebooting the ISA server often resolves the OWA  access issue.

Hope this can be helpful to you.

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi Amy!

I think it's not an issue on the ISA Server.

If I try to access from Internet it works.

We have this issue when we try to access OWA in our LAN, and here we go directly to our Exchange Server.

Thanks.

Hi Dario,

Could you please check internal url under virtulal directory

Go To ECP Console->Servers-> Virtual Directories -> Click OWA (Default Web Site) -> click Edit -> In General TAB

Look at the  internal URL, Copy that url and paste to browser

Try now.

Regards,

Joby

Hi,

Internal URL is https://mail.domain.com/owa, same as external. In DNS/AD Integrated servers it points to the Exchange Server.

Thanks.

Could you please slightly change internal link https://fully qualified machine name.com/owa instead of https://mail.domain.com/owa  and apply that. then try to browse. It wont impact any email flow

Regards,

Joby

Hi Dario,

In your case, ECP is working well, only OWA doesn't work well internally. I recommend you make sure that OWA Authentication method (default is Basic authentication) and SSL settings (default is SSL required) are right. When you upgrade Exchange server, the IIS settings are reset.

Hope my clarification can be helpful to you.

Best regards,

If you have feedback for TechNet Subscriber Support, contact  tnmff@microsoft.c

Auth settings are the same:

[PS] C:\Windows\system32>Get-OwaVirtualDirectory | select *auth*

ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}

ClientAuthCleanupLevel        : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}

[PS] C:\Windows\system32>Get-EcpVirtualDirectory | select *auth*

InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}

InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}

On IIS for Default Web Site, OWA VD have Basic Auth. For Back End Web Site have Anonymous and Windows Auth.

The same for ECP and all have require SSL.

I get another error in some machines:

X-ClientId: JGTO - TBXF - 0MHQ - NQQVUVROQ
X-OWA-Error: ClientError;exMsg='jQuery' no est definido;file=ReferenceError: 'jQuery' no est definido
   at Global code (https://correo.tabacal.com.ar/owa/prem/15.0.1044.25/scripts/boot.0.mouse.js:70:2):83
X-OWA-Version: undefined
X-FEServer: ARBUEDCEXC01
X-BEServer: undefined
Date: 27/02/2015 04:13:48 p.m.

Sorry for the delay.

Yes it's only internal. Also we can't connect locally on the Exchange Server so I think it's an internal error on the OWA site, not networking issue.

Hi, I have the same problem! Do you fixed it?

Thanks!

Aurlien

It just start working for us...

No CU8 yet...

It just start working for us...

No CU8