Forum Discussion

btrowdy's avatar
btrowdy
Level 3
10 years ago
Solved

App Error Something went wrong - OWA Webapp

We run an Enterprise Vault 10.4 server and are moving to Exchange 2013. I have registered OwaWebApp on a new Exchange 2013 user. When accessing the Enterprise Vault button on a vaulted item I get the error

 

App Error Something went wrong and we couldn't start this app. Please try again later or contact your system administrator.

 

I suspect this might be related to the URL and certificates. We currently use an internal name for the evserver as everver.domain.local and do not want to change this. However for webapp to work, we wanted to ensure SSL was enabled. I created a DNS alias fro evserver.domain.com and have registered a star cert on the evserver testing both http and https to the enterprisevault directory. No issues here.

I do notice however when I goto the URL for the Webapp i.e http://evserver.domain.com/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=mylegacydn

 I see an XML page showing the internal server name (https://evserver.domain.local) this will not match with my SSL cert. 

 

1. Does the EV server need to be accessible externally for remote users to access EV content from owa? or perhaps the CAS server accesses the evserver internally and just retrieves the content to be displayed.

2. we use evserver.domain.local internally.  Does this cause any issues accessing items? I suspect that if this indeed uses the internal name on https there will be cert errors.

The command I used to register the webapp

New-App -mailbox $Mbx.LegacyExchangeDN -Url ("https://evserver.domain.com/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" + $Mbx.LegacyExchangeDN)

 

Thanks

 

  • You probably need to specify the BaseURL parameter to match your certifcate, something like this:

    New-App -mailbox $Mbx.LegacyExchangeDN -Url ("https://evserver.domain.com/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" + $Mbx.LegacyExchangeDN + "&BaseURL=https://evserver.domain.com/EnterpriseVault)

     

    Clients will need to be able to connect to the EV server.

    Hope that helps

    Andrew

  • I tried with the baseurl and now just get Initialization failed.

     

    It's unfortunate that the clients need access to the vault server externally, this was not the case in previous OWA versions as I believe the OWA extensions just reached out to the evserver from the CAS.

     

  • Even in OWA for Exchange 2007 and 2010, they would have needed access to EV for Search and Archive Explorer, but not for opening shortcuts.

    Have you looked at the troubleshooting section for the Office Mail App in the Setting Up Exchange Server Archiving guide? That's available on the installation media, or here.

     

    Andrew