Quote:
Originally posted by stienessen
OK, even better - I got a failure with a 32 bit system (same error) - so, perplexed I started troubleshooting - I logged the command line that's used and copy/paste the command line to a command prompt and it works!!! - it also worked against my x64 box - now my question is why isn't it working from visual build?
Also on a side-note I couldn't find where visual build stores psexec - I have a copy for myself to run from the command line located in the project directory, but I guess I expected to find a copy of it somewhere under c:\program files\visualbuildpro6 Where does visual build run psexec from? I was starting to think I may have had path problems but since I can't find psexec I'm a bit confused...
|
It could be that PsExec is not in the path for VBP to invoke (cmd.exe will fail with an exit code of 1 if it's unable to launch the specified program). You can verify this by creating and building a Run Program step with a command of psexec and blank computer on the Remote tab. It will fail with "Failed to create process: The system cannot find the file specified" if it couldn't be found.
VBP does not install PsExec; it must be available in its PATH environment.
http://www.visualbuild.com/Manual/programremotetab.htm
07-05-2007, 05:41 PM
Threaded Mode