ALTERYX INSPIRE | Join us this May for for a multi-day virtual analytics + data science experience like no other! Register Now

Alteryx Server Knowledge Base

Definitive answers from Server experts.
Steps to retrieve the version of your Alteryx Server's MongoDB instance.
View full article
One of the three database options when setting up the Alteryx Server is to connect into a User-Managed MongoDB instance. Why would you want to set up your own implementation of MongoDB? The main benefits are to take advantage of the features of MongoDB that are not included with our embedded instance.
View full article
How To: Server Cases Attach Logs
View full article
When migrating a MongoDB to a new machine all the relevant steps in https://help.alteryx.com/20201/server/server-host-recovery-guide (use document for your Server version) should be followed. Skipping steps can cause issue occurring later.
View full article
How to connect to Alteryx Server MongoDB using the command line
View full article
If your mongo database seems to take up a lot of disk space, you're not alone. You do need to allocate sufficient space for it. But you can take some steps to compact it as well. Read on for more information on how to proceed.
View full article
This error typically occurs when using an unsupported MongoDB version for instance MongoDB 4.2+.or using a Server Usage Report version not compatible with the Server version.
View full article
One of the three database options when setting up the Alteryx Server is to connect into a User-Managed
View full article
This KB outlines how to enable MongoDB logs for troubleshooting purposes
View full article
After having used MongoDB logging for troubleshooting purposes, you can now safely turn it off.
View full article
Alteryx Service throws corrupt record error when a MongoDB backup script is in progress
View full article
There are occasions where it is necessary to identify the ID of a Workflow or Schedule. These are easy to find in the URL.
View full article
How to determine which User deleted a Gallery application
View full article
This KB gives you fundamental understanding on how to extract a list of users and their permissions on the Gallery. Only relevant for versions 2020.1+ with Windows Authentication.
View full article
This KB provides you with steps on connecting to a User-Managed MongoDB using Robo 3T
View full article
Alteryx Service Fails to Start when Mongo Fails with Error - “Input string was not in a correct format”    When trying to start the Alteryx Service, the following error can be seen in the Alteryx Service Logs:   FATAL,1,,RegisterClasses,,,,Axx-xxxxx100,,,,,,Input string was not in a correct format.,   Environment   Alteryx Server Windows Operating System   Diagnosis   This error message is coming directly from MongoDB and while very generic, it is telling us that the driver is unable to handle the data that is being sent to MongoDB. The Alteryx Service will fail to start and you will most likely get some sort of popup error when trying to start the service from the Windows Services menu.   Is FIPS enabled on your machine? If so, See Solution A.   Are you in a multi-node environment? If you are unable to start the Alteryx Service on a node that is not the Controller, see Solution B.   Cause A   FIPS is enabled on the Machine   Solution A   This error occurs because the encryption Alteryx Server uses for inter-service communication won't happen if FIPS is enabled because .NET will block the requests.   Per this article : “FIPS Compliance Encryption Issues In the .NET framework, three different versions of the SHA256 hashing algorithm, each having different security levels and speed are available. The fastest one among them has not yet been submitted for validation. However, it is believed that it is as secure. Enabling FIPS mode in systems with Microsoft OS will break the .NET applications as they probably use latest cryptography algorithms that are more efficient. And, if the .NET applications must necessarily work then a slower, much less efficient cryptography algorithm must be used.”   The Alteryx Gallery uses .NET completely for communication with MongoDB, there is not another option for communication.   Resolutions\Workarounds: There is currently no workaround to get the Alteryx Service to start with FIPS enabled. FIPS must be disabled completely on the server machine to get the Alteryx Gallery to communicate with Mongo correctly and get the service running. The impacted policy is named System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.   To get to this setting:   1. Open the Local Security Policy window from the Windows Start menu 2. Navigate to Local Policies > Security Options 3. Select the correct policy   Make sure that group policy does not enforce FIPS after reboot. To verify that FIPS has been disabled, make sure that the “Enabled” registry key located here HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy is set to “0”:     Cause B   Generic failed Connection to MongoDB (Not FIPS).   Solution B   The error states that for whatever reason, MongoDB is not able to understand the information that is being sent. A failed connection to MongoDB can also cause this error, though it can be difficult to pinpoint the root cause. There are a few things that you will want to check to see if they are causing the issue:   1. If you have a multi-node environment and are configuring the Gallery, confirm the following in the Alteryx System Settings under Gallery > Persistence. 1. Confirm the password is correct. This password should be the user (not-admin) password from the System Settings on the Controller. 2. Confirm you have the port appended to the hostname (default port for embedded MongoDB is 27018) hostname:port   2. Enable Mongo logging and see if MongoDB gives more details on why the error is occurring  3. Test connecting to MongoDB through another source (such as Robo 3t) and see if this gives more detail on why the error is occurring.          
View full article
If you are upgrading your Alteryx Server from an older version to 2018.1 or greater, your MongoDB will be migrated from Mongo 3.0 to Mongo 3.4 as part of the process. This article details how to troubleshoot a potentially failed migration. 
View full article