Symptoms

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:

Error:

:-(

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.


Cause

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.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×