Welcome to the Alteryx Knowledge Base

Common indexing issues

When attempting to rebuild the Gallery indexes on a Server, the workflow ends with a "500 Internal Server Error" - UnknownException - Unknown error:

 

Cause 1

Looking at the Gallery logs, the below FATAL error message is highlighted:

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

FIPS is enabled in the Server environment.

According to this resource:
FIPS stands for “Federal Information Processing Standards.” It’s a set of government standards that define how certain things are used in the government–for example, encryption algorithms. FIPS defines certain specific encryption methods that can be used, as well as methods for generating encryption keys. It’s published by the National Institute of Standards and Technology or NIST.

Microsoft doesn't recommend enabling FIPS unless you are mandated to by government regulations due to the issues it causes with common software packages. Also, enabling FIPS also restricts or disables the use of RS4 for encrypted communications which will conflict between our implementations of RS4 for communication between clients and the controller and internal communication between different parts of the server.
 

Cause 2

There are still records present in the lucenseFs.locks collection within the AlteryxGallery_Lucene database.

Solution A

Note: The below steps will have to be authorized or performed by your IT. Feel free to reach out to Customer Support if you have questions.
 

Option 1: Using RegEdit

Solving this issue consists in disabling FIPS on the machine that hosts Alteryx Server:

1. Open the Registry Editor

2. Locate the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy key

3. This key contains a value named "Enabled"
4. Right-click on this value and select "Modify"
5. Set the "Value data" field to 0 
6. If it was already 0, change it to 1, and vice versa.

7. Restart Alteryx Service
8. Rebuild the Gallery indexes

Once FIPS is disabled, the Server admin will need to ensure that group policies do not enforce FIPS on the machine after reboot, or at any other time.
 

Option 2: Using Local Group Policy Editor

Alternatively, the change can be done via Local Group Policy Editor.

Please note that the below steps apply do not apply if the  “Use FIPS compliant algorithms for encryption, hashing and signing” group policy is applied to the domain and you will have to work with your IT to make the required changes on the group policy for the domain.
To turn off FIPS Cryptography using the Local Policies, follow these steps:

• Press the key combination WINDOWS_KEY+R to launch the Run dialog.
• Type secpol.msc into the dialog and click OK.
• In the Local Security Policy Management Console window that opens, use the left tab to navigate to the Local Policies > Security Options. 
• Scroll down the right pane and double-click System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.
• In the Properties window, select the Disabled option and click the Apply button.
• Close the Properties window by clicking OK.
• Close the Local Security Policy Management Console.
• Reboot the server for the changes to take effect

Solution B

Remove luceneFS.locks from AlteryxGallery_Lucene DB with the following command:

db.getCollection('luceneFs.locks').remove({})

• National Institute of Standards and Technology (NIST) resource on FIPS
• Changing FIPS setting in Windows
• How to connect to MongoDB