Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 818
  • Last Modified:

Exchange 2013 - OWA People & Tasks Not Loading

We're currently running Exchange 2007 and 2013 in coexistence as we prepare to transition fully to 2013.  We have loaded a couple of test users into 2013 and all seems to work well other than one small issue with OWA.  We can log in with their accounts and access mail and calendars, but when we click on "People" or "Tasks", the main windows loops "Loading" indefinitely.  Does anybody have a thought as to how to resolve this?  Thanks in advance!
0
pcamis
Asked:
pcamis
  • 7
  • 4
2 Solutions
 
Jian An LimCommented:
have your autodiscover been cut-over fully or you still have it configured half way?

and is this OWA related or Outlook related?

can you also run the test-owaconnectivity ?
0
 
pcamisAuthor Commented:
Thanks limjianan for the response.  Autodiscover is in fact not fully cut over - autodiscover.external.com still points to the 2007 server.  We have also have mail.external.com pointing to the 2013 server and legacy.external.com pointing to 2007.

This is an OWA issue (when connected to mail.external.com) only.  Outlook is functioning correctly when connected internally.  Have not tested Outlook from outside our network.

From what I found, test-owaconnectivity was depreciated in 2013 in favor of test-webservicesconnectivity.  Results of that test are:

[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>test-webservicesconnectivity -clientaccessserver 2013

Source                              ServiceEndpoint                     Scenario                       Result  Latency
                                                                                                                  (MS)
------                              ---------------                     --------                       ------  -------
2013.internal.com                       2013.internal.com                       Autodiscover: SOAP Provider    Failure     100
2013.internal.com                       2013.internal.com                       EWS: GetFolder                 Failure       1


[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>test-webservicesconnectivity -clientaccessserver 2007

Source                              ServiceEndpoint                     Scenario                       Result  Latency
                                                                                                                  (MS)
------                              ---------------                     --------                       ------  -------
2013.internal.com                       2007.internal.com                      Autodiscover: SOAP Provider    Failure       6
2013.internal.com                       2007.internal.com                      EWS: GetFolder                 Failure       1


[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>test-webservicesconnectivity

Source                              ServiceEndpoint                     Scenario                       Result  Latency
                                                                                                                  (MS)
------                              ---------------                     --------                       ------  -------
2013.internal.com                       mail.external.com                  Autodiscover: SOAP Provider    Success     145
2013.internal.com                       mail.external.com                  EWS: GetFolder                 Success     429

Open in new window


As you can see, I get failures when I run the test against a specific server, but if run without any flags, it succeeds.  That help?  Is this just a normal behavior until autodiscover is fully cut over?
0
 
Jian An LimCommented:
i think the service point name is different on 2007 and 2013, so i am pretty sure your OWA 2013 has some name fault.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
pcamisAuthor Commented:
Thanks again limjianan - have been researching through the course of the day and am not sure I'm finding answers to your suggested issue.  Is it a matter of URL naming?  If so, I've followed essentially this convention:

http://msexchangeguru.com/2013/12/31/e20132007-urlsauth/

If otherwise, could you provide a link or recommendation on what exactly to check?  Very much appreciate your help!
0
 
Jian An LimCommented:
hi, just have a tought about your issue

you have a migrated user (from ex2007) in exchange 2013 browsing exchange 2013 OWA.
in this case, autodiscover don't come in.


Can you create to create a fresh user on exchange 2013 (without the migration) and confirm whether exchange 2013 OWa still appears the same?

also, can you also check you can access to the OWA/ECP/EWS side of it?

I will also start to jack up the loglevel to capture more data.

http://www.projectleadership.net/blogs_details.php?id=3090
0
 
pcamisAuthor Commented:
Sorry for the delay - was out of the office at the end of last week.

I have also tested with a new user created on the 2013 server with the same results.

For testing OWA/ECP/EWS, I ran tests with the Microsoft Remote Connectivity Analyzer.  Microsoft Exchange Web Services Connectivity Tests, Microsoft Office Outlook Connectivity Tests all come back clean.  I do get an error when testing Exchange Active Sync:

      
An ActiveSync session is being attempted with the server.
 	Errors were encountered while testing the Exchange ActiveSync session.
 	
	Additional Details
 	
	Test Steps
 	
	Attempting to send the OPTIONS command to the server.
 	Testing of the OPTIONS command failed. For more information, see Additional Details.
 	
	Additional Details
 	
A Web exception occurred because an HTTP 451 - 451 response was received from Unknown.
HTTP Response Headers:
Transfer-Encoding: chunked
X-MS-Location: https://mail.external.com/Microsoft-Server-ActiveSync
Cache-Control: private
Content-Type: text/html
Date: Mon, 29 Sep 2014 17:29:44 GMT
Server: Microsoft-IIS/7.0
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
Elapsed Time: 196 ms. 

Open in new window


Does that answer your question about access to other services?

Lastly, do you have a suggestion on what logs to elevate logging levels on?

Thanks again very much for your help!
0
 
pcamisAuthor Commented:
To add to the mystery, or perhaps help somebody figure out a solution, some more oddities with our OWA that I've since discovered...

Users can't enter text into the body of a message - there seems to be a text field (the cursor switches to the text icon) but I can't click into it.

Certain options within the settings dropdown don't do anything.  If I click on Display Settings, Offline Settings, or Change Theme, nothing happens.  Change Password and Options however work properly.

Finally, I've enabled the option to switch to OWA Light mode at login, but even with that box checked, Premium mode always loads.

For reference, we're running Exchange 2013 CU6 on a Server 2012 R2 VM.  I've confirmed this behavior in Windows 7 x64 with IE 11 (regular and compatibility mode), Chrome, and Firefox browsers.
0
 
pcamisAuthor Commented:
Making some progress via help from another source.  Discovered that our OWA version found in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa doesn't match the version found when running:

Get-ExchangeServer -Identity $env:ComputerName | fl Name, AdminDisplayVersion

(For reference, 15.0.995.28 versus 15.0.995.29 respectively)

If anybody can suggest how to sync the versions, I'd hopefully be in good shape.
0
 
Jian An LimCommented:
http://social.technet.microsoft.com/wiki/contents/articles/15776.exchange-server-2013-and-cumulative-updates-cus-build-numbers-en-us.aspx

according to the above website, there is no 15.0.995.28 so that could be a bit concern.

if you install CU6 on top of your current build, maybe uninstall via program features and install again may help.
0
 
pcamisAuthor Commented:
Solved!  Part of the trouble was that I was looking at the version in the wrong place... I had been looking here:

C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\15.0.995.28

When I should have been looking here:

C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem\15.0.995.29

By copying the contents of the latter folder into the 15.0.995.31 folder found in the same location, then restarting the WWW service, OWA now is working like a charm.  Found this last bit of info here:

https://social.technet.microsoft.com/Forums/en-US/386ce3aa-dba8-49be-858a-e8e20b70b50b/exchange-2013-cu6-coexistence-with-exchange-2007-ru13-activesync-dont-work-http-error-500?forum=exchangesvrdeploy

Thanks again limjianan - REALLY appreciate your assistance!
0
 
pcamisAuthor Commented:
Found information on another site, thanks to limjianan's comment about the non-existent version.  See link in response.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 7
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now