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.
The Alteryx server is unable to run a workflow that runs properly on the user’s local machine where the workflow was created.
[ODBC Driver Manager] Data source name not found and no default driver specified alteryx
This error can be encountered when running an app or workflow on a Gallery:
Or when uploading a workflow during validation:
Users will also receive the following error when opening a shared workflow where the Data Source Name does not exist on the user’s local machine:
Version ≥ 11.0
A workflow that contains a Data Source Name (DSN) on the Input Data tool.
Confirm that the data source name (DSN) specified in the workflow is pointing to an existing DSN in your machine’s ODBC Data Source Administrator:
***You must have the driver installed on the machine prior to using this guide. The download links to many of the drivers can be found here.
On your local machine, search for ODBC Data Sources (64 bit)
The DSN referenced in the input data tool within the workflow must be listed under either User DSN or System DSN tabs.
The workflow is not able to successfully run because the input data tool cannot reach the database in the following scenarios:
The workflow creator sends a workflow with a database connection to a colleague who does not have the same DSN on their computer.
The workflow gets sent to the alteryx server to run on a scheduled frequency where the DSN does not exist on the server machine.
You must have the driver installed on the machine prior to using this guide. The download links to many of the drivers can be found here.
Once confirmed that the appropriate driver is installed, select to add from either the user DSN or System DSN tab. Generally, the User DSN is what most users will have access to and what is commonly used. You can learn more about the difference between User and System DSNs here.
In order to resolve the error at the local level or on the Alteryx Server, you will need to set up the corresponding DSN found in the app/workflow. The following Community article will provide you step by step instructions on how to set up an ODBC connection .
Once you've established the DSN on your machine, you will now be able to successfully re-run the workflow!
In Alteryx Designer 2019.1, after adding Browse tools to all of the output anchors of a tool using Right-click > Add All Browses OR Ctrl + Shift + B, running the workflow returns an Unhandled Exception error. The workflow runs indefinitely until Designer is canceled from Windows Task Manager.
This error is usually caused by two things:
The file you selected is of a different format than what is selected in the File Format drop down in the Configuration window.
A .yxdb file you are using as an input has become corrupt.
Other causes can be found here: https://community.alteryx.com/t5/Alteryx-Knowledge-Base/Error-FileID-does-not-match-in-the-FileHeader/ta-p/19870
Although extremely rare, if a .yxdb file becoming corrupt is the culprit (one cause is a network connection dropping in the middle of writing the file), you may have a quick and simple way to resolve this potentially stomach-dropping issue:
Open up Windows Explorer and navigate to the file.
Right-click on the file and choose Properties.
Click on the Previous Versions tab.
If you're lucky, there is at least one option of the file that you can revert back to you, hopefully allowing you to avert disaster. Obviously, this doesn't just work with Alteryx files, so perhaps this knowledge will come in handy with other files.
Thanks for reading!
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.
When importing a .xls file using the Input tool, Alteryx produces NULL values for specific cells, why does this happen?
By design, Alteryx uses either the Jet or ACE drivers when importing .xls files. In short, it’s not really an Alteryx issue but rather a limitation on the Microsoft drivers, but there’s always a workaround available, and we’ll dig into it later.
One of the common reasons this happens is due to the logic both the JET and ACE drivers follow. By design, they look at the first eight rows in your document when identifying the data types and their lengths, when it comes to handling Legacy Excel files. Translation, please? If at least one cell within the first eight rows of your file contains more than 255 characters, then the drivers will set the data type as “memo” (i.e., a length that can hold up to 32,768 characters). Now if the data type doesn’t exceed 255 characters within the first eight rows the driver sets the data type as a string with a 255-character restriction. How does this relate back to you? Well, if any of your cell values that are after the first eight rows do surpass 255 characters, then the driver will assign a NULL value to those cells. Confusing, right? It’s a good thing all is not lost, at least not yet.
The user has the choice to work around this issue or fix it in their registry. The workaround includes the following:
From the Input Data Tool configuration, check option 6: "First row contains data." This will force all fields as a V_String.
Configure the Dynamic Rename Tool to "Take Field Names from First Row of Data."
Use the Auto Field Tool to assign the best field type for each data column correctly.
The fix for this involves changing a setting in your registry. These instructions are being provided as well as documented from Microsoft, as Alteryx cannot be sure that changing this setting will not cause problems with other applications. For more information on this issue: http://support.microsoft.com/kb/189897.
To change the Registry setting***
Go to Start > Run and type "regedit"
In the registry go to HKey Local Machine > Software > Microsoft > Jet > 4.0 > Engines > Excel
Double Click: TypeGuessRows
Change the value to 0 (zero)
Another workaround is to save the .xls file as a .xlsx. It’s well known that Microsoft hasn’t updated the legacy file extension since 1997. If this is an option you desire to exercise, fear not, there is a Macro for that, especially if you need to convert files by the masses.
Quick Shout out to DanJones for creating a fantastic app that takes a directory path and converts all xls files to csv or .xlsx respectively.
The post is located all the way in the bottom.
Disclaimer, when it comes to converting a .xls as .xlsx, please review if your workflow has a lot of formatting enabled, if so, please remember that sometimes this will potentially create inconsistencies with your data. It’s also possible to lose some data in the process.
*** For performance reasons, setting the TypeGuessRows value to zero (0) is not recommended if your Excel table is enormous. When the value is set to zero, Microsoft Excel will scan all records in your table to determine the type of data in each column.
Thanks for reading! If you have any questions, please message away!
This error is typically thrown when trying to read a file that does not match the selected File Format, but also in rare cases, from a corrupted file.
Error: FileID does not match in the FileHeader
Common causes/ resolutions:
Inputting a yxdb file? Make sure your file type is .yxdb rather than .csv, .kml, etc.
Trying to access a yxdb while it's updating? If you try to access the yxdb before the module is done running, or if the module crashes/errors during the creation of the yxdb, you'll see this error. Use a Block Until Done tool immediately before your Output tool.
Using a Directory tool/ Dynamic Input? Specify the file type. If your Dynamic Input is pointing to a yxdb template, use the *.yxdb wildcard in your Directory tool, rather than the all-extensions wildcard *.*
Running an app in the Gallery? Check 'Replace a specific string' in the Action connected to the Input tool where you specified the file type.
As always, if this does not resolve your error, please open a Support ticket through the Case Portal.
Microsoft released a fix for the XLS issue described below, this fix is included in their November 14, 2017 Monthly rollup.
For your convenience, this is the link to the fix for Windows 10
And this is for Windows 7 and other OS
We’ve been made aware of an issue connecting to .xls files with the File Format: Microsoft Excel 97-2003 (*.xls). The behavior manifests in two ways.
As an error pop-up box:
'InvalidArgument=Value of '0' is not valid for 'itemIndex'. Parameter name: itemIndex'
Within the Results - Messages pane of the Designer or on the Annotation associated with the impacted tool:
‘Error: Input Data (2): Error opening connect string: Microsoft JET Database Engine: Unexpected error from external database driver (1).\3275 = -535434136’
The error box appears when an Input Data tool is configured to open an .xls file for the first time ever (if there are cached tables, then the error box will not appear). The Annotation and Results pane error message occurs when an .xls file is dragged directly onto an Alteryx designer canvas or when a workflow containing an Input or Output tool that connects to an .xls file using the above format is run (within the designer, a server, or on a schedule), respectively.
The error and experience are discussed in this Alteryx Community post, though you can also read about the issue on this external forum and here, documenting this is a widespread experience across many platforms. Towards the bottom of the external forum post, you can see a comment from a Support Engineer on the Microsoft SQL BI team stating that Microsoft recommends not using the Microsoft JET engine drivers as the current solution to the issue. We detail below how to follow that directive within Alteryx.
The root cause of the error comes from Microsoft’s October Security Update (links below).
If you have already had the update installed, must remain using the update, or choose to proceed with the update, you will experience this behavior. In those situations, here are a couple options available to you.
For new or existing workflows:
Within Excel, manually save the .xls file as a .xlsx file and within Alteryx update tools pointing to the old file to point to the new file or Browse to the new file within an Input Data tool
For existing workflows:
Within Alteryx, manually change the File format to ‘Microsoft Excel Legacy (*.xlsx)’ within the affected Input Data or Output Data tool (described below)
For new workflows/new Input Data tools you will not be able to manually Browse out to the .xls file and read it in as you will receive the pop-up error message desribed above. Your options are:
Drag and drop the desired .xls file from the Windows explorer box onto the Designer canvas and then manually change the File format to 'Microsoft Excel Legacy (*.xlsx)'
Drag an Input Data tool onto the canvas and paste the full path of the desired .xls file into the Connect to a Database box within the Configuration pane and then manually change the File format to 'Microsoft Excel Legacy (*.xlsx)'
Option 2 and 3 Step-by-Step
Determine if you have the “Microsoft Excel Legacy (*.xlsx)” option available within your Input Data tool. You can determine this by loading any file into an Input Data tool, and then clicking the “File Format” drop-down. If you have this option, you can skip to Step 7.
Determine the “bitness” of your Office Installation. The file you download will depend on whether you are running a 32-bit or 64-bit version of Office. https://support.office.com/en-us/article/About-Office-What-version-of-Office-am-I-using-932788B8-A3CE-44BF-BB09-E334518B8B19?ui=en-US&rs=en-US&ad=US In this screenshot, I’m using a 32-bit copy of office.
Browse to the Microsoft Access Database Engine 2010 Redistributable page and click “Download” https://www.microsoft.com/en-us/download/details.aspx?id=13255
Select the download that matches your Office “bitness” from before, then click “Next”. The file will begin to download. Save the file to a location that you can run it from.
Run the previous installer you downloaded. You can simply click “Next” or “Install” through the installation utility, as options do not need to be changed. Once you receive the dialog that the setup has completed successfully, you can click “OK” and continue to the next step.
If Alteryx Designer was open prior to the installation, you should close the program fully, saving your work, and then re-open Alteryx Designer. Otherwise, if Alteryx Designer was not already open, you can open it now.
Within Alteryx Designer: Open the workflow with the issue in Alteryx Designer. b. Click on your Input Data or Output Data tool that is experiencing the issue. (Refer to Option 3 above if you are receiving the pop-up error box while connecting to an .xls file for the first time) c. Click the “File Format” drop-down and choose “Microsoft Excel Legacy (*.xlsx)” d. Data should now display in the preview window and the error should no longer appear if you click off the tool or run the workflow.
We understand this is likely to be a frustrating experience for our users and we are investigating what can be done from the Alteryx side to produce a fix for the issue. We are also following the Microsoft posts to understand what their response will be and if they will take any action toward resolution. Please contact Customer Support to report your experience with this issue, as that will allow us to contact any impacted users directly if and when there is a fix made available.
Updates associated with the error:
Windows 7, Windows Server 2008 R2 - https://support.microsoft.com/en-us/help/4041681/windows-7-update-kb4041681
Windows Server 2012 - https://support.microsoft.com/en-us/help/4041690/windows-server-2012-update-kb4041690
Windows 8.1, Windows Server 2012 R2 - https://support.microsoft.com/en-us/help/4041693/windows-81-update-kb4041693
Windows 10 Original - https://support.microsoft.com/en-us/help/4042895
Windows 10 1511 - https://support.microsoft.com/en-us/help/4041689
Windows 10 1607, Windows Server 2016 - https://support.microsoft.com/en-us/help/4041691
These methods should work in most versions of Alteryx.
One of the most common issues we see from clients trying to read in a .csv file is that they are receiving an error starting “Too many fields in row x”, and because of this Alteryx can’t read in the file.
There are a couple of different ways you can resolve this error.
First, in the Input Data tool, you can tell Alteryx to treat read errors as warnings to allow the file to be read in.
This will change the Error to a Warning so that Alteryx can read in the file so you can investigate.
The other method is to read the file in with no delimiter. You can do this by changing the delimiter in the Input Data tool to \0.
Once you have your data parsed back out into its fields, you can use the Dynamic Rename tool to correct your field names, a select tool to remove the original field, and a simple Trim() function to remove the extra delimiter from your data.
This process is illustrated in the attached workflow, created in version 10.1.
What does this error mean?
There was an error opening "[filepath].yxdb": Data at the root level is invalid. Line 1, position 1.
This error occurs when a user attempts to open an Alteryx data file (yxdb) by going to File --> Open Workflow.
This option is specifically designed to open only workflows (yxmd), macros (yxmc), apps (yxwz), and packages (yxzp).
To read an Alteryx data file in to Alteryx please make sure to use an Input Data Tool and navigate to your .yxdb file accordingly. This will insert your data file in to your workflow and enable you to use subsequent Alteryx tools to blend, cleanse, parse, manipulate and augment your data until your heart is content!
I am reading a large(ish) .txt file, with fields separated by semicolons.
Out of more than 2 million records, on about 800 I get the error: "not enough fields in record" from the Input Data Tool.
This error is very similar to the error mentioned in this article. Generally it refers to an issue where a particular row of data has less delimiters than previous rows. There are a couple of ways to resolve this and fix the row that is causing the issue. Both solutions from the original forum post will help to make it so you can read the file into Alteryx. Personally, I prefer the option where you read in the data file without a delimiter (either specify None or use \0). This forces all the data into a single field which you can then easily parse out using the Text to Columns tool as noted in the first article linked above.
Attached is a sample that shows the parsing method to resolve the issue.
The other way to go about it is to use the process below:
In the Input Tool configuration, there is a "Treat Read Errors as Warnings".
If you check this it will typically allow all the records to be imported and then you can determine where the issue is (it should give you warnings on the records with an issue).
Why am I getting the error "InvalidArgument=Value of '0' is not valid for 'itemIndex'. Parameter name: itemIndex" when trying to load an Excel file in and Input tool?
This error has come up when an Excel file that had the extension .xls, but was saved as .xlsx, or vice versa. The resolution to this is to save the file with the original extension.
Sometimes when reading a delimited text file (like CSV) an error like this may appear ‘Error reading “FILEPATH\MYFILE.txt”: Too many fields in record #’
The cause of this error is that too many delimiters were located in that specified record.
For example if I had a text file with the contents below:
You see that at record 6 (assuming x and y are field headers) I have an extra comma. If I’m specifying the delimiter to be a comma, Alteryx has recognized from the first record that there should only be two columns in this dataset. Since it sees three on record 6, it will error.
If you had the opposite case where you started with three commas for each record then suddenly had two like this:
You would just get a warning like this:
'Warning: Input Data (1): Record #6: Not enough fields in record'
And the last record in the third field will just be null.
So how do we get around this? Well we could always go into the text file itself and edit the file. This could be cumbersome if you have a lot of records in the text file. Instead let’s just use Alteryx to solve our problems.
First, let’s change our Input Data Tool to bring in the file as a non-delimited text file:
Now we can attach the Text To Columns Tool to separate the fields by our specified delimiter.
Now that our fields have been brought in it’s up to you to decide how handle that extra field, we could simply delete it or keep it. If you’re still wondering about its contents we can simply use a filter tool where the Record ID will be set equal to the record number that popped up in the error.
Attached to this article is a workflow I built in 10.6 that should illustrate this example.
Every so often we get questions about a .tde (Tableau Data Extract) file that is being output from Alteryx that has a file size of 30k when the original data is much larger. When the file is opened in Tableau this error sometimes comes up: An error occurred while communicating with data Source ‘yourfilename.tde’
When importing a delimited file, have you ever run across an error saying ‘Too many fields in record…’ and it’s something like record number 1478254 and you think to yourself, “how the heck am I going to find that record and correct it?”
Well, let us help you with that.
This message is essentially telling us that some particular row of data, when parsed, has more fields that the first row of data (usually caused by an extra delimiter in that row).
The first step in identifying the row is to change the delimiter in the Input Data configuration window. Change the delimiter from the current delimiter to \0 (that is a backslash zero, which stands for no delimiter). This will read in your file but instead of parsing, it’ll just read in the data as is.
Now just add a RecordID tool and Filter tool so we can filter on RecordID 2 (or 1478254) to find the row that is holding us up.
Now that you’ve identified the row that is causing issues, you could go back to your original data, correct it and try importing it again.
If you were looking closely at the example data, you may have noticed that record 4 also had a different number of fields as row 1. After correcting row 2 and importing , again, we would get an error for row 4. Just follow the same procedure to correct additional errors. This could probably be done through an automated/iterative process, but that will have to wait for another time.
(attached is an example workflow created in Alteryx 10.0)
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.
Error: "system.data.oracle client requires 8.1.7 or greater"
Please bear in mind this error is not related to Alteryx but to Oracle. This error message is returned from the Oracle Database, therefore please check with your DBA about the configuration and set up of your machine and server before reaching out to email@example.com. However, we are always happy to help so here are a few troubleshooting tips!
Which database connection did you use?
If you tried using the ODBC connection, try using the OCI (New Oracle Connection). If you do not know what the TNS server name it can be found in the TNSnames.ORA file. Your DBA will also know this.
What permissions do you have?
Go to the Oracle Client folder.
2- Right Click on the folder.
3- On security Tab, Add “Authenticated Users” and give this account Read & Execute permission.
4- Apply this security for all folders, Subfolders and Files (IMPORTANT).
5- Don’t Forget to REBOOT your Machine; if you forgot to do this you will still face the same problem unless you restart your machine.
*Before changing any permission settings please check with your IT
How many instances of Oracle do you have installed?
Oracle may find it difficult to navigate and select the correct version if it has more than one version installed. If you only need one of them it is better just to remove them all and reinstall the one that is needed.
Do you have the correct drivers installed?
One way to check to see if you have the right drivers installed is to set up the DSN connection through Alteryx, navigate to the ODBC admin and see if any drivers populate for either the 32 or 64 bit connections.
Do you have one of the supported client versions?
Please see the Technical Specifications
Please bear in mind often this error is not related to Alteryx but to Oracle. This error message is returned from the Oracle Datbase side and therefore please check with your DBA about the configuration and set up of your client before reaching out to Alteryx Support
Client Service Support Engineer
Unable to find the dll: "OCI.dll"
Within Alteryx this error will be prompted due to a mismatch between 32/64 bit drivers and the Alteryx bit version. This error may also appear if you do not have the drivers installed.
One way to troubleshoot this is to find out what drivers you have installed!
You can use an input tool in the Alteryx designer and select either ‘Database connection’ for 64bit or ’32 Bit Database Connection’ for 32 bit. You can then click on the New OleDB or New ODBC connection and in the next pop out window it will populate with the available drivers for those connections. If you have no drivers in this pop out window this means you do not have the correct drivers for 32 bit or 64 bit connection dependent upon which one you chose.
On our technical specification page (http://www.alteryx.com/techspecs ) we have links to the driver installation pages. This will take you away from the Alteryx website and onto the driver provider’s pages. Please consult with your IT to find the correct drivers for your environment.
Client Services Support Engineer
Errors from the R tool, and macros using R, such as the Association Analysis tool, can be a challenge to troubleshoot. Since R is very particular about naming conventions, and the R macros are very particular about delimiters, one easy way to preemptively limit these errors is to make sure your field names are R-friendly and compliant.
Best practices is to use only letters, numbers and the underscore. Any special characters will likely upset R. One hint is "Error: No valid fields were selected." This means that one of the Pipe-to-Rows tools embedded in the R macros could not appropriately parse the field names.
For example, the following errors came from the Association Analysis tool, where the field names contain the gamut from asterisks to ampersands:
Error: Association Analysis (4): The Action "select fields A" has an error: ParseError: Expected entity name for reference at line 7 and column 30 while processing "Action_UpdateRawXml"
Error: Association Analysis (4): The Action "select fields A" has an error: ParseError: Expected whitespace at line 13 and column 63 while processing "Action_UpdateRawXml"
Error: Association Analysis (3): The Action "select fields A" has an error: ParseError: Unterminated entity reference, 'test' at line 4 and column 30 while processing "Action_UpdateRawXml"
If you have a thousand fields with every special character, don't fret. Dynamic Rename and regex to the rescue!
Using the Rename Mode: Formula, select all your fields, and replace any non-word character with an underscore:
Crisis averted! Happy Alteryx-ing.
My workflow was doing just great, reading in a bunch of stuff and cranking out new data like a boss. But then I saved the workflow, closed down Alteryx, and now when I try to open that file up again, I get the following error:
There was an error opening "C:\my file name.yxmd" There is an unclosed literal string. Line 3042, position 42.
Does this mean anything to you guys?
The workflow has likely become corrupted, perhaps after saving it across a network, and has dropped something in the save process.
Alteryx creates backups of the workflows (same name with a .bak extension). Try to open the .bak file in Alteryx.
Go to File ->Open and change the "Files of Type" to All Files. The .bak files will show up and you can open the one you are having difficulty with.
Another alternative would be to check if Alteryx auto-saved it prior to your last save. Go to File -> Open Autosaved files.