Workflow issue Invalid Directory: G:\

Question

I was able to successfully run the model which I saved within the Alteryx Designer App, however I am receiving a similar error message when saving the "new" model to the server and when trying to run within the server.

Can you let me know if there is any additional steps I may try to resolve these issues?

Below are screenshots of the error messages that I am receiving

image (2).png

image (1).png

abacon · Answer

To echo what @chandra_balusugure  said, @Bhanuares the server operates on it's own machine that needs to have access to the specific folders selected. Additionally, the mapped drives are specific to each machine, meaning you must do the UNC path for the server to recognize it UNLESS you map the drives on the server machine to mirror what you have on your machine.

The screenshot above to make all UNC is a great trick to do this and would recommend whenever you are referencing a file in a workflow that you don't want pushed up with the workflow as well.

Bacon

chandra_balusugure · Answer

Hi @Bhanuares

* Verify that the file is specified correctly in the tool.* Check that the file is in the expected location.
* Verify that the file name has been specified accurately, including file type extension.

* Make sure that Alteryx is configured to have access to the location. If running on Server, note that each Server Worker node will need to be able access that location.* In the above example image, the path to the desired workflow includes a mapped drive letter (Z:)  This is not the best way to designate a path when writing a workflow.  Instead, best practice is to use a UNC path.  A UNC path has a format that gives the hostname as well as the directory structure in which the desired file is located, for example: \HostnameDOTdomainDOTcom\MainDirectoryName\SubDirectories\Filename.csv

* If you have used a mapped drive letter instead of a UNC path, the workflow will probably run correctly from your desktop Designer because you are running from your own account, but this is not the best practice because if you ever share your workflow with a colleague or schedule it to run automatically or publish it to Server, you'll find that running the workflow in the new environment causes it to fail. 
* You can change the paths in your workflow using Options > Advanced Options > Workflow Dependencies.

* You can use the All UNC button to change the paths to UNC paths, and if you desire, you can also test the location to confirm.   Click OK to make the change in the workflow.
* In the scenarios noted above, the colleague or the AlteryxService must have permission to access network shared resources, even with the UNC path.  There is more information on configuring Desktop Automation or Server to grant appropriate permissions in other articles.

* The path length cannot be longer than 260 characters.