Initialization Failed with Office Mail App (OMA)

book

Article ID: 100032824

calendar_today

Updated On:

Description

Error Message

The end user will receive an error message initialization failed, when attempting to access the Office Mail App. 

initialization failed

A Wireshark trace performed on the end users workstation while generating the initialization failed error will display the error message "The underlying connection was closed. An unexpected error occurred on a receive."

Underlying
Note: To locate the error, search for ExecuteEwsProxy in the Wireshark trace.

Cause

This issue has been seen when the Client Access Server (CAS) that receives the ExecuteEwsProxy call can not properly proxy the request to the appropriate Mailbox server.
Note: This issue can be seen even if the Client Access Server has the Mailbox Server role as well. DNS issues can be the cause of the issue, however it has also been seen that Hosts file entries on the exchange servers causes this behavior. In some instances, Hosts file entries that resolve the Client Access Server to an incorrect name/ IP Address (.i.e resolving the CAS server to a load balancer) will cause this issue. 

 

Resolution

  • Ensure that all DNS entries are correct regarding the exchange servers in the environment.
  • Remove any Hosts file entries that resolve the exchange servers to a IP Address/Name that is not correct. 



Issue/Introduction

Launching Enterprise Vault Office Mail App (OMA) within Outlook Web Access (OWA) fails with an initialization failed error message.
Powered by Wolken Software