Exchange
--
Questions
--
Followers
Top Experts
Exchange 2013 OWA Issues - "Sorry Something went Wrong"
Hi Guys,
Our OWA stopped working 48 hours ago and we have been trying to trouble-shoot it since. There were no changes to the environment, no Windows Updates were run through. The environment has been running without error for the past 9 months.
All of sudden our OWA has stopped working.
Our users come to the login page and once they log in, they get the error
We are running 2 * Exchange 2013 Servers CU2 Build 712.24 and one Exchange 2010 (Build 123.4) for Edge Transport purposes. We have rebuilt the Virtual Directories, removed the Canary AD entries, just about everything we have been able to ascertain from the web, none of which has worked for us.
What's further puzzling is we are able to access the ECP/ EAC without error (and it logs through the OWA.auth).
Any help or insight would be much appreciated.
Our OWA stopped working 48 hours ago and we have been trying to trouble-shoot it since. There were no changes to the environment, no Windows Updates were run through. The environment has been running without error for the past 9 months.
All of sudden our OWA has stopped working.
Our users come to the login page and once they log in, they get the error
:-(
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
Â
Want to be able to use your email when you're offline?
Next time you are connected:
1. At the top of Outlook Web App, next to your name, click Settings
2. Click Offline settings and turn on offline access
3. That's it! You'll never see this message again.
 refresh the page Â
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
Â
Want to be able to use your email when you're offline?
Next time you are connected:
1. At the top of Outlook Web App, next to your name, click Settings
2. Click Offline settings and turn on offline access
3. That's it! You'll never see this message again.
 refresh the page Â
We are running 2 * Exchange 2013 Servers CU2 Build 712.24 and one Exchange 2010 (Build 123.4) for Edge Transport purposes. We have rebuilt the Virtual Directories, removed the Canary AD entries, just about everything we have been able to ascertain from the web, none of which has worked for us.
What's further puzzling is we are able to access the ECP/ EAC without error (and it logs through the OWA.auth).
Any help or insight would be much appreciated.
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Thanks Carol. I have already been through the Spiceworks link.
We have re-created the OWA Virtual Directories a number of times (along with the ECP ones).
Running an CU 3 now to see if that assists...
We have re-created the OWA Virtual Directories a number of times (along with the ECP ones).
Running an CU 3 now to see if that assists...
Good idea....
And reset the Application Pools?
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
The moment OWA stopped working, what was there to see in the error logs?
About Exchange 2013, can we assume SP1 installed?
About Exchange 2013, can we assume SP1 installed?
There was nothing that we could find in the Error logs.
As for SP1 no the environment has not been upgraded as yet.
When opening the OWA on Firefox, it gets to the point of "Opening your mailbox...." before the message appears... So perhaps it's an AD connectivity issue... We cant be sure.
As for SP1 no the environment has not been upgraded as yet.
When opening the OWA on Firefox, it gets to the point of "Opening your mailbox...." before the message appears... So perhaps it's an AD connectivity issue... We cant be sure.
All i can say is make a backup and update the exchange instance.... pretty sure this is the best starting point.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Where is the mailbox? Exchange 2010 or 2013? Was it moved recently.
Have you run the exchange connectivity https://testconnectivity.microsoft.com/
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
So results of the CU update haven't really helped, although it gives more detail on the error message.
All Test Connectivity components come up OK (EWS, RPC, ActiveSync etc).
We have also switched the OWA from premium to lite and now able to access OWA.
Seems the same issue as this post...
http://social.technet.microsoft.com/Forums/exchange/en-US/bdc969e1-e0bc-4413-8a9a-ca61f4d5e7b1/owa-premium-not-working-only-light?forum=exchangesvradmin
@Adam - The AD Attributes look OK to me.
:-(
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
X-OWA-Error: SDServerErr;System.Xml.XmlException
X-OWA-Version: 15.0.775.32
X-FEServer: <<SERVER NAME>>
X-BEServer: <<SERVER FQDN>>
Date: 1/2/1601 3:00:12 PM
less detail...All Test Connectivity components come up OK (EWS, RPC, ActiveSync etc).
We have also switched the OWA from premium to lite and now able to access OWA.
Seems the same issue as this post...
http://social.technet.microsoft.com/Forums/exchange/en-US/bdc969e1-e0bc-4413-8a9a-ca61f4d5e7b1/owa-premium-not-working-only-light?forum=exchangesvradmin
@Adam - The AD Attributes look OK to me.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
We had exhausted all options provided by EE members and engaged Microsoft to work through the issue.
Hello! Also error 500 on https://mail.corp.com/owa/sessiondata.ashx?appcacheclient=0
Response "An unexpected error and was unable to handle the request."
X-OWA-Error: SDServerErr;System.Xml.Xml
Cache-Control: no-cache, no-store
Content-Type: application/x-javascript; charset=utf-8
Date: Mon, 25 Jul 2016 06:01:06 GMT
Expires: -1
Pragma: no-cache
Server: Microsoft-IIS/8.5
Set-Cookie: X-BackEndCookie=S-1-5-21-1
Transfer-Encoding: chunked
X-AspNet-Version: 4.0.30319
X-BEServer: EX02
X-BackEnd-Begin: 2016-07-25T09:01:07.129
X-BackEnd-End: 2016-07-25T09:01:07.223
X-CalculatedBETarget: ex02.corp.com
X-DiagInfo: EX02
X-FEServer: EX01
X-FrontEnd-Begin: 2016-07-25T09:01:06.824
X-FrontEnd-End: 2016-07-25T09:01:06.933
X-FrontEnd-Handler-Begin: 2016-07-25T09:01:06.824
X-OWA-CorrelationId: 20364d4f-7b76-4af8-ad09-4d
X-OWA-Error: System.Xml.XmlException
X-OWA-MinimumSupportedOWSV
X-OWA-OWSVersion: V2_23
X-OWA-Version: 15.0.1210.3
X-OWAErrorMessageID: ErrorUnexpectedFailure
X-Powered-By: ASP.NET
X-UA-Compatible: IE=EmulateIE7
request-id: 94559ce370-e12c-4269-be01-
x-content-type-options: nosniff
Response "An unexpected error and was unable to handle the request."
X-OWA-Error: SDServerErr;System.Xml.Xml
Cache-Control: no-cache, no-store
Content-Type: application/x-javascript; charset=utf-8
Date: Mon, 25 Jul 2016 06:01:06 GMT
Expires: -1
Pragma: no-cache
Server: Microsoft-IIS/8.5
Set-Cookie: X-BackEndCookie=S-1-5-21-1
Transfer-Encoding: chunked
X-AspNet-Version: 4.0.30319
X-BEServer: EX02
X-BackEnd-Begin: 2016-07-25T09:01:07.129
X-BackEnd-End: 2016-07-25T09:01:07.223
X-CalculatedBETarget: ex02.corp.com
X-DiagInfo: EX02
X-FEServer: EX01
X-FrontEnd-Begin: 2016-07-25T09:01:06.824
X-FrontEnd-End: 2016-07-25T09:01:06.933
X-FrontEnd-Handler-Begin: 2016-07-25T09:01:06.824
X-OWA-CorrelationId: 20364d4f-7b76-4af8-ad09-4d
X-OWA-Error: System.Xml.XmlException
X-OWA-MinimumSupportedOWSV
X-OWA-OWSVersion: V2_23
X-OWA-Version: 15.0.1210.3
X-OWAErrorMessageID: ErrorUnexpectedFailure
X-Powered-By: ASP.NET
X-UA-Compatible: IE=EmulateIE7
request-id: 94559ce370-e12c-4269-be01-
x-content-type-options: nosniff
https://social.technet.microsoft.com/Forums/ru-RU/9db69d30-2fd4-4f56-9d9e-dc1cfc5cb06c/owa-error-exchange-2013-cu13-sdservererr-systemxmlxmlexception?forum=exchange2013ru
https://social.msdn.microsoft.com/Forums/en-US/2a78611e-f5e6-4867-b823-12d987a81816/owa-error-exchange-2013-cu13-sdservererr-systemxmlxmlexception?forum=exchangesvrdevelopment
https://social.msdn.microsoft.com/Forums/en-US/2a78611e-f5e6-4867-b823-12d987a81816/owa-error-exchange-2013-cu13-sdservererr-systemxmlxmlexception?forum=exchangesvrdevelopment
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Exchange
--
Questions
--
Followers
Top Experts
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.