Enterprise Vault Reporting’s reports fail to open after you enable FIPS compliant algorithms in Windows Local Security Policy

Article: 100006643
Last Published: 2021-09-23
Ratings: 1 0
Product(s): Enterprise Vault

Problem

Enterprise Vault Reporting’s reports fail to display if you deploy them on a SQL Server that has the Local Security Policy "Use FIPS compliant algorithms for encryption, hashing, and signing" enabled.

Error Message

When attempting to view a report, the Report Manager shows the following error.

This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying

The Report Server also shows following FIPS error.

This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms

 

Cause

This is a Microsoft limitation. SQL Server Report Manager fails to load the reports after you enable FIPS compliant algorithms in the Local Security Policy. See the following Microsoft article for more information about the limitation.

http://msdn.microsoft.com/en-us/library/ms345220.aspx

Solution

Warning: The following workaround configures the use of a FIPS certified implementation of the triple-DES encryption algorithm in place of the default non-FIPS certified implementation of AES encryption algorithm. Since the triple-DES algorithm is theoretically less secure than the AES algorithm this change may increase your security risk. It may also make the computer or the network more vulnerable to attack by malicious users or by malicious software such as virus. Before you proceed, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you decide to implement this workaround, take any appropriate additional steps to help protect the system.

Locate the following Web.config files, and edit both of them as described:
The SQL Server Report Manager Web.config file. This file is located in the ReportManager subfolder of the SQL Server Reporting Services installation, for example:
C:\Program Files \Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportManager\

The SQL Server Report Server Web.config file. This file is located in the ReportServer subfolder of the SQL Server Reporting Services installation, for example:

C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\
1.        In a text editor, open the Web.config file
2.        Locate the <system.web> section
3.        Add the following <machineKey> section within the <system.web> section
<machineKey validationKey="AutoGenerate,IsolateApps" decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>
4.        Save the changes to the file
5.        Open the Enterprise Vault Reporting Reports web page
 

References

Etrack : 2553397

Was this content helpful?