OWA Exchange 2013 SP1 Security Update KB3011140 December 2014

After performing this update on our server, I noticed now users can no longer recover items from deleted items in OWA. The page always errors out now.

The KB installed was KB3011140

:-(
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=Sys.ArgumentException: Value does not fall within the expected range.Parameter name: Unknown type _d.$Vq was requested;file=$7CD@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.1.mouse.js:1:1170608_t.PopoutStartupViewModelFactory.prototype.$E/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.1.mouse.js:1:1171022_a.$Z0.prototype.$5V3/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:294125_a.$2r.$5e5@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:601482_a.$2r.$iS@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:600669_a.$Sd.$9lW@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:369272$1mX@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27237$4pt@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27789_js.$J.prototype.$6Kk@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:32733Function.createDelegate/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/preboot.js:34:39109_a.$2r.$5e5@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:601482_a.$2r.$iS@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:600669_a.$Sd.$9lW@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:369272$1mX@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27237$2gl/s@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:28216:1170608
X-OWA-Version: 15.0.847.34
X-FEServer: SERVERNAME
X-BEServer: null
Date: 1/2/1601 3:22:42 PM




  • Edited by Afterlife4u Wednesday, December 31, 2014 4:24 PM updated title
December 31st, 2014 6:55pm

Hi,

From the above description, "Something went wrong" error shows an incorrect date. 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 connectivity 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. In order to resolve this issue, you need to install the Cumulative Update 6 for Exchange Server 2013.

For more information, here is a KB for your reference.

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

https://support.microsoft.com/kb/2961715?wa=wsignin1.0

Hope this can be helpful to you.

Best regards,

Free Windows Admin Tool Kit Click here and download it now
January 1st, 2015 11:20am

That update is only for NON-SP1 exchange server 2013?

The server already has SP1 for exchange server 2013 installed, as I previously stated this only happened when I installed that December 2014 security update for SP1 exchange server 2013. According to your article (CU6 Exchange 2013) SP1 should already have the time fix in it. So I'm not sure why the issue is still happening.

  • Edited by Afterlife4u Friday, January 02, 2015 2:38 PM
January 2nd, 2015 5:30pm

Any suggestions, other than uninstalling the KB?
Free Windows Admin Tool Kit Click here and download it now
January 5th, 2015 5:02pm

Same problem, any hints how to solve this ?
January 6th, 2015 12:15pm

I had the same problem on my DAG members running Exchange 2013 SP1 and on 2 CAS running Exchange Server CU6

This KB applies to both versions

It was solved by upgrading all four servers to CU7
  • Edited by Cedric Ch Monday, January 26, 2015 9:25 AM
Free Windows Admin Tool Kit Click here and download it now
January 14th, 2015 6:19pm

Solved by installing CU7 :)
February 16th, 2015 4:15am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics