Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Cannot execute "After Run" command on server

albert-hu
6 - Meteoroid

Hi, everyone.

I got a very strange problem regarding executing a command for "After Run" event for a workflow, after it was published to our company's gallery, but the command for "Before Run" was executed successfully.

 

The first picture is the configuration of "Before Run" event.

The second picture is the configuration of "After Run" event.

 

When I ran my workflow in my Designer, both commands were executed successfully. But after I published to our company's gallery, I got this error:

Error running Event #2: The external program "C:\Windows\System32\cmd.exe" returned an error code 1: The system could not find the environment option that was entered. (203).

 

Could anyone help me with a solution?  Thanks a lot in advance!

 

 

before_run_event_command.pngafter_run_command.png

4 REPLIES 4
brindhan
9 - Comet

Hi @albert-hu 

Since the before run event ran ok, one can assume that the license has been configured for access to command line.

 

When I compare the 2 screenshots, I notice that the double quotes have been misplaced in the second config(under command arguments).

 

Hope this helps. Cheers! 

albert-hu
6 - Meteoroid

Thanks a lot for pointing out this mistake. But after I fixed the misplaced double quotes, I still got the same error for "After Run" event.

danilang
19 - Altair
19 - Altair

Hi @albert-hu 

 

The error message 1 is what is returned by the batch file that you're trying to run after your workflow.  Make sure that the account that is running the Alteryx Gallery can run this batch file successfully.  Only then can it run as part of workflow.  It's probably a command option or an environment variable that is defined when you run it locally, but not when the Alteryx service runs it on the server.

 

Dan

albert-hu
6 - Meteoroid

Now the problem is solved.  The problem is caused by that fact that our server admin didn't use the correct account to configure the worker process for "Run As" option. He used a local account. After he changed to a domain account, all commands were executed successfully for the workflow running on server!

 

Thanks a lot for everyone's help!  Very much appreciate it !!

Labels