cancel
Showing results for 
Search instead for 
Did you mean: 

Web App fails with "Initialization failed" after installing CU 8 for Exchange 2016

stephan_vanheld
Level 5

We recently insatlled CU 8 for our Exchange 2016. Since then, browser displays "Initialization failed" then clicking the Enterprise Vault shortcut in Outlook on the Web.

Browser console shows:

MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.654: Office.initialize() - diagnostics host name - OutlookWebApp
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.655: Office.initialize() - navigator user agent - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.656: Office.initialize() - navigator app name - Netscape
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.656: startSlowLoadTimer()
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.657: Determining EV language support for en-US
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.657: Page reload needed
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.657: getSettings()
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.658: getItemId()
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.658: EWSFindAssociatedItem.addRestriction()
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.658: EWSFindAssociatedItem.invoke()
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.658: EWSRest_EVSettings.getSoapTag()
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.658: EWSRest_DistinguishedFolderId.getSoapTag()
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:37.658: Making EWS call to find item with restriction : <t:IsEqualTo><t:FieldURI FieldURI="item:ItemClass" /><t:FieldURIOrConstant><t:Constant Value="IPM.Note.EnterpriseVault.Settings" /></t:FieldURIOrConstant></t:IsEqualTo>
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:38.407: onSlowLoadTimer()
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:38.408: showSlowLoadMessage()
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:38.750: EWSFindAssociatedItem.onEwsRequestComplete()
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:38.750: EWSFindAssociatedItem.onEwsRequestComplete() - no cancel check defined.
MicrosoftAjax.js:5 EVOMA (ERROR) 09:16:38.751: 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) 09:16:38.751: initializationFailed(): Failed to send a request to the Exchange Server
MicrosoftAjax.js:5 EVOMA (TRACE) 09:16:38.751: cancelSlowLoadTimer()
MicrosoftAjax.js:5 EVOMA (ERROR) 09:16:38.752: displayFailure()
MicrosoftAjax.js:5 EVOMA (ERROR) 09:16:38.752: displayMessage()

Fiddler trace shows this JSON response:

ErrorMessage=Failed to make a request via HttpWebRequest. Exception: Unable to read data from the transport connection: The connection was closed.

Is there anything more we can do or test, or does it just not work with CU 8?

2 REPLIES 2

haeussler
Level 4

Hello Stephan,

please refer the following compatibility artciel:

https://www.veritas.com/content/support/en_US/doc/128058600-128865835-0/v128056146-128865835

CU8 is in Pending state for Exchange 2016. You can test the behaviour with CU7. This is supported.

 

LG

Lucas

You can test the behaviour with CU7. This is supported

Supported by Veritas probably, but not by Microsoft anymore. Thus this is not really an acceptable solution. (We rather go without EV OWA integration for a while than use an outdated and unsupported Exchange version.)