Forum Discussion

dgoodyear's avatar
dgoodyear
Level 5
9 years ago

Tracking down Exchange 2013 OWA Office Mail App Initialization Failed

Our current environment is a single EV 10.0.4 CHF3 server.  We are running Exchange 2010 and have recently stood up our 2013 environment.  We have a handful of IT test users migrated to 2013.  Enterp...
Enterprise Vault
Information Governance
  • dgoodyear's avatar
    dgoodyear
    9 years ago

    I do have https enabled and configured on EV with the proper cert.  After coming across a good troubleshooting article for mail apps here:

    http://blogs.msdn.com/b/emeamsgdev/archive/2014/09/19/troubleshooting-exchange-2013-mail-apps-executeewsproxy-calls.aspx

    and the author's corresponding visual on various logs to check to see where the failure might be:

    http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-components-postattachments/00-10-55-92-15/steps.png

     

    I was able to trace the issue through each step of the communication process.  It turns out that we had a firewall blocking traffic from our mailbox servers back to the Exchange 2013 F5 vip on port 443. What was happening was that the Enterprise Vault mail app was communicating properly to the EV server and communication was working up through step 3, after step three, checking the Exchange CAS iis logs again, I did not see any iis requests coming back from the mailbox servers.  EV was configured correctly in this case and it turned out to be an Exchange communication issue.

    Everything seems to be working well now.

dgoodyear's avatar
dgoodyear
Level 5
9 years ago

I do have https enabled and configured on EV with the proper cert.  After coming across a good troubleshooting article for mail apps here:

http://blogs.msdn.com/b/emeamsgdev/archive/2014/09/19/troubleshooting-exchange-2013-mail-apps-executeewsproxy-calls.aspx

and the author's corresponding visual on various logs to check to see where the failure might be:

http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-components-postattachments/00-10-55-92-15/steps.png

 

I was able to trace the issue through each step of the communication process.  It turns out that we had a firewall blocking traffic from our mailbox servers back to the Exchange 2013 F5 vip on port 443. What was happening was that the Enterprise Vault mail app was communicating properly to the EV server and communication was working up through step 3, after step three, checking the Exchange CAS iis logs again, I did not see any iis requests coming back from the mailbox servers.  EV was configured correctly in this case and it turned out to be an Exchange communication issue.

Everything seems to be working well now.