Error Communicating With Psshutdown Service On
hornerea Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 June 2005 Location: United States Status: Offline Points: 11 Post Options Post Reply Quotehornerea Report Post Thanks(0) QuoteReply Topic: psshutdown v 2.51 failing, pipe errorPosted: 02 June 2006 at 3:32pm Hello, I recently upgraded my PSTools suite from a version in 2004 to the current version. This moved me from psshutdown v. 2.32 to v 2.51. Now I continually get the output: PsShutdown v2.51 - Shutdown, logoff and power manage local and remote systemsCopyright (C) 1999-2006 Mark RussinovichSysinternals - www.sysinternals.com Error communicating with psshutdown service on local system. The system maynot have been shutdown:The pipe has been ended. Normally, I am just trying to log off the console of the local machine, but, I also get the same error trying to actually shut the local machine down. I have seen the previous posting chain from 2005, but, decided to post a new thread in the hopes of getting more attention. Is ANYONE having any luck with the current version of psshutdown? Thanks in advance, Eric Horner hornerea Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 June 2005 Location: United States Status: Offline Points: 11 Post Options Post Reply Quotehornerea Report Post Thanks(0) QuoteReply Posted: 02 June 2006 at 7:39pm I have been thinking about this and tried it again on my home system. This system has also been upgraded to 2.51 psshutdown and works fine, with exactly the same command set that fails on my work machine. Is it possible that this problem is a disconnect between the level of the service that is installed (2.32 at work) and the psshutdown.exe? With psexec, this situation gives a "level of the service mismatch" type message. Maybe the psshutdown client/service is not as robust. Does anyone know of a good way to "uninstall" the services so that I can put in the 2.51 version? Karlchen Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 18 June 2005 Location: Germany Status: Offline Points: 5141 Post Options Post Reply QuoteKarlchen Report Post Thanks(0) QuoteReply Posted: 03 June 2006 at 8:44am Hi, Eric. It may well be that the pssdnsvc.exe (PsShutdownSvc) that psshutdown.exe extracts and loads in order to schedule the next reboot/shutdown changed from v2.32 to v2.51. At least, I would not bet that PsSdnSvc.exe v2.32 and psshutdown.exe v2.5
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) 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, http://forum.sysinternals.com/psshutdown-v-251-failing-pipe-error_topic6187.html 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 https://social.technet.microsoft.com/Forums/office/en-US/d2de0504-758e-4530-9967-c2c5ebeb77f1/unable-to-abort-psshutdown-initiated-shutdown-error-login-failure?forum=w7itprogeneral 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 Off(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Could not start PsExec service on target machine. Access is denied. Windows 7 IT Pro > Windows 7 Miscellaneous Question 0 https://social.technet.microsoft.com/Forums/office/en-US/96decbd7-16eb-44a7-aa64-5ab1eeff976a/could-not-start-psexec-service-on-target-machine-access-is-denied?forum=w7itprogeneral Sign in to vote Hi, I am trying to execute psexec command to remote http://www.tech-archive.net/Archive/Windows/microsoft.public.windows.terminal_services/2008-05/msg00199.html machine. My command is psexec -u domain\user -p password \\machineName -c abc.bat I am trying from windows 7(64 bit) machine. The remote machines are xp and windows 7(32 and 64 bit). In XP machines, it is working and also in some windows 7 machines. But in some windows 7 machines it give message- "Could not start error communicating PsExec service on target machine. Access is denied." If I try to execute psexec command from XP machines, it works to all machines. Suddenly what happen I do not know but one of the windows 7 machine( where psexec was not starting) , psexec started. but not in other machines. Now I am very much confuse here exactly what happen. and what is the issue. Please help. It urgent. error communicating with Thanks. Tuesday, November 01, 2011 7:45 AM Reply | Quote Answers 2 Sign in to vote Hi, When opening the Command Prompt, please right click it and run as Administrator. Meanwhile, make sure the user has administrator privileges on target PC. If the issue persists, try to disable UAC on both sides. As far as I know the Security Level on Windows 7 is higher than the level on Windows XP. Therefore, 'psexec' works to all machines. Best Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Proposed as answer by Sean Mallonee Tuesday, November 08, 2011 12:14 AM Marked as answer by Niki HanModerator Monday, November 14, 2011 1:02 PM Thursday, November 03, 2011 8:29 AM Reply | Quote Moderator 0 Sign in to vote Hi, I had exacly the same issue today, only that I had many servers (2003, 2008 nad 2008 R2) Run command exacly as yours, from W7 SP1 and a elevated command window. It worked on 80% of the servers but on some it didn't work,
without any problem though. I used psshutdow.exe and got this: --------- E:\PsTools>psshutdown -f -o \\PW-fp2 PsShutdown v2.52 - Shutdown, logoff and power manage local and remote systems Copyright (C) 1999-2006 Mark Russinovich Sysinternals - www.sysinternals.com Error communicating with psshutdown service on PW-FP2. The system may not have been shutdown: The pipe has been ended.------------------ So I'm totally stuck. Help please. LittleIT "Vera Noest [MVP]" wrote: Try a remote reboot from another server or an XP client (with the shutdown command), then connect to the file system (the C$ share) and delete the profile. _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net *----------- Please reply in newsgroup -------------* =?Utf-8?B?TGl0dGxlSVQ=?=