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 you observe an error message like Error: Salesforce Input (1) File " ", line 1 os.environ['PATH'] = r"... please read on to learn how to adjust the environment variables to resolve it. This can happen with any one of several Connector tools, not just the tool mentioned in the example.
Error connecting to Office 365 using the Sharepoint Input tool - "The sign-in name or password does not match in the Microsoft Account system", when the user tries to connect to Sharepoint from the Alteryx Designer
In some cases a customer using the Publish to Tableau Server macro encounters the error message "Failed to start a new Hyper instance". The only currently working solution for this is to perform a nuclear uninstall and then reinstall of Alteryx Designer.
Troubleshooting Invalid Path: "Cleanse.yxmc" / Nested Macro Locations are not supported
Randomly Designer appears to be losing macro references. This results in the below two behaviours.
Invalid path error for macro based tools
In some cases the user will see the error message below when running a workflow containing the Data Cleansing tool. Typically a simple uninstall will not solve the issue.
Invalid Path: "Cleanse.yxmc"
Additionally, the error message below will be shown when trying to use the Publish To Tableau macro.
Invalid Path: "PublishToTableauServer_v2.0.0\Supporting_Macros\PublishToTableauServer.yxmc"
Unable to add Macro paths in User Settings
When trying to add a path to a macro this will lead to the below error.
Nested Macro locations are not supported
This is caused by a corrupted AddOnData folder in %ProgramData%\Alteryx\DataProducts.
1. Close Designer
2. Rename the AddOnData folder in %ProgramData%\Alteryx\DataProducts
3. Restart Designer (to recreate the AddOnData folder)
As always if you encounter issues please feel free to reach out to Alteryx Customer Support.
We are working diligently and intelligently on making connections to databases easier, more secure, and faster in Alteryx. Even when we can make the best possible experience for our users come to fruition, any user may still encounter some issues due to the use of third party drivers and/or the intricate communications between the database, driver, and Alteryx. To help to minimize those issues, Alteryx is tested with an abundance of "supported" databases and drivers that are proven to be compatible but, unfortunately, you just can't test every database and every driver out there. Our technical specifications page found here will show you those databases Alteryx supports, as well as the drivers we have tested and support with respect to each database. This does not mean Alteryx will not connect to a database or driver you do not see on this page (or links within the page), however, Alteryx can not support those databases and/or drivers if troubleshooting or setup is required.
Amazon Redshift: Check 'stl_load_errors' system table for error details When writing to Amazon Redshift, the following error appears: Data Stream In (x): The COPY failed with error: [Amazon][Amazon Redshift] (30) Error occurred while trying to execute a query: [SQLState XX000] ERROR: Load into table 'ayx1XXX' failed. Check 'stl_load_errors' system table for details. Environment Alteryx Designer In-DB connection to Amazon Redshift Cause Amazon Redshift uses the stl_load_errors table to track errors that happen when loading data to a Redshift table. This table contains error messages that will provide necessary detail to determine the cause for an error. For more information on the stl_load_errors table, see Amazon's STL LOAD_ERROR documentation. Solution Users with appropriate permissions can access the table themselves to investigate errors: Open a new Alteryx workflow. Drag an Input Tool on the canvas. Connect to the Redshift database. Go to the SQL Editor Window and enter the following query: Select * From stl_load_errors Run the workflow. The table will return an error code and an error reason. Use the column "starttime" to find the right error. See Amazon's STL_LOAD_ERROR documentation for a detailed explanation of all fields on the table and their load error reference for a list of errors. Solution B If the user doesn't have access to the table themselves, their DBA should be able to provide the same information. Error Message examples String length exceeds DDL length Input data exceeded the acceptable range for the data type, try increasing the field size in Alteryx to resolve the error. This often happens with multi-byte characters. In Alteryx, field size relates to characters, i.e.the value ' Góðan dag' only needs a field length of 9. In Redshift, field size is in bytes, to write out 'Góðan dag', the field size has to be at least 11. See Amazon's document on Redshift character types for more information. Multibyte character not supported for CHAR (Hint: try using VARCHAR) The CHAR datatype in Redshift only accepts single-byte UTF-8 characters. The VARCHAR datatype accepts multi-byte characters, to a maximum of four bytes. The WString datatype in Alteryx is translated into a CHAR datatype in Redshift. To load multi-byte characters into Redshift, use the V_WString datatype in Alteryx. Additional Resources STL_LOAD_ERRORS Documentation from Amazon Database Issues – Working with Alteryx Customer Support Engineers (CSEs)