Cannot log on to OWA when FIPS is enabled in an Exchange Server 2016 environment

If Federal Information Processing Standards (FIPS) is enabled in an Exchange Server 2016 environment, users cannot log on to Outlook Web Access (OWA). Instead, the user receives the following error page:


Something went wrong
We can't get that information right now. Please try again later.
X-ClientId: 9CBDD459E5D04C5A821C1A4605B2DF76
X-FEServer: Exchange
Date: date
Additionally, the following Event ID 1309 is logged on the Exchange server:
This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

This issue occurs because the instance of MD5CryptoServiceProvider is not FIPS compliant.

Cumulative update information

For Exchange Server 2016

To resolve this issue, install Cumulative Update 3 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

ID do Artigo: 3175080 - Última Revisão: 09/20/2016 15:24:00 - Revisão: 2.0

Exchange Server 2016 Enterprise Edition, Exchange Server 2016 Standard Edition

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