"Something went wrong" error in Outlook Web App may show an incorrect date

When a user encounters an error in Outlook Web App, they are shown a "Something went wrong" error page. The date on this error page may be incorrect.

The following is an example error message that has an incorrect date:
Something went wrong
Sorry, we can’t get that information right now. Please try again later. If the problem continues, contact your helpdesk.
X-OWA-Error: ClientError;exMsg=Out of memory;file=https://mail.contoso.com/owa/:1
X-OWA-Version: 15.0.775.9
X-FEServer: Server1
X-BEServer: null
Date: 1/2/1601 2:17:10 PM
X-OWA-Error: SessionDataError;
X-OWA-Version: 15.0.775.11
X-FEServer: Server1
X-BEServer: Server2
Date: 1/2/1601 2:17:09 PM

The date information is calculated based on the date of the Exchange server to which the user is connected. In some scenarios (such as network connectiivy failure), the Outlook Web App client-side script is unable to connect to the server to obtain the correct date. When this occurs, a generic "1/2/1601" date is used. 
To resolve this issue, install the following cumulative update:
2961810 Cumulative Update 6 for Exchange Server 2013

Article ID: 2961715 - Last Review: 08/26/2014 16:47:00 - Revision: 3.0

  • Microsoft Exchange Server 2013 Enterprise
  • kbsurveynew kbqfe kbfix KB2961715