Error Establishing Communication With Psshutdown Service
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Unable to Abort PSShutdown Initiated Shutdown - Error Login Failure Windows 7 IT Pro > Windows 7 Miscellaneous Question 0 Sign in to vote Hi - A PSShutdown -a (abort) command on a remote machine after initiating a PSShutdown -h (hibernation) command returns the error "Error establishing communication with psshutdown service on TARGET1. Login Failure: Unknown user name or bad password" I run both commands from a script, with identical user logon/passwords, so I know the issue isn't what's being reported. The abort command is also being sent well before the time specified for the hibernation command. Has anyone seen this issue before and possibly know why the abort command isn't being initiated? I didn't find any info on this error in the PSTools forums, asked this same question in the MS Community forum, and they referred me to the TechNet forum. Thanks for any help/advice here. -Val63 Edited by Valkarie63 Tuesday, January 14, 2014 1:19 AM Tuesday, January 14, 2014 12:57 AM Reply | Quote Answers 0 Sign in to vote Hi, Please make sure you run it with a user who is member of the administrator group and the "PsShutdownSvc" service is isntalled. Meanwhile, we'd recommend you post this thread to PSTools forum to ask for more professional solution. http://forum.sysinternals.com/pstools_forum8.html Karen Hu TechNet Community Support
Marked as answer by 暁北Microsoft contingent staff, Moderator Wednesday, January 29, 2014 3:39 PM Wednesday, January 15, 2014 5:56 AM Reply | Quote Moderator Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? Privacy statement © 2016 Microsoft. All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback TechNet Products IT Resources Downloads Training Support Products Windows Windows Server System Center Browser Office Office 365 Exchange Server SQL Server SharePoint Products Skype for Business See all products » Resources Evaluation Center Learning Resources Microsoft Techbe down. Please try the request again. Your cache administrator is webmaster. Generated Tue, 11 Oct 2016 12:10:10 GMT by s_wx1131 (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 http://stackoverflow.com/questions/31683374/psexec-fails-to-run-locally-error-establishing-communication-with-psexec-servic About Us Learn more about Stack 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 error establishing locally: Error establishing communication with PsExec service up vote 1 down 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 error establishing communication PsExec service on SUPPORT02: The system cannot find the file specified. EDIT1: It seems that running PSEXEC 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 pse