Showing results for 
Search instead for 
Did you mean: 

Alteryx Knowledge Base

Definitive answers from Designer experts.
 You are using an unsupported browser for translation. Please switch to another browser.

This article is an extension to the community article " Scheduling as a copy in the Scheduler DB vs On Disk ", and is specifically aimed for Designer + Desktop Automation installations only.
View full article
When your Python libraries don't work the way they should in Python tool, restoring the tool to it's original state could be the solution. This article walks through how to restore Python libraries and the virtual environment associated with the Python tool.
View full article
Symptoms   “Unhandled Exception occurred” error is thrown when you copy and paste text (Ctrl-V) using the R Tool.     Now, to witness it happening:     Diagnosis   Looking at the error log you will see error message below:   Default Log path - C:\ProgramData\Alteryx\ErrorLogs\AlteryxGUI         If you look at the log, you can see the error is directly related to the FIPS cryptographic algorithms. According to Wikipedia, FIPS stands for Federal Information Processing Standards and it is a “standard developed by the United States federal government for use in computer systems by non-military government agencies and government contractors”.   As of right now, “Unhandled Exception occurred” error will be thrown in the R Tool if FIPS compliance is turned on .    Solution   Our Development team is fully aware of the problem with the FIPS compliance and is planning to sort this out in the future releases. As for temporary solution, you can consider turning off the FIPS compliance, of course after checking and making sure your IT manager is okay with it, and this should resolve the “Unhandled Exception occurred” error.   Here’s how you can turn off FIPS compliance:   There are other ways to turn on/off FIPS compliance and you can find them here:   Eddie Wong Alteryx CSE
View full article
The symptoms, diagnosis and solution for the ConnectNamedPipe error associated with McAfee.
View full article
 When attempting to publish a workflow to your private Gallery which contains the Publish to Tableau Server macro, you may encounter an error similar to this:   “ Cannot find macro "PublishToTableauServer_v1.08.1\Publish to Tableau Server.yxmc"   This is typically due to one of two reasons:   The Publish to Tableau Server macro has not been installed on the Alteryx Server where the Gallery is located. The macro has been installed but has not been installed in the correct location, or the Gallery cannot access the macro for other reasons. Please see this link for instructions on correctly installing the Publish to Tableau Server macro on an Alteryx Server.   Even when the macro has been installed properly on the server, this issue can still occur, and if it does, here is a simple workaround to get your workflow published:   Save the workflow to the Gallery: From Designer, click on File > Save As and choose your Gallery. Add the Tableau macro components as assets of your workflow: Click on Workflow Options > Manage workflow assets. Select all of Publish to Tableau Server related assets (currently there are four). Including these assets when publishing should allow the workflow to publish and run successfully in the Gallery.   Thank you!
View full article
You may have run across this error, using the html plugin predictive tools (Linear Regression, Logistic Regression, Decision Tree):   Logistic Regression: Error in searchDir(dbDir, lang) : Logistic Regression: Expecting a single string value: [type=NULL; extent=0]     In 2018.2, this can happen when you have previously had an Admin version of Designer installed, but have since uninstalled.  Once you've installed the 2018.2 non-Admin version with Predictive tools, these errors will now occur.   Help is on the way!  (In the form of suggestions and an upcoming stable release.)  You have several options.  First, you can install an Admin version of Designer concurrently - 11.8, 2018.1, 2018.2, etc.   Last ditch effort: delete registry keys.  This is not recommended - only delete keys if you cannot install a current version, or cannot wait until the next stable update.   Step 0) Save your license key somewhere easy to find: Options> Manage Licenses   Step 1) Open the Registry Editor (type regedit into your windows search bar) and delete the following directory: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SRC\Alteryx   Now, go predict stuff!  Happy Alteryx-ing.
View full article