Alteryx Server Knowledge Base

Alteryx Server provides a fully scalable architecture that allows an organization to scale Alteryx to automate data analytics, tackle bigger projects, process larger datasets and put self-service data analytics into the hands of more decision makers. From scaling Worker nodes to Gallery nodes to the MongoDB persistence layer, Alteryx Server allows organizations to efficiently manage their automated and self-service data analytics needs.

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.

Procedures for backing up Built-in MongoDB

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. 

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.

After having used MongoDB logging for troubleshooting purposes, you can now safely turn it off.

One common reason why the Alteryx Service appears stuck in the 'Stopping' state is when the service is trying to stop but the AlteryxEngineCmd.exe process is running. In other words, a workflow is running. The Alteryx Service cannot be stopped when a workflow is running due to a schedule or a Gallery run.

Now, find all your Server and Gallery questions and answers in one place!  The new Gallery Admin Help Page has your Server Installation Guide, Configuration instructions, and the much-requested Administer Gallery management features - Subscriptions and Studios defined!  Manage your user permissions!  Edit user accounts! \n  

Some widely accepted best practices for backing up servers and databases

How To: Log App

Helpful Tips in Opening a Case

This is a very common error that can occur if the AlteryxService shuts down unexpectedly. Most commonly the error is caused by MongoDB not shutting down properly and the lock file does not get released. This prevents MongoDB from starting the next time you try to start the AlteryxService and returns an error message.

Steps to retrieve the version of your Alteryx Server's MongoDB instance.

One of the three database options when setting up the Alteryx Server is to connect into a User-Managed

Alteryx Service throws corrupt record error when a MongoDB backup script is in progress