Having been hit by this one myself, i digged a little in the source an found:
This bug is a misleading logged message,resulting from an unfixed logging statement couple lines before psexec is called. Psexec is called correctly.
If you run into this error, check wether psexec is aviable/executable on the remote host in the calling security context/profile.
Having been hit by this one myself, i digged a little in the source an found:
This bug is a misleading logged message,resulting from an unfixed logging statement couple lines before psexec is called.
Psexec is called correctly.
If you run into this error, check wether psexec is aviable/executable on the remote host in the calling security context/profile.