Alteryx Server Knowledge Base

Definitive answers from Server experts.

'Tis the season to be spooky! Read our new blog, How Spooky is Your City? Mapping and Predicting Scary Stuff. In it, @SusanCS provides a fun glimpse into using data to figure out the creepy quotient of where you live! And don't forget to check out our Digital Costume Thread to get yourself in the mood for a candy binge!

This error occurs when the password of the Service Account AlteryxService is running under expires.
View full article
Properly reading Alteryx Server logs will significantly help in the resolution of Alteryx Server issues. This article will help you understand and focus your search within the logs.
View full article
Alteryx Service throws corrupt record error when a MongoDB backup script is in progress
View full article
After setting up SAML in Azure, and the client attempts to login to gallery, receive Access Denied - Key issue within AAS.logs
View full article
This KB will help understand why "Verify IDP" doesn't work when setting up SAML authentication
View full article
After installing Alteryx Server as either a full Server or a Worker node, it doesn't start up and no AlteryxService exists in the service list.
View full article
Error: "failed: CURLerror (curl_easy_perform() failed) - code=60 msg='SSL peer certificate or SSH remote key was not OK'" when running a workflow.
View full article
Running a workflow on Alteryx Server or Gallery never finishes and no errors are thrown.
View full article
Error: "[SQLState 08S01] fe_sendauth: no password supplied" when using Amazon Redshift and publishing to the Gallery.
View full article
Error: "SQL1031N The database directory cannot be found on the indicated file system. SQLSTATE=58031" when connecting to DB2 z/OS
View full article
Error resolving python plugin for various Connectors when running on the Server/Gallery.
View full article
Upgrading to 2020.1 An unknown error occurred during authentication with your Windows credentials
View full article
When saving a workflow to the gallery, the following error occurs: Tool ## - Error finding connection "connection_name".
View full article
Users are unable to get view the Collections section of Gallery. Attempting to load Collections for both User and Admin Gallery sites fails / stalls.
View full article
Alteryx provides sample clients that utilize the API in both C# and Javascript. The examples provided utilize the Subscription API and endpoints located on the Subscription tab in the top left of the Interactive Documentation. ERROR: The remote server returned an error: (401) Unauthorized. Inner exception: The provided API Key (oauth_consumer_key) is invalid.
View full article
How to Troubleshoot DNS Issues   Changing the gallery URL can often lead to "website not found" error in a windows authenticated/domain environment if a CNAME record has not been created in DNS (Domain Name Space). CName records (also known as Canonical Name) are typically used to map any given name against the host providing the service, in this case the Alteryx server hosting gallery. When gallery URL is changed in System Settings without adding the CNAME record the following errors can appear.                           Other symptoms include: Gallery website not loading and in a constant loading state. Unable to connect or upload workflows to the gallery server in designer  To check this, Open Designer>>  Click on File, Save As, Add Gallery                     Enter the gallery URL and click on Connect. "Could not connect to server, please try again" is another indication the gallery is not valid                   Environment   Product - Alteryx Server platform   Diagnosis   You can take the following steps to confirm its a DNS related issue. For other gallery related issues please reference the following article: Gallery Service failed to start in a timely fashion   Is the URL resolvable? To check this Open Command Prompt Type "nslookup" followed by the URL without http and gallery. (Example: if the Url is http://mygallery123.com/gallery  then the cmd is "nslookup mygallery123.com").  If the CNAME record does not exist in DNS, following results will shown     Accessing gallery using the IP address of the gallery server. Open the web browser Enter the URL replacing the CNAME with the Server IP address hosting the gallery (Example: if the URL is http://mygallery123.com/gallery, replace with http://192.168.9.2/gallery) If the gallery successfully loads then this is another indication of a DNS issue.   The following external link shows how to find the IP Address of the Alteryx Server. Note: you must run the cmd from the server - IP address in Windows 10 from cmd (Command Prompt)     Please check additional resources section for gallery URL related issues. Solution   DNS entries are typically managed by the IT department. Please consult with your internal IT to complete this process. This solution covers the windows server platform. Open DNS Manager and select the forward lookup zone for your domain.                            Right Click on the Zone then select New Alias (CNAME)                               On the next window Fill in the Alias Name field with the name you want to use.  For example mygallery123 Fill in the FQDN for the target host field with the target host or browse to select from the available records. The target host is the Server hosting gallery. You can choose to tick Delete this record when it becomes stale option. When enabled, this option will convert your CNAME record into a dynamic record. Otherwise it is static by default. You can also tick the Allow any authenticated user to update all DNS records with the same name to allow automatic update of this CNAME record if the information on the target host record is changing overtime, such as when the server is using DHCP.                                5. Click OK complete the entry    Note: The new gallery URL may not work immediately as your machine caches previous DNS entries that have not expired yet. You can clear this manually by typing "ipconfig /flushdns"  in command prompt on your local machine.      Additional Resources   Add CNAME Record in Windows DNS Server Changing the Gallery URL on Alteryx Server
View full article
Issue   When binding a certificate to an SSL port as detailed in this article, you may run into one of these 2 common errors:   The parameter is incorrect.     SSL Certificate Add Failed, Error: 1312 A specified logon session does not exist. It may have already been terminated.     Environment   Alteryx Server   Cause   If you are getting the message that "The parameter is incorrect," the certhash likely contains hidden characters that were inadvertently copied from the certificate's thumbprint. In the above screenshot, note the '?' at the beginning of the certhash which is causing the issue.   If you are getting Error Code 1312, the certificate you are attempting to bind likely does not contain the private key.   Diagnosis   If you are getting Error Code 1312, you can determine if the certificate you imported contains the private key by looking at its icon in MMC.    Icon only shows a certificate. The private key needs to be added.     Icon includes a key. While your icon may be slightly different, the presence of a key means the private key is attached.     Solution A (Incorrect Parameter)   Copy the command into notepad Save As ANSI Re-open the file Remove hidden characters Re-try the command   Solution B (Error 1312)   Create a .pfx file with your certificate and key file using the following command (replace pfx, key, and crt filenames as appropriate): openssl.exe pkcs12 -export -out ServerName.pfx -inkey ServerName.key -in ServerName.crt Remove the previously imported certificate from MMC Follow the instructions in this article beginning with the "Installing the Certificate" section   Additional Resources   Configuring Alteryx Server for SSL: Obtaining and Installing Certificates
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
Issue: Error '"You are attempting to upgrade from an unsupported version" when upgrading to 2019.3'   During the upgrade of Alteryx Server to 2019.3, you may encounter the following error once you attempt the migration of the Mongo database:   You are attempting to upgrade from an unsupported version. Upgrade to Alteryx Server version 2018.1 or later to attempt to upgrade to your desired version, or contact Alteryx Customer Support for assistance. Environment   Alteryx Server 2018.1+ Embedded MongoDB   Diagnosis   If you are running a version pre 2018.1, please upgrade to version 2018.1+ before attempting to upgrade to 2019.3. Do not continue further in this article.   If you are in fact running version 2018.1 or newer, confirm that your database is version 3.4.10 with the following steps:   Check which storage engine you are running:   The first step is to identify which storage engine you are using. You can easily identify which storage engine is being used by reviewing the file system:   Open the Alteryx System Settings Navigate to the Controller > Persistence page Copy the Data Folder path. Open Windows Explorer (File Browser) Paste the Data Folder path copied in Step 3 in the Address Bar of Windows Explorer If you see a series of "NS File" and "0 File" file types, as shown below, MongoDB is running using the MMAP storage engine. If you see a series of "WT File" file types and a file named "WiredTiger", as shown below, MongoDB is running using the wiredTiger storage engine.   MMAP     wiredTiger     Start the Mongo daemon:   1. Open command prompt as an Administrator 2. Change directories to the location of the Alteryx bin folder. The default location is "C:\Program Files\Alteryx\bin" cd "C:\Program Files\Alteryx\bin\" 3. If you are using the wiredTiger storage engine, run the following command, replacing the dbpath location with your Data Folder path: mongod3_4.exe --dbpath "C:\ProgramData\Alteryx\Service\Persistence\MongoDB_34" --port 27018 3b. If you are using the MMAP storage engine, run the following command, replacing the dbpath location with your Data Folder path: mongod3_4.exe --dbpath "C:\ProgramData\Alteryx\Service\Persistence\MongoDB_34" --port 27018 --storageEngine mmapv1 4. You should see a message that says 'waiting for connections on port 27018'. Leave this window open and proceed with the next steps.   Connect to the Mongo shell:   1. Open another command prompt as an Administrator 2. Change directories to the location of the Alteryx bin folder. cd "C:\Program Files\Alteryx\bin\" 3. Get the MongoDB password by running the following:  alteryxservice getemongopassword Copy the Non-Admin password.   4. Run the following to connect to the Mongo shell: - Enter the password from above after -p mongo3_4 -u user -p YOUR_PASSWORD --host localhost:27018 AlteryxService 5. Run the following command to retrieve the version: db.version() If your version says 3.4.10, see Solution below.   Cause   The ASMongoDBVersions.bin file contains the wrong version.   Solution   1. Confirm the AlteryxService is stopped 2. Navigate to the Data Folder path in Windows File Explorer. Locate the ASMongoDBVersions.bin file 3. Replace the content of the file with just the following, and Save: 3.4.10 Example of a corrected ASMongoDBVersions.bin file 3. Re-run the MongoDBUpgradeTo30.exe found in the Alteryx bin folder in the installation directory 4. You should now be presented with the following screen. Continue through the prompts to migrate the database. 5. If you run into issues with the migration, please see the article under Additional Resources below, or contact Alteryx Support     Additional Resources   Troubleshooting a failed MongoDB migration - Server 2019.3
View full article