topic Re: Unable to run workflow in server in Alteryx Server Discussions

Unable to run workflow in server

Surajnair — Wed, 04 Sep 2024 08:14:02 GMT

Hi Team,

im fetching data from SSMS 18. based on data im doing some transformation.

when i run the workflow in local designer workflow is working and providing me the output.

But when im trying to save it in server it throws me multiple error.

For sql i also even tried with oledb and ODBC it works in designer but not working in server.

Can anyone help me to fix this issue.

Attaching below snap of error.

Re: Unable to run workflow in server

fmvizcaino — Wed, 04 Sep 2024 13:37:45 GMT

Hi @Surajnair ,

From the error message, it looks like you have two different issues:

Can`t find the file: temp.xlsx: Alteryx Server cannot access your local folders - the options are to send the file with the workflow or to add this file to a shared folder that the server has also access to
1. Here is more about workflow assets: https://knowledge.alteryx.com/index/s/article/Assets-and-Packaging-Workflows-1583460636757
Server is not found or accessible: I believe there are three different possible reasons for this
1. DSN not configured on the Server: If you have configured a DSN in your ODBC admin, you need to create a connection with the same name in your server machine. If you don`t have access to your server machine but knows the driver Native Client 11.0 is installed there, you can go with a DSN-less connection string: https://knowledge.alteryx.com/index/s/article/How-To-format-common-ODBC-DSN-less-connection-strings-1583461565318
2. If the connection is defined to use windows authentication, you have to guarantee the server account/run as credential of your server has also access to this database
  1. https://knowledge.alteryx.com/index/s/article/Run-As-Settings-1583459849487#
3. Timeout issue: If both options above are already configured, maybe it is indeed a timeout issue and this can be solved by configuring your dsn settings and adding more
  1. Look the DSN settings and look for a timeout settings somewhere or adjust your dsn-less connection string to look something like this: Driver={SQL Server};Server=server_name;Database=database_name;Trusted_Connection=yes;Connection Timeout=60;

Best,

FErnando Vizcaino

Re: Unable to run workflow in server

Surajnair — Thu, 05 Sep 2024 05:17:36 GMT

Hi @fmvizcaino ,

I tried all the above steps but im still facing issue in DB connection.

please find attached img.

Re: Unable to run workflow in server

fmvizcaino — Thu, 05 Sep 2024 15:24:05 GMT

Hi @Surajnair ,

Not sure if you only deleted from the image, and that was probably my bad. But you need to add the user and password on your connection string.

Driver={SQL Server Native Client 11.0};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;

The password will be automatically encrypted after you click out of the input tool.

Best,

Fernando Vizcaino

Re: Unable to run workflow in server

Surajnair — Fri, 13 Sep 2024 04:41:19 GMT

hi @fmvizcaino ,

I tried above steps but no luck.

After configuring i came to know there is firewall block issue due to which DB is getting blocked.

Still thnx for the help will figure out firewall issue with infosec team then i wil check the same.

Re: Unable to run workflow in server

stirpastie — Thu, 28 Aug 2025 09:21:28 GMT

Hi @Surajnair ,

From the error message, it looks like you have two different issues:
Can`t find the file: temp.xlsx: Alteryx Server cannot access your local folders - the options are to send the file with the workflow or to add this file to a shared folder that the server has also access to
Here is more about workflow assets: https://knowledge.alteryx.com/index/s/article/Assets-and-Packaging-Workflows-1583460636757
Server is not found or accessible: I believe there are three different possible reasons for this
DSN not configured on the Server: If you have configured a DSN in your ODBC admin, you need to create a connection with the same name in your server machine. If you don`t have access to your server machine but knows the driver Native Client 11.0 is installed there, you can go with a DSN-less connection string: https://knowledge.alteryx.com/index/s/article/How-To-format-common-ODBC-DSN-less-connection-strings-...
If the connection is defined to use windows authentication, you have to guarantee the server account/run as credential of your server has also access to this database
https://knowledge.alteryx.com/index/s/article/Run-As-Settings-1583459849487#wacky flip
Timeout issue: If both options above are already configured, maybe it is indeed a timeout issue and this can be solved by configuring your dsn settings and adding more
Look the DSN settings and look for a timeout settings somewhere or adjust your dsn-less connection string to look something like this: Driver={SQL Server};Server=server_name;Database=database_name;Trusted_Connection=yes;Connection Timeout=60;
Best,
FErnando Vizcaino

Really detailed breakdown, thanks Fernando. I’ll start by moving the file to a shared location and then test DSN configuration with the connection string.