Version: 7.3

After updating Exchange 2013, the EWS connection might not work in contentACCESS

Introduction

This page describes a known issue affecting the EWS (Exchange Web Services) connection in contentACCESS after updating an Exchange 2013 server. It explains the cause of the problem and provides the steps required to restore the EWS connection.

Problem

After updating Exchange 2013 to CU15 (and possibly earlier cumulative updates as well), the EWS connection might stop working in contentACCESS.

Solution

After updating the Exchange Server, test the EWS connection again on each Email archive.

If you receive the following error:

(413) Request Entity Too Large

then the EWS configuration must be updated on each CAS server:

Back up the following file:

C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\ews\web.config

Replace the uploadReadAheadSize value of 0 with 1048576 (bytes):
```
serverRuntime uploadReadAheadSize="1048576"
```

Introduction​

Problem​

Solution​

Introduction

Problem

Solution