Error Establishing Communication With Psshutdown
Topic Rallex Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 09 August 2005 Status: Offline Points: 1 Post Options Post Reply QuoteRallex Report Post Thanks(0) QuoteReply Topic: psshutdown communication errorPosted: 09 August 2005 at 1:23am Hello, I like to use "psshutdown -h -t 5" to set my computer to hibernation after 5 seconds. The result is the following error message: "Error communicating with psshutdown service on local system. The system may not have been shutdown: Die Pipe wurde beendet." What's wrong? Thank you for your support... Ralf muddyh2o Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 13 July 2005 Location: United States Status: Offline Points: 10 Post Options Post Reply Quotemuddyh2o Report Post Thanks(0) QuoteReply Posted: 24 August 2005 at 12:17pm I get the same thing on remote and local systems, except my error is in english "The pipe has ended" This is only since i started using the new version of psShutdown.exe. I need to find my old copy... Kaci Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 01 October 2005 Location: Hungary Status: Offline Points: 1 Post Options Post Reply QuoteKaci Report Post Thanks(0) QuoteReply Posted: 01 October 2005 at 8:36am Hello, I got the same message on my WXP Prof SP2. The interesting part of the problem is that if I use command "psshutdown -h -t 5", I got the error message, but if I use "psshutdown -h -t 0", my computer hibernates immediately as expected. muddyh2o wrote:
This is only since i started using the new version of psShutdown.exe. I need to find my old copy... If you could send me the older version please to kaci@freemail.hu, I would try it. Ciao KaciEdited by Kaci thebds Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 October 2005 Status: Offline Points: 2 Post Options Post Reply Quotethebds Report Post Thanks(0) QuoteReply Posted: 27 October 2005 at 12:15pm I'm experiencing the same issue; happens on win2k pro workstations,win2k servers,and win2003 server; seems to have started to occur after all the latest microsoft security updates were applied. I also update daily wbe down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 09 Oct 2016 23:13:49 GMT by s_ac4 (squid/3.5.20)
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack http://stackoverflow.com/questions/31683374/psexec-fails-to-run-locally-error-establishing-communication-with-psexec-servic Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up PSEXEC Fails to run locally: Error establishing communication with PsExec service up vote 1 down error establishing vote favorite I only have this issue on a single Windows 8.1 machine in my domain when running PSEXEC locally. Before my domain password expired and was changed, running PSEXEC locally with this command worked. \\fs\storage\QA\Mason\psexec\PSExec.exe \\support02 /accepteula -u build -p password -e -s \\fs\storage\QA\Mason\psexec\Cambria_RI.bat Now, it produces this error: Error establishing communication with PsExec service on SUPPORT02: The system cannot find the file specified. EDIT1: It seems that running PSEXEC error establishing communication locally, with a local target (.bat) file fixes this issue. Why suddenly am I restricted to only using local files? EDIT2: Executing the same command as above but with a different target machine machine will also work. psexec share|improve this question edited Jul 28 '15 at 19:15 asked Jul 28 '15 at 17:33 Mason Itkin 67211 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote One known solution for this exact error is to kill any rogue psexecsvc.exe process on the target machine. While this works for remote callers, I suspect it may resolve local issues as well. If the psexecsvc.exe is hanging around after using psexec, something is likely going wrong like an application crash or simultaneous remote executions with mismatching versions. A couple things to look at are; Clean out older instances of psexecsvc. Ensure you have the latest version of the pstools. Ensure you are using the same versions of psexec on all your machines. Use process of elimination to figure out what events are leaving the psexecsvc process running. The psexecsvc.exe should automatically exit and remove itself from %windir% where it is temporarily placed during execution. Cleaning out rogue copies: Check the %windir% directory and make sure you don't have a r