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!

Error: "This workflow requires a higher version of Alteryx" when saving a workflow to the Gallery. Is it possible to publish workflows from a newer version of Designer to an older version of Server?
View full article
Error resolving python plugin for various Connectors when running on the Server/Gallery.
View full article
The final step in an Insight's journey is it's publication to a company's private Gallery. After publication, an insight can be shared with anyone who has access to the Gallery it is hosted on. This article provides detailed steps on how to publish an insight   to   a Gallery, and how to share the insight with other users on the Gallery.  
View full article
Issue    When publishing a workflow to Gallery with user credentials and you run into the following: Entering credentials has been disabled   When configuring a new Gallery Data Connection the below error comes up when attempting to test or save the connection:   Credential usage is disabled as a result of encryption configuration. Please contact your server administrator.     Environment   Alteryx Designer Alteryx Server   Diagnosis    You can verify this issue in the AlteryxService logs after a service restart. During the startup you will see a message like the following: ERROR,8912,AlteryxService,,,,,,,,"AlteryxService_InitLocalEncryptedStorage_Error: Error importing keys to Microsoft\Crypto\RSA\MachineKeys\ directory in ProgramData: Access is denied. (5)"   Cause   The Alteryx Service account has insufficient permissions to the server's machine key directory (%ProgramData%\Microsoft\Crypto\RSA\MachineKeys) or specifically the Alteryx Machine Key which is used to encrypt/decrypt user credentials and Gallery data connections.    Solution   Check your Service Log On As Account. The user set as the Log On As user (the default is Local System account) will need to have specific permissions.   Run services.msc (CTRL+R, enter services.msc, and click OK) Locate the Alteryx Service and check the Log On As account Per the server help documentation, ensure the Service Account has Full Control over  %ProgramData%\Microsoft\Crypto\RSA\MachineKeys** **If giving permissions to the full directory is not possible due to security reasons you can give it to just the Alteryx Machine key which starts with "3312". Also allowing Full Control over this machine key may fix the issue of the directory access does not. After granting permissions to the service account, restart the Alteryx Service  
View full article
When you publish an application to the Alteryx Gallery it packages this workflow up into a yxzp and creates folders called 'Externals'. In these folders it might contain macros within your workflow or more commonly input and output file locations.    The Designer does this is to ensure your application has the read and write capabilities when published to the server. However, you may be confident that the server has access to a mapped drive or database. Therefore, you can do the following to keep your macros, input & output file paths absolute (C:\Users\etc.) rather than relative (.\etc):   1. Within the Alteryx Designer go to File>>Save As>>Gallery   2. Before Saving go to 'Workflow Options' >>> 'Manage workflow assets'   3. Make sure all macros, input and output files you want to keep absolute are unchecked    4. When you publish to the Alteryx Gallery now these macros, input and output file will keep the same path and not kept in external folders.    Consideration: When uploading to the Gallery the location of the macros needs to be accessible from the server. Hence, it is best practice to have these on a mapped drive or on the server itself so the workflow does not error.    Best,   Jordan Barker Solutions Consultant  
View full article
Question Is it possible to allow users to publish an app/workflow to the Private Gallery but not allow users to actually run the app/workflow? Answer I received this question from a client that needs to do careful QA on apps before they can be pushed to the Production server.    This is possible through a manual process currently. When a workflow is published to the private gallery, the user who published it can edit the workflow settings to prevent the workflow from being able to run in the Gallery manually. This method requires the user to change the workflow settings for every workflow published that they do not want to be able to run.   The steps for this process are shown below.   1) Log in to your Private Gallery after publishing your workflow/app 2) Click on the Private Studio icon on the left side of the screen 3) Select the workflow/app you wish to change the settings for 4) Click the link for Workflow Settings 5) Deselect the option showing "This workflow may be run in the Gallery"     Note: Screen shots taken from 10.1.7.
View full article