"Your request cannot be completed right now” error in Outlook Web App after an upgrade to Exchange Server 2013 CU 11 or later

In a Microsoft Exchange Server 2013 environment that's been upgraded to Cumulative Update 11 or later, users experience one or more of the following behaviors in Outlook Web App:
  • You receive a “Request cannot be completed right now. Please try again later” error message when you try to open, reply to, or forward items in Outlook Web App.
  • When you try to log in to Outlook Web App or select different folders, you also encounter this error.

Additionally, the following event is logged repeatedly in the Windows Application log:

Time:     7/5/2016 2:20:24 PMID:       4999Level:    ErrorSource: MSExchange CommonMachine:  MBX1.contoso.comMessage:  Watson report about to be sent for process id: 10472, with parameters: E12IIS, c-RTL-AMD64, 15.00.1178.004, w3wp#MSExchangeOWAAppPool, m.exchange.services, M.E.S.C.T.IdConverter.ConvertId, System.MissingMethodException, a16f, 15.00.1104.003.ErrorReportingEnabled: False
This issue occurs if, when a cumulative update is applied, the setup bits for any previous cumulative update exist in the Exchange installation directory’s Bin subdirectory. For example: in C:\Program Files\Microsoft\Exchange Server\V15\Bin\Setup.

When you run the Setup process in this scenario, the SharedWebConfig.config file that's located in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess (Mailbox role) or C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy (Client Access role) points to C:\Program Files\Microsoft\Exchange Server\V15\Bin\Setup. These files are not updated by the Setup process.
To resolve the issue, follow these steps to remove the files from C:\Program Files\Microsoft\Exchange Server\V15\Bin\Setup and to update the SharedWebConfig.config files to point to the correct locations:
  1. At an elevated command prompt, run the following command to stop IIS services in order to allow access to the files: iisreset /stop
  2. Move the C:\Program Files\Microsoft\Exchange Server\V15\Bin\Setup folder to another directory location outside of the Exchange installation path. For example, move it to C:\TEMP\Setup. 
  3. Make a backup copy of the SharedWebConfig.config file in both C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess and C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy in an alternative location.
  4. At an elevated command prompt, run cd %ExchangeInstallPath%\bin to change to the correct directory. Then, run the following command to rebuild the SharedWebConfig.config file in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess:
    • DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%\bin" -exchangePath "%ExchangeInstallPath%\ClientAccess" -configFile "%ExchangeInstallPath%\ClientAccess\SharedWebConfig.config"
  5. At elevated command prompt, run the following command to rebuild the SharedWebConfig.config file in C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy:
    • DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%\bin" -exchangePath "%ExchangeInstallPath%\FrontEnd\HttpProxy" -configFile "%ExchangeInstallPath%\FrontEnd\HttpProxy\SharedWebConfig.config"
  6. At an elevated command prompt, run the following command to restart IIS services: iisreset /start

ID d'article : 3191636 - Dernière mise à jour : 09/15/2016 20:51:00 - Révision : 1.0

Microsoft Exchange Server 2013 Standard, Microsoft Exchange Server 2013 Enterprise

  • kbsurveynew KB3191636
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)