cancel
Showing results for 
Search instead for 
Did you mean: 

Problem accessing Archive Explorer via OWA 2013

stullier
Level 4

We are beginning a deployment of Exchange 2013 in our environment.  We have configured our EV servers appropriately, and so far, all actions work as expected, except for Archive Explorer via OWA 2013.

 

When we click the Archive Explorer action, a new page appears with two frames, but a pop-up then appears stating  "The XML returned for this tree is not as expected"

If we copy the URL in the address bar into a new tab, the Archive Explorer displays as expected.

Search and View functionality from OWA all work fine.

Here are the system details:

Exchange 2013 SP1 on Windows Server 2012 R2

Enterprise Vault 10.0.4 CHF2 on Windows Server 2012 R2

 

The behaviour is the same both inside and outside the firewall.  

Look forward to any suggestions.

6 REPLIES 6

AndrewB
Moderator
Moderator
Partner    VIP    Accredited

have you seen this technote?

Archive Explorer generates error: XML returned for tree view is not as expected (500)

Article:TECH74846  |  Created: 2009-01-24  |  Updated: 2014-09-17  |  Article URL http://www.symantec.com/docs/TECH74846

stullier
Level 4

Hi Andrew,

Yes, we looked through that article and everything checks out.

We have opened a case with tech support - will let everyone know what we find.

 

 

stullier
Level 4

One of my coworkers was able to get the Archive Explorer window to appear correctly by pressing F12 in IE 10 and changing to IE10 Compatability Mode using a Document Mode setting of 9.

Going to pass this on to tech support to see what they can divulge from this.

stullier
Level 4

A debugging session revealed that the XmlLoader.js file from https://(servername)/EnterpriseVault/V10.0.4.1189/en/script/XmlLoader.js is throwing the following error:

Line 67 character 1: String Expected

AndrewB
Moderator
Moderator
Partner    VIP    Accredited

sounds right. this is documented in the EV compatibility guide.

stullier
Level 4

Here is the odd thing - we have Compatability Mode turned on.  The problem is still occuring.