Forum Discussion

Richard_J_Cunni's avatar
13 years ago

Exchange 2010 OWA - Archive Explorer\Search Archive links not working

 

 

I have EV reverse proxied through an apache RP, opening vaulted items works fine both internally and externally. But the Archive Explorer\Search Archives buttons aren't working in OWA, it tries to point to the internal URL, even though in the policies in EV the external app is set to the external app.  
 
But if I try to access the below, these are the URLs it tries to point to, searcho2k doesn’t work at all, but AE works internally.
 
res://ieframe.dll/dnserror.htm#http://ukevsrv.uk.companyname.org/EnterpriseVault/ArchiveExplorerUI.asp?mbx=Richard.Cunningham@companyname.co.uk&server=UKBNEX01&OWA2007=1&Owa2007Url=https%3a%2f%2fwebmail.companyname.co.uk%2fowa%2f - works int, doesn't ext. AE
 
http://ukevsrv.uk.companyname.org/EnterpriseVault/Searcho2k.asp?vaultid=1FBAE6FC652319F43AFD4BD4046DD2C151110000ukevsrv&mbx=Richard.Cunningham@companyname.co.uk&server=UKBNEX01&usebrowserview=True&OWA2007=1&OWA2007Url=https%3a%2f%2fwebmail.companyname.co.uk%2fowa%2f - doesn't work int\ext, searcho2k
 
Any ideas on how I’d change these?
 
  • Glad the issue is resolved.

    Sometimes it is hard to understand what exactly to enter in the command boxes/fields.

  • So if users (internal or external) get to OWA using "https://webmail.company.co.uk/owa", then they will use "https://webmail.company.co.uk/enterprisevault" to get to search/archive explorer.

    In other words, your internal users are probably now getting to EV through the Apache RP too.

  • I suspect, the internal users, when they click on Serach or Archive Explorer they will be using the external webappurl, unless you have reconfigured your DNS internally for internal OWA, internal users will have opposite problem of external users now.