OWA doesn't work internally - something went wrong
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
February 23rd, 2015 1:49pm
Do you have set up mail record in AD DNS which points to Exchange server?
Clear cache in DNS, Restart, and also restart IIS..
February 23rd, 2015 2:19pm
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.
February 23rd, 2015 2:21pm
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:
2961715
"Something went wrong" error in Outlook Web App may show an incorrect date
February 23rd, 2015 2:41pm
Yes I saw this article, the update to apply is CU6, I have CU7.
Thanks.
February 23rd, 2015 2:54pm
Cumulative Update 7 for Exchange Server 2013 (KB2986485)
-
Edited by
Bulent Sahin
15 hours 56 minutes ago
link edited
February 23rd, 2015 2:56pm
Yes, I have applied CU7 for Exchange 2013.
February 23rd, 2015 3:01pm
Since it works externally and does not internally we need to look at the differences between the two methods. Do users get redirected to the same machine when they connect externally as they do internally? Did anything change internally at all? Has
this ever worked?
February 23rd, 2015 3:47pm
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...
February 23rd, 2015 4:36pm
Cumulative Update 7 for Exchange Server 2013 (KB2986485)
-
Edited by
Bulent Sahin
Monday, February 23, 2015 7:55 PM
link edited
February 23rd, 2015 7:55pm
Cumulative Update 7 for Exchange Server 2013 (KB2986485)
-
Edited by
Bulent Sahin
Monday, February 23, 2015 7:55 PM
link edited
February 23rd, 2015 10:55pm
Cumulative Update 7 for Exchange Server 2013 (KB2986485)
-
Edited by
Bulent Sahin
Monday, February 23, 2015 7:55 PM
link edited
February 23rd, 2015 10:55pm
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
February 24th, 2015 5:41am
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.
February 24th, 2015 4:58pm
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
February 24th, 2015 5:38pm
Hi,
Internal URL is https://mail.domain.com/owa, same as external. In DNS/AD Integrated servers it points to the Exchange Server.
Thanks.
February 24th, 2015 6:14pm
Just tried but nothing... Same issue.
February 24th, 2015 7:27pm
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
February 26th, 2015 9:55pm
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.
February 27th, 2015 10:55am
I get another error in some machines:
:-(
hubo un problema
Lo sentimos. No podemos obtener esa informacin en este momento. Intntalo nuevamente ms tarde. Si el problema contina, pngase en contacto con el departamento de soporte tcnico.
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.
February 27th, 2015 11:14am
This is only internally right? Can you connect to OWA locally on an Exchange server? If that works then I would suggest looking at the underlying network and see if something is coming in and causing a problem.
February 27th, 2015 11:17am
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.
March 9th, 2015 3:56pm
Hi, I have the same problem! Do you fixed it?
Thanks!
Aurlien
April 1st, 2015 9:10am
Since CU8 is out now, has anyone who's experiencing this issue installed CU8 and confirmed that it's still broken?
April 1st, 2015 9:44am
It just start working for us...
No CU8 yet...
April 1st, 2015 7:46pm
It just start working for us...
No CU8
April 2nd, 2015 10:37am
Sorry really I don't know, we didn't change anything...
April 2nd, 2015 10:54am