Check the context path definition field and ensure the location defined already exists on the server running the Deploy Agent and the correct permissions are allocated based on the user that the Deploy Agent runs as. Another thing to check is to enter the call to the script in the deploy setup as: Windows: cmd /c c:\myFolder\myScript.bat
This error occurs in the deploy log if the path to the script defined for the pre deploy or post deploy commands in the deploy agent aren't valid for the deploy agent to run. It's important that if the script is set to run on the target server via the deploy agent then that script actually lives on the target server and not the Mover or Collage server. The script then needs to be called as the path exists on the computer where the agent is running .
Mover will not build binaries itself, but it can run any batch/ script file that you create. To force the build during the deploy process, first you will need to create a batch/ script file that will compile the source. If the compiled binaries should be copied to the destination but not any of the source files, you will also need to code this into the batch file.
Try running the command using these variations: (using valid paths for your server, of course) sh -c /opt/ script /myScript.sh /usr/bin/sh -c /opt/ script /myScript.sh ksh /opt/ script /myScript.sh /usr/bin/ksh /opt/ script /myScript.sh
According to this kb doc from microsoft the envrionment variables need to be in alphabetical order but the output of the "Set" command shows the variables in all kinds of order after patching to 2.3.0.4 which consequently means you can't override one of the variables with your own set command in a script . ... 1. Running Mover 2.3.0.3 on windows
