Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.
Don't forget to submit your entry for the Excellence Awards by October 30! | Need more information about the program? Check out the blog here

Change installation path Alteryx

7 - Meteor

Hi Gurus,


We are currently on Alteryx v11.x and we have two environments - DEV and PROD

We have a set of business users who are running a series of  Alteryx workdlows using scripts which they are triggering from their local machines.

User is trying to run sequential workflow which will be trigger as one after another one workflows using the Commands.


The users have tested their workflows already on DEV where the installation has been done on E: drive.


Now, when they are planning to migrate them to PROD, they are unable to as here the installation is done on C:drive.


I did suggest scheduling from gallery as an alternate option if it would help. However, I wanted to know would "changing the path" would be similar to a completely new install? 

What could be the impact and what precautions need to be taken here?


Any suggestions would be of great help here.



Hi @AshwynS


Are you receiving errors when you attempt to run these workflows? Is it because the executable is not in the same path or the workflow is not in the same path between DEV and PROD (or both?)?

If the engine executable is in a different path, and it is hard coded, an option would be to set the Environmental Variable PATH to the Alteryx bin directory, and then the AlteryxEngineCommand.exe could be accessed without specifying whole path to the executable. There is a helpful How to Set or Change the Path System Variable article from Java article that details this process, which will be the same for the Alteryx bin directory.


Can you please provide an example of what your workflows are doing to execute other workflows? This might help me better understand what you are trying to do and the roadblock you are facing.


Moving the path of the Alteryx Server would require a re-installation of the Server product. You would be able to migrate your MongoDB, but a re-installation would need to occur.