I've found a solution myself: When psexec starts at first time is needs your assept for EULA. And though CCNet servise used its own(dedicated) user, that EULA was newer assepted.
- logon CCnet user - assept EULA .... and everithing goes OK!!!! 2009/1/8 Zheka Borodkin <[email protected]> > I'm using psexec for running scrips like start/stop services on remote the > computer. > > In comand line everything goes perfect but when I moved script to CCNET it > hung. I have suspicion that it coused by the fact that CCnet is windows > service. > > I expoct that it is good known problem, and I'm not the fist. Please share > you experience :)! > > 2009-01-06 18:09:37,191 [Deploy:DEBUG] Done executing task "Exec". > 2009-01-06 18:09:37,191 [Deploy:DEBUG] Task "Exec" > 2009-01-06 18:09:37,191 [Deploy:DEBUG] Command: > 2009-01-06 18:09:37,191 [Deploy:DEBUG] .\Executables\psexec.exe \\server -u > domain\user -p password -d -c -i "C:\stop.bat" > 2009-01-06 18:09:37,284 [Deploy:DEBUG] > 2009-01-06 18:09:37,284 [Deploy:DEBUG] PsExec v1.85 - Execute processes > remotely > 2009-01-06 18:09:37,284 [Deploy:DEBUG] Copyright (C) 2001-2007 Mark > Russinovich > 2009-01-06 18:09:37,284 [Deploy:DEBUG] Sysinternals - www.sysinternals.com > > >
