Enterprise Vault Office Mail App fails with 'Initialization failed' due to EWS restrictions configured for Exchange Org
Article ID: 100049032
Updated On:
Description
Error Message
Initialization Failed.
In the browser Network Diagnostic trace for ExecuteEWSProxy gets the below response:
{"Body":null,"ErrorMessage":"The remote server returned an error: (403) Forbidden.","StatusCode":0,"StatusDescription":null,"WasProxySuccessful":false}
In the Browser Console Trace we get
MicrosoftAjax.js:5 EVOMA (ERROR) 14:55:34.474: logAndReportFailure: EWSFindAssociatedItem.onEwsRequestComplete ID[ERROR_EWS_ERRORRESULTSTATUS] Err[Failed to send a request to the Exchange Server] [Result status:failed]
MicrosoftAjax.js:5 EVOMA (ERROR) 14:55:34.475: initializationFailed(): Failed to send a request to the Exchange Server
Cause
EWS restriction configured for Exchange Org Config.
Resolution
The MailApp is not allowed to access EWS at the organization Config level due to which we get the Forbidden response..
Run the command get-OrganzationConfig | fl ews* on the exchange server and make a note of the output.
If you see the value for EWSAllowList not set to blank ensure you add the "EWSProxy/MaillApp/0cc6d075-e610-4b8a-90c6-1460e6d4d710" to it.
Add EWSProxy/MailApp/0cc6d075-e610-4b8a-90c6-1460e6d4d710 to EWSAllowList by using the command
Set-OrganizationConfig -EWSAllowList:"EWSProxy/MailApp/0cc6d075-e610-4b8a-90c6-1460e6d4d710".
Also Ensure -EWSEnabled is not set False.
Note: Append EWSProxy/MailApp/* to the existing value of the EWSAllowList in the OrganizationConfig.
Issue/Introduction
