trying to execute a PSEXEC

[VBuild_Rookie]

I can run this from the command prompt with no prob

psexec \\ustpaqaapp001 -u newtonqa\WebSvc -p syk3s*n6wt0n cscript "c:\windows\system32\iisweb.vbs" /stop "PGNewtonAdmin"


but can not run it from the visual build program and I am using the "RUN PROGRAM" tool

[kevina]

Please provide more detail on 'can't run' it from Visual Build Pro. The log entry corresponding to the failure would be very helpful in understanding what didn't work.

Is the error related to not finding the psexec app? If so, the simplest solution is to use an absolute path to the executable you are invoking...

[VBuild_Rookie]

Connecting to OLD_SERVER... Starting PsExec service on OLD_SERVER... Connecting with PsExec service on OLD_SERVER... Starting cscript on OLD_SERVER...
cscript exited on OLD_SERVER with error code -2147024664.

Process completed with exit code -2147024664
Step 'Stop Web Site' failed

[kevina]

Not sure, it works here with this simple test of psexec on a remote WinXP machine located on a different NT domain.

Attached is the build file and the test script I ran with it. [You'll have to change the computername, user and password values from *** to run it]

A reproduceable case would be helpful for troubleshooting. I can only guess that it is some sort of rights issue, but I certainly don't know for sure...

[VBuild_Rookie]

I could not see the attachment ..where is it here on the post or email I looked in both places

[kevina]

Oops, after reviewing my post, I didn't attach the file again :-(

It should be attached to this post.

[VBuild_Rookie]

Ok not sure if this thread is still active if not I will repost.....
Anyway I tried your test.bld with the test.vbs it worked find
so I replaced c:\Test.vbs with c:\Windows\System32\iisweb.vbs /stop "Administration"...just to see if I can stop the Admin web site on the local pc.....I got the same error that I have been getting

"Process completed with exit code -2147024664"

[kinook]

That is odd. In my testing, it succeeds the first time but fails with that error afterwards. One workaround is to redirect the command's output to a file and read the file output (instead of reading stdout). See the attached sample.