|
#1
|
|||
|
|||
Could it be due to firewall setting? Remotely running the batch file works, but the exit code seems not able to catch, hence it stucks in execution state.
However when I tried to remotely execute the psbatch with command "powershell -command" the VBP is able to show the error and shows program completed with exit code. But when adding "throw" into the batch file it will stuck in execution. |
#2
|
|||
|
|||
I wouldn't think so. At first, you said that Visual Build continues as if no error occurred, but more recently you say that Visual Build "stucks in its execution state", so I'm not sure exactly what's going on. From the sound of it, I would guess that PsExec is never finishing and Visual Build is waiting for it. Which version of PsExec are you using? Which version of Visual Build? Which version+SP of Windows on local and remote? Any more details you can provide (see http://www.kinook.com/Forum/showthread.php?t=3044) might help. Thanks.
|
#3
|
|||
|
|||
I added start-process -PassThru in the batch file and get the ExitCode from Powershell, seems to be working in my test now.
Thanks for the assists along the way, much appreciated. |
Tags |
error , halt , powershell , vbp |
|
|