Solved

Exchange 2013 OWA Issues - "Sorry Something went Wrong"

Posted on 2014-07-20
16
5,832 Views
Last Modified: 2016-07-24
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

:-(

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.
0
Comment
Question by:maccadu
  • 5
  • 4
  • 3
  • +2
16 Comments
 
LVL 16

Assisted Solution

by:Carol Chisholm
Carol Chisholm earned 166 total points
ID: 40206986
If it's all users: web site bindings in IIS?
http://community.spiceworks.com/topic/348158-exchange-2013-ecp-owa-issue-something-went-wrong

Have you tried another device ?

There are separate virtual directories for just about everything.

Here's a link about migrations, but yours is an established system:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Q_28252720.html
0
 

Author Comment

by:maccadu
ID: 40206994
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...
0
 
LVL 16

Expert Comment

by:Carol Chisholm
ID: 40207025
Good idea....
0
 
LVL 16

Expert Comment

by:Carol Chisholm
ID: 40207027
And reset the Application Pools?
0
 
LVL 19

Expert Comment

by:Patricksr1972
ID: 40207151
The moment OWA stopped working, what was there to see in the error logs?
About Exchange 2013, can we assume SP1 installed?
0
 

Author Comment

by:maccadu
ID: 40207171
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.
0
 
LVL 19

Expert Comment

by:Patricksr1972
ID: 40207191
All i can say is make a backup and update the exchange instance.... pretty sure this is the best starting point.
0
 
LVL 19

Expert Comment

by:Adam Farage
ID: 40207484
Where is the mailbox? Exchange 2010 or 2013? Was it moved recently.
0
 
LVL 16

Expert Comment

by:Carol Chisholm
ID: 40207536
Have you run the exchange connectivity https://testconnectivity.microsoft.com/
0
 
LVL 19

Assisted Solution

by:Adam Farage
Adam Farage earned 334 total points
ID: 40207562
So I think this is one of two things, either a permissions issue between the Exchange servers (2010/2013) or an ad replication issue... I would check the users ad object via adsiedit and then determine if the attributes (msExchangeVersion and homeMBD) show the proper values for exchange 2013..
0
 

Author Comment

by:maccadu
ID: 40208073
So results of the CU update haven't really helped, although it gives more detail on the error message.

:-(
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...

Open in new window



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.
0
 
LVL 19

Assisted Solution

by:Adam Farage
Adam Farage earned 334 total points
ID: 40208085
if the X-FEServer and X-BEServer are showing properly, then you know its attempting a connection to Exchange 2013... usually Fiddler trace would show this, but in this case I think you would see an HTTP 500 ISE thrown back (ISE = Internal Server Error).

Could it be time related by change? I saw this, and I never see it in this format:

Date: 1/2/1601 3:00:12 PM
0
 

Accepted Solution

by:
maccadu earned 0 total points
ID: 40223769
We ended up getting Microsoft engaged to complete the works.

From what we can understand the issue was with the WAC Server end point configuration and perhaps an initial issue with accessing our AD.

Thanks for the suggestions above.
0
 

Author Closing Comment

by:maccadu
ID: 40235882
We had exhausted all options provided by EE members and engaged Microsoft to work through the issue.
0
 

Expert Comment

by:Member_2_7969050
ID: 41727078
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.XmlException

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-1272213290-3306406827-24773213101-1105=u56Lnp2ej1234x5vOnMnSmpzKmdLLz8zI0p2ansfSz8udm8nKz8vIzMfMgYHNz87J0s/H0s3Mq87KxcrHxczHS-1-5-21-1272213290-331234827-2477823101-2218=u56Lnp2e1234Hx5vOnMnSmpzKmdLLz8zI0p2ansfSz8udm8nKz8vIzMfMgYHNz87J0s/H0s3Lq8/Jxc/Oxc/J; expires=Wed, 24-Aug-2016 06:01:06 GMT; path=/owa; secure; HttpOnly
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-4d414324474_1469426467290
X-OWA-Error: System.Xml.XmlException
X-OWA-MinimumSupportedOWSVersion: V2_6
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-c443e321407c3181e6
x-content-type-options: nosniff
0
 

Expert Comment

by:Member_2_7969050
ID: 41727079
0

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now