This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
If a Server is freezing with jobs stuck in an initializing state, there may be resource contention occurring due to the configuration of System Settings. This article provides best practice formulas to ensure the optimal settings for resource utilization.
The remote server returned an error: (401) Unauthorized.
Inner exception: The provided API Key (oauth_consumer_key) is invalid.
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
Product - Alteryx Server platform
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.
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.
Add CNAME Record in Windows DNS Server
Changing the Gallery URL on Alteryx Server
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.
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.
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
Configuring Alteryx Server for SSL: Obtaining and Installing Certificates
Platform Product: Server/Gallery/Scheduler Issues – Working with Alteryx Customer Support Engineers (CSEs) (for use by CSEs and Alteryx Customers)
To EXPEDITE the resolution of your case, please include the below information.
Server/Gallery/Scheduler- Requested Information
*** Suggestion: Copy/Paste the questions below and email to email@example.com
1. Detailed description of the Issue
2. Is this a Production Issue? What is the urgency?
3. Have there been any changes made recently? Update to Alteryx, Server, etc.?
4. Alteryx Version
5. Screenshot of Error
6. Gallery/Service/Engine Logs
7. Runtime Settings.xml
8. Check for LastStartupError.txt file (may not be there)
9. Screenshot of System Settings
10. Windows Event Logs
11. System Info – File Save - .nfo
Server/Gallery/Scheduler – Requested Information (Detailed Instructions):
1. Detailed Description of the Issue – What issues are you having? Has it worked in the past? When did the issue start? Are all users affected or just some? What are the steps to reproduce your issue? What have you tried to resolve the issue? Have you searched the Alteryx Community ?
2. Is this a Production Issue? What is the urgency? How many people is this affecting? Are you able to complete most of your work? Do you have a time frame that you need to resolve the issue?
3. Have there been any changes made recently? Update to Alteryx Designer, Server, etc.? What do you think may have caused the issue? What have you done to try to resolve the issue?
4. Alteryx Version – Our Customer Support Engineers need to know the precise version so we can replicate any issues. In Alteryx, click Help > About and provide a screenshot, or the exact version number.
5. Exact Text of Error or Screenshot of error- Click CTRL-Print-screen to capture the error and paste into your e-mail. Note: You may wish to Google the error text research the issue. The Knowledgebase is also a great place to search the error text as well! Where was the error encountered? Gallery?
6. Gallery, Service and Engine Logs are the best way for us to get to the root of the problem. We look at errors and warnings. For the Alteryx logs (Gallery, Service, and Engine), please include the logs that reflect the time of the error/crash (the logs immediately before and after the error/crash). Before sending the logs, recreate the issue, and then send the latest logs. Use Alteryx App - Server Logs the easy way! OR…
Default Paths: Gallery Logs (\ProgramData\Alteryx\Gallery\Logs) Service Logs (\ProgramData\Alteryx\Service\AlteryxServiceLog.log) *** Send several .log files. Engine Logs (\ProgramData\Alteryx\ErrorLogs)
If you have Server, and do not have logs in the pathways above, click Options >> User Settings >> System Settings, and note the paths that the logs are written to. Navigate to that location and collect the logs. If the path is not yet set, pick a path, rerun the workflow to create the error, and then send the logs.
Locating the path of your Engine logs:
Note: it’s important to note that by default Engine logs do not generate, therefore this field will be empty for most users. If a user wants to enable Engine Logging, then they will need to set a directory of their choosing in this field.
Locating the path of your Service logs:
Locating the path of your Gallery logs:
If you aren't using Server, you're probably using a Desktop Automation/ Scheduler installation that has logs located in C:\Program Data\Alteryx\Engine. However, if you have Desktop Automation/ Scheduler and do not have logs in this pathway, click Options >> User Settings >> System Settings, and note the paths that the logs are pointed to. Then locate and send the logs.
If the path is not set yet, pick a path, rerun the workflow to create the error, and then send the logs. If there is not a directory, check "Override System Settings", and enter a path for “Logging Directory." Rerun your workflow to create the error and send the new log files.
Check out this resource for more information on Alteryx logs!
7. RuntimeSettings.xml – This file gives us helpful information about your specific instance configuration and the default location will be in the directories shared above, unless you have a custom installation. You should have a RuntimeSettings.xml file, even if it is not in the default directory, and should be able to recover it for sharing with a disk search of the file name.
File Location: C:\ProgramData\Alteryx\RuntimeSettings.xml
Note: This search will find two RuntimeSettings.xml. One will be from the Program Files Directory. We do not want this file, only the one from C:\ProgramData
This file outlines the configuration of your Server and will provide Support critical information on how the node is configured. In a multi-node environment, we will need this file from each node. This file will only exist for Server installations and Desktop Automation/Scheduler installations. Regular Non-Admin Designer installations will not have this file available.
8. Check for LastStartupError.txt file
This file will be in the same path as set in the System Settings: Controller >> General >> Logging
Default is: C:\ProgramData\Alteryx\Service
May contain helpful messages to identify your issue.
9. Screenshot of System Settings – Click Control Panel >> All Control Panel Items >> System. We need your system settings to replicate issues you are having on a similar configuration.
This information in conjunction with the RuntimeSettings.xml will help Support be sure that your Server is properly configured for the amount of resources that are available.
10. Windows Event Logs (Optional)- Event logs provide historical information that can help you track down system and security problems. Provide System and Application logs in evtx format.
From the Windows Start menu, search for “event” and choose Event Viewer.
Expand the Windows Logs and right-click on ‘Application’ and select ‘Save All Events As…’ and save as *.evtx file
Right-click on ‘System’ and select ‘Save All Events As…’ and save as *.evtx file
11. System Info - Records events logged by the operating system or its components, such as the failure of a service to start at bootup. System Information shows details about your computer's hardware configuration, computer components, and software, including drivers.
System Information will provide Support with the detailed specifications of your Server that will be very helpful when troubleshooting complex issues. This will provide us with information about the Services that are running, specific information around the CPU and memory of the system, available drive space, and other information that can be very useful for identifying potential problems.
Click Start and in the Search Programs and Files Field, type msinfo32.exe. Click File >> Save and save as .nfo file.
Alteryx Server Knowledge Base Alteryx Server Backup & Recovery Part 1: Best Practices
Alteryx Server Backup & Recovery Part 2: Procedures Analytic Gallery FAQ's Alteryx Gallery Series - The Lay of the Land 101: Gallery Admin Edition
Some users can experience the below error when working with numeric data:
FormatException RequestID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
In Alteryx Designer
When publishing workflows to a Gallery:
On the Gallery
When running a workflow, it will first display the below error message:
We are unable to get the status of your workflow results at this time. You can close this view and check the Workflow Results page later.
Trying to view the Workflow's results will display the below error message:
Error Getting Job Results
Unknown error. FormatException RequestID:
Version ≥ 2018.4 to version 2019.3
Microsoft Windows Server with European regional Settings
Open the Control Panel -> Clock and Region -> Region settings on the server:
On the new window, open the Additional Settings:
Under the "Numbers" tab, verify what symbol has been set for "Digit grouping symbol":
If it is left blank or set to a space (" "), refer to the Solution at the end of the article.
The Alteryx Server expects there is a character present for the Digit Grouping Symbol, this will be fixed in a future release (DE18733).
If the Decimal Symbol is set to a period (.) :
Change the "Digit grouping symbol" from a space to a comma (,)
If the Decimal Symbol is set to a comma (,) :
Change the "Digit grouping symbol" from a space to a period (.)
Save the changes
Apply it to the system account through the below:
Control Panel -> Clock and Region -> Region settings -> Tab "Administrative" -> Copy settings -> Check “Welcome screen and system accounts” -> Ok
Restart the Alteryx Service
As always, don't hesitate to contact us over at Customer Support if you run into any trouble.
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.,
Windows Operating System
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.
FIPS is enabled on the Machine
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.
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”:
Generic failed Connection to MongoDB (Not FIPS).
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)
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.
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.
Alteryx Server 2018.1+
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.
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:
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:
If your version says 3.4.10, see Solution below.
The ASMongoDBVersions.bin file contains the wrong version.
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
Troubleshooting a failed MongoDB migration - Server 2019.3
Schedules Disabled - "Logon Failure: the User has not been Granted the Requested Logon Type at this Computer"
A change in Run As credentials or workflow credentials can lead to the user(s) losing access to his/her workflows.
When clicking on a workflow the below error appears:
Error: Logon failure: the user has not been granted the requested logon type at this computer. (1385)
Apps appear in state 'Disabled'
When trying to access apps the above error message appears
This error occurs when the Run As User credentials or the workflow credentials do not have sufficient permissions on the server. More specifically, 'Allow log on locally' or 'Log on as a batch job' group policy permission are required for the user to log onto the server. If neither is granted to user the above error appears.
Check that that Run As credentials are set correctly. Refer to Help doc page - Set Required Run As User Permissions.
Specifically, 'Allow log on locally' or 'Log on as a batch job' group policy permission are required.
How Workflow Credentials Work on a Private Gallery
Troubleshoot "Invalid Username or Password" Error - Setting Up Workflow Credentials
Troubleshooting "Entering credentials has been disabled", "Credential usage is disabled"