I was getting an error trying to run a remote command on a Windows XP machine on our domain today:
“Error communicating with PsExec service on [hostname]: No process is on the other end of the pipe.”
As usual, google came to the rescue but it took a lot of forum scanning to find a result. The quick fix is to do this:
You should find a process called PSEXESVC, if you pskill it, then you should be able to use PsExec again.
This happened to me after I’d used the SCCM Configuration Manager Console to initiate a_Interactive Command Prompt_ which I subsequently closed without terminateing the process cleanly.