How to resolve: The PsExec service running on ?????????????? is an incompatible version.
2011-07-21 16:22
976 查看
Issue:
When i try to run PSEcex from a WinXP machine accessing a Win2003 Server, then i get the following error:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
psexec \\server01 cmd
PsExec v1.70 - Execute processes remotely
Copyright (C) 2001-2006 Mark Russinovich
Sysinternals - www.sysinternals.com
The PsExec service running on server01 is an incompatible version.
I copied the newest version on both machines but still get the error.
The server is a 2003 Enterprise Edition, on other 2003 (and 2000) Servers Standard Edition, it works fine.
Root Cause:
This situation occurs when multiple versions of PSTools have been executed on a remote system. The fix below is specifcally for PSExec. It can be applied to other PSTools.
Solution:
The Following steps need to be completed
Stop service
Delete exe from %windir%
Delete exe from %system32%
Delete servce
Example (using sc.exe [service control] from windows resource kit)
sc \\%1 stop psexesvc
del \\%1\admin$\psexesvc.exe
del \\%1\admin$\system32\psexesvc.exe
sc \\%1 delete psexesvc
%1 is the input to a script in this case the remote computer name
--------------------------------------------------------------------------------
Root Cause:
On the target machine look for a file named psexesvc.exe in %windir% and maybe %windir%\system32.
If you find any delete them. (*)
When you launch psexec it copies psexesvc.exe to \\target\admin$, i.e. %windir% on \\target.
Next psexec executes the command you specified.
When the command terminates, psexesvc.exe will be stopped and deleted from \\target.
If this did not happen then an outdated psexesvc.exe might still be on \\target.
I think a previous version of Psexec failed to clean up after itself in the past on a pc
Solution:
Yet I would like to stress it is a workaround, not a real solution - I can understand though if you can live with a workaround for ages as long as it does the trick.
Ok, having said that it is a workaround, I encourage everybody who experiences the same problem to proceed like this:
Make sure no psexec is running targetting the machine where psexesvc will not go away.
Make sure psexesvc is removed from the list of active services on the target machine by proceeding like this:
+ Open a cmd.exe window on the target machine
+ sc query psexesvc
+ sc delete psexesvc
+ sc query psexesvc (should be gone now)
Find any occurences of psexesvc.exe on the target machine, very likely they will be in %windir% and %windir%\system32.
Delete them.
Now go back to your local machine and retry your psexec command. Hopefully it will work now without any complaints about (incompatible versions of) psexesvc. And hopefully, too, psexesvc will die gracefully when psexec terminates.
When i try to run PSEcex from a WinXP machine accessing a Win2003 Server, then i get the following error:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
psexec \\server01 cmd
PsExec v1.70 - Execute processes remotely
Copyright (C) 2001-2006 Mark Russinovich
Sysinternals - www.sysinternals.com
The PsExec service running on server01 is an incompatible version.
I copied the newest version on both machines but still get the error.
The server is a 2003 Enterprise Edition, on other 2003 (and 2000) Servers Standard Edition, it works fine.
Root Cause:
This situation occurs when multiple versions of PSTools have been executed on a remote system. The fix below is specifcally for PSExec. It can be applied to other PSTools.
Solution:
The Following steps need to be completed
Stop service
Delete exe from %windir%
Delete exe from %system32%
Delete servce
Example (using sc.exe [service control] from windows resource kit)
sc \\%1 stop psexesvc
del \\%1\admin$\psexesvc.exe
del \\%1\admin$\system32\psexesvc.exe
sc \\%1 delete psexesvc
%1 is the input to a script in this case the remote computer name
--------------------------------------------------------------------------------
Root Cause:
On the target machine look for a file named psexesvc.exe in %windir% and maybe %windir%\system32.
If you find any delete them. (*)
When you launch psexec it copies psexesvc.exe to \\target\admin$, i.e. %windir% on \\target.
Next psexec executes the command you specified.
When the command terminates, psexesvc.exe will be stopped and deleted from \\target.
If this did not happen then an outdated psexesvc.exe might still be on \\target.
I think a previous version of Psexec failed to clean up after itself in the past on a pc
Solution:
Yet I would like to stress it is a workaround, not a real solution - I can understand though if you can live with a workaround for ages as long as it does the trick.
Ok, having said that it is a workaround, I encourage everybody who experiences the same problem to proceed like this:
Make sure no psexec is running targetting the machine where psexesvc will not go away.
Make sure psexesvc is removed from the list of active services on the target machine by proceeding like this:
+ Open a cmd.exe window on the target machine
+ sc query psexesvc
+ sc delete psexesvc
+ sc query psexesvc (should be gone now)
Find any occurences of psexesvc.exe on the target machine, very likely they will be in %windir% and %windir%\system32.
Delete them.
Now go back to your local machine and retry your psexec command. Hopefully it will work now without any complaints about (incompatible versions of) psexesvc. And hopefully, too, psexesvc will die gracefully when psexec terminates.
相关文章推荐
- The way to select how large is diesel-engined keep an eye on
- How to add dependency on a Windows Service AFTER the service is installed
- Cannot connect to the Docker daemon. Is the docker daemon running on this host?
- How to fix “Firefox is already running” error by Matt Cutts on January 2, 2007 in How to,Linux/Ubu
- [Android]Error running app: This version of Android Studio is incompatible with the Gradle Plugin us
- How to draw an Icon on the IndicatorPane of Series 60
- How to fix the phpmyadmin error “json extension is missing” on Ubuntu 14.04 desktop amd64?
- Unable to start debugging on the web server. The web server is not configured correctly. See help for common configuration errors. Running the web page outside of the debugger may provide further information.
- how to project an icon to any point on the map
- Cannot connect to the Docker daemon. Is the docker daemon running on this host?
- Cannot connect to the Docker daemon. Is the docker daemon running on this host?
- How to find out the Sql Server version and service pack
- Docker出现Cannot connect to the Docker daemon. Is the docker daemon running on this host错误解决办法
- RunningMapReduceExampleTFIDF - hadoop-clusternet - This document describes how to run the TF-IDF MapReduce example against ascii books. - This project is for those who wants to experiment hadoop as a skunkworks in a small cluster (1-10 nodes) - Google Pro
- AS错误-Error running app: This version of Android Studio is incompatible with the Gradle Plugin used.
- [转]How to find who is using / eating up the Virtual Address Space on your SQL Server
- How to fix “The system is running in low-graphics mode” Ubuntu 17.04 or 16.04
- How to enable single sign-on service on the SPS
- docker出现Cannot connect to the Docker daemon. Is 'docker -d' running on this host?导致起不了服务
- Error running app: This version of Android Studio is incompatible with the Gradle Plugin used. Try