EVBAAdmin web page fails to open correctly after enabling FIPS compliant algorithms

Problem

The EVBAAdmin web page fails to open correctly on a Compliance Accelerator (CA) or Discovery Accelerator (DA) server that has the Local Security Policy Use FIPS compliant algorithms for encryption, hashing, and signing enabled.

Error Message

When the EVBAAdmin web page is loaded only a single gray line is displayed.

Cause

This is a known Microsoft limitation. The original Microsoft article that documented this issue is no longer available: https://support.microsoft.com/en-gb/help/911722/you-may-receive-an-error-message-when-you-access-asp-net-web-pages-tha. An unofficial copy may be found at https://mskb.pkisolutions.com/kb/911722. Note - Please read the notice and disclaimer at the top of this website, as it is an unofficial Microsoft Knowledge Base archive for deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation.

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 EVBAAdmin Web.config file, and edit as described. This file is located in the AcceleratorAdminWeb subfolder of the Accelerator installation, for example:
C:\Program Files (x86)\Enterprise Vault Business Accelerator\AcceleratorAdminWeb\
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. Re-launch the EVBAAdmin web page