PsExec, Error establishing communication with PsExec service
I am getting the following error if I try to use PsExec (psexec \MyServer cmd, nothing fancy)
PsExec v2.1 - Execute processes remotely
Copyright (C) 2001-2013 Mark Russinovich
Sysinternals - www.sysinternals.com
Error establishing communication with PsExec service on MyServer:
Das System kann die angegebene Datei nicht finden.
(Translation of the last part: the system cannot find the file specified)
PsInfo returns:
System information for \MyServer:
Uptime: 346 days 22 hours 24 minutes 18 seconds
Kernel version: Windows Server 2012 Standard, Multiprocessor Free
Product type: Standard Edition
Product version: 6.2
Service pack: 0
Kernel build number: 9200
Registered organization:
Registered owner: Windows User
IE version: 9.0000
System root: C:Windows
Processors: 1
Processor speed: 2.9 GHz
Processor type: Intel(R) Xeon(R) CPU X5670 @
Physical memory: 2 MB
Video driver: VMware SVGA 3D
Now I've read that I should kill the PSEXESVC process on the server, stop the service and delete the service. I did that, but as soon as I retry it, it just recreates the service and it keeps running again.
We also tried to disable the virus scanner for a short test, but that didn't work either.
The best thing is: It worked 2 days ago!
I am out of ideas, maybe someone else could give me a hint?
windows psexec
edited Mar 28 '14 at 13:07
Ƭᴇcʜιᴇ007
98.8k14156212
asked Mar 28 '14 at 12:05
FerocFeroc
2721316
add a comment |
I am getting the following error if I try to use PsExec (psexec \MyServer cmd, nothing fancy)
PsExec v2.1 - Execute processes remotely
Copyright (C) 2001-2013 Mark Russinovich
Sysinternals - www.sysinternals.com
Error establishing communication with PsExec service on MyServer:
Das System kann die angegebene Datei nicht finden.
(Translation of the last part: the system cannot find the file specified)
PsInfo returns:
System information for \MyServer:
Uptime: 346 days 22 hours 24 minutes 18 seconds
Kernel version: Windows Server 2012 Standard, Multiprocessor Free
Product type: Standard Edition
Product version: 6.2
Service pack: 0
Kernel build number: 9200
Registered organization:
Registered owner: Windows User
IE version: 9.0000
System root: C:Windows
Processors: 1
Processor speed: 2.9 GHz
Processor type: Intel(R) Xeon(R) CPU X5670 @
Physical memory: 2 MB
Video driver: VMware SVGA 3D
Now I've read that I should kill the PSEXESVC process on the server, stop the service and delete the service. I did that, but as soon as I retry it, it just recreates the service and it keeps running again.
We also tried to disable the virus scanner for a short test, but that didn't work either.
The best thing is: It worked 2 days ago!
I am out of ideas, maybe someone else could give me a hint?
windows psexec
edited Mar 28 '14 at 13:07
Ƭᴇcʜιᴇ007
98.8k14156212
asked Mar 28 '14 at 12:05
FerocFeroc
2721316
1
Are you running this as administrator? If not, does that make a difference?
– Der Hochstapler
Mar 28 '14 at 12:06
2
is the user account you are running psexec under, or the account specified in the command itself an admin on the target system? psexec needs the rights on the target system to install and start a service.
– Frank Thomas
Mar 28 '14 at 12:32
@FrankThomas Ok, looks like it really was some kind of account problem. I've tried to use -u and -p to connect with username and password, that didn't work. But starting a cmd prompt under the user that has access to the server works.
– Feroc
Mar 28 '14 at 13:09
As the answers allude to, I've seen similar issues happen when a server is managed with different versions of PSEXEC, and one doesn't exit cleanly. Some versions don't seem to be cross compatible. This is why running the version on the server may work (if it was the one that got stuck) or why stopping the service usually works (to clear the way for any version).
– GuitarPicker
Oct 30 '17 at 16:19
add a comment |
I am getting the following error if I try to use PsExec (psexec \MyServer cmd, nothing fancy)
PsExec v2.1 - Execute processes remotely
Copyright (C) 2001-2013 Mark Russinovich
Sysinternals - www.sysinternals.com
Error establishing communication with PsExec service on MyServer:
Das System kann die angegebene Datei nicht finden.
(Translation of the last part: the system cannot find the file specified)
PsInfo returns:
System information for \MyServer:
Uptime: 346 days 22 hours 24 minutes 18 seconds
Kernel version: Windows Server 2012 Standard, Multiprocessor Free
Product type: Standard Edition
Product version: 6.2
Service pack: 0
Kernel build number: 9200
Registered organization:
Registered owner: Windows User
IE version: 9.0000
System root: C:Windows
Processors: 1
Processor speed: 2.9 GHz
Processor type: Intel(R) Xeon(R) CPU X5670 @
Physical memory: 2 MB
Video driver: VMware SVGA 3D
Now I've read that I should kill the PSEXESVC process on the server, stop the service and delete the service. I did that, but as soon as I retry it, it just recreates the service and it keeps running again.
We also tried to disable the virus scanner for a short test, but that didn't work either.
The best thing is: It worked 2 days ago!
I am out of ideas, maybe someone else could give me a hint?
windows psexec
edited Mar 28 '14 at 13:07
Ƭᴇcʜιᴇ007
98.8k14156212
asked Mar 28 '14 at 12:05
FerocFeroc
2721316
I am getting the following error if I try to use PsExec (psexec \MyServer cmd, nothing fancy)
PsExec v2.1 - Execute processes remotely
Copyright (C) 2001-2013 Mark Russinovich
Sysinternals - www.sysinternals.com
Error establishing communication with PsExec service on MyServer:
Das System kann die angegebene Datei nicht finden.
(Translation of the last part: the system cannot find the file specified)
PsInfo returns:
System information for \MyServer:
Uptime: 346 days 22 hours 24 minutes 18 seconds
Kernel version: Windows Server 2012 Standard, Multiprocessor Free
Product type: Standard Edition
Product version: 6.2
Service pack: 0
Kernel build number: 9200
Registered organization:
Registered owner: Windows User
IE version: 9.0000
System root: C:Windows
Processors: 1
Processor speed: 2.9 GHz
Processor type: Intel(R) Xeon(R) CPU X5670 @
Physical memory: 2 MB
Video driver: VMware SVGA 3D
Now I've read that I should kill the PSEXESVC process on the server, stop the service and delete the service. I did that, but as soon as I retry it, it just recreates the service and it keeps running again.
We also tried to disable the virus scanner for a short test, but that didn't work either.
The best thing is: It worked 2 days ago!
I am out of ideas, maybe someone else could give me a hint?
windows psexec
windows psexec
edited Mar 28 '14 at 13:07
Ƭᴇcʜιᴇ007
98.8k14156212
asked Mar 28 '14 at 12:05
FerocFeroc
2721316
edited Mar 28 '14 at 13:07
Ƭᴇcʜιᴇ007
98.8k14156212
asked Mar 28 '14 at 12:05
FerocFeroc
2721316
edited Mar 28 '14 at 13:07
Ƭᴇcʜιᴇ007
98.8k14156212
edited Mar 28 '14 at 13:07
Ƭᴇcʜιᴇ007
98.8k14156212
edited Mar 28 '14 at 13:07
Ƭᴇcʜιᴇ007
98.8k14156212
98.8k14156212
asked Mar 28 '14 at 12:05
FerocFeroc
2721316
asked Mar 28 '14 at 12:05
FerocFeroc
2721316
asked Mar 28 '14 at 12:05
FerocFeroc
2721316
2721316
1
Are you running this as administrator? If not, does that make a difference?
– Der Hochstapler
Mar 28 '14 at 12:06
2
is the user account you are running psexec under, or the account specified in the command itself an admin on the target system? psexec needs the rights on the target system to install and start a service.
– Frank Thomas
Mar 28 '14 at 12:32
@FrankThomas Ok, looks like it really was some kind of account problem. I've tried to use -u and -p to connect with username and password, that didn't work. But starting a cmd prompt under the user that has access to the server works.
– Feroc
Mar 28 '14 at 13:09
As the answers allude to, I've seen similar issues happen when a server is managed with different versions of PSEXEC, and one doesn't exit cleanly. Some versions don't seem to be cross compatible. This is why running the version on the server may work (if it was the one that got stuck) or why stopping the service usually works (to clear the way for any version).
– GuitarPicker
Oct 30 '17 at 16:19
add a comment |
1
Are you running this as administrator? If not, does that make a difference?
– Der Hochstapler
Mar 28 '14 at 12:06
2
is the user account you are running psexec under, or the account specified in the command itself an admin on the target system? psexec needs the rights on the target system to install and start a service.
– Frank Thomas
Mar 28 '14 at 12:32
@FrankThomas Ok, looks like it really was some kind of account problem. I've tried to use -u and -p to connect with username and password, that didn't work. But starting a cmd prompt under the user that has access to the server works.
– Feroc
Mar 28 '14 at 13:09
As the answers allude to, I've seen similar issues happen when a server is managed with different versions of PSEXEC, and one doesn't exit cleanly. Some versions don't seem to be cross compatible. This is why running the version on the server may work (if it was the one that got stuck) or why stopping the service usually works (to clear the way for any version).
– GuitarPicker
Oct 30 '17 at 16:19
1
1
Are you running this as administrator? If not, does that make a difference?
– Der Hochstapler
Mar 28 '14 at 12:06
Are you running this as administrator? If not, does that make a difference?
– Der Hochstapler
Mar 28 '14 at 12:06
2
2
is the user account you are running psexec under, or the account specified in the command itself an admin on the target system? psexec needs the rights on the target system to install and start a service.
– Frank Thomas
Mar 28 '14 at 12:32
is the user account you are running psexec under, or the account specified in the command itself an admin on the target system? psexec needs the rights on the target system to install and start a service.
– Frank Thomas
Mar 28 '14 at 12:32
@FrankThomas Ok, looks like it really was some kind of account problem. I've tried to use -u and -p to connect with username and password, that didn't work. But starting a cmd prompt under the user that has access to the server works.
– Feroc
Mar 28 '14 at 13:09
@FrankThomas Ok, looks like it really was some kind of account problem. I've tried to use -u and -p to connect with username and password, that didn't work. But starting a cmd prompt under the user that has access to the server works.
– Feroc
Mar 28 '14 at 13:09
As the answers allude to, I've seen similar issues happen when a server is managed with different versions of PSEXEC, and one doesn't exit cleanly. Some versions don't seem to be cross compatible. This is why running the version on the server may work (if it was the one that got stuck) or why stopping the service usually works (to clear the way for any version).
– GuitarPicker
Oct 30 '17 at 16:19
As the answers allude to, I've seen similar issues happen when a server is managed with different versions of PSEXEC, and one doesn't exit cleanly. Some versions don't seem to be cross compatible. This is why running the version on the server may work (if it was the one that got stuck) or why stopping the service usually works (to clear the way for any version).
– GuitarPicker
Oct 30 '17 at 16:19
add a comment |
1 Answer
1
active
oldest
votes
I had this same issue, after some trial and error I managed to get it working by using the following long winded command;
"\serverpsexec locationPSExec.exe" \server.DOMAIN.com -u username -p password -e -s cmd
So I had to point to the remote PSExec.exe, then specify the server along with my networks domain name. I also had to provide my username and password but run with higher privileges (-e -s).
Give it a go!
answered Oct 12 '16 at 9:25
WillWill
334
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f734692%2fpsexec-error-establishing-communication-with-psexec-service%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had this same issue, after some trial and error I managed to get it working by using the following long winded command;
"\serverpsexec locationPSExec.exe" \server.DOMAIN.com -u username -p password -e -s cmd
So I had to point to the remote PSExec.exe, then specify the server along with my networks domain name. I also had to provide my username and password but run with higher privileges (-e -s).
Give it a go!
answered Oct 12 '16 at 9:25
WillWill
334
add a comment |
I had this same issue, after some trial and error I managed to get it working by using the following long winded command;
"\serverpsexec locationPSExec.exe" \server.DOMAIN.com -u username -p password -e -s cmd
So I had to point to the remote PSExec.exe, then specify the server along with my networks domain name. I also had to provide my username and password but run with higher privileges (-e -s).
Give it a go!
answered Oct 12 '16 at 9:25
WillWill
334
add a comment |
I had this same issue, after some trial and error I managed to get it working by using the following long winded command;
"\serverpsexec locationPSExec.exe" \server.DOMAIN.com -u username -p password -e -s cmd
So I had to point to the remote PSExec.exe, then specify the server along with my networks domain name. I also had to provide my username and password but run with higher privileges (-e -s).
Give it a go!
answered Oct 12 '16 at 9:25
WillWill
334
I had this same issue, after some trial and error I managed to get it working by using the following long winded command;
"\serverpsexec locationPSExec.exe" \server.DOMAIN.com -u username -p password -e -s cmd
So I had to point to the remote PSExec.exe, then specify the server along with my networks domain name. I also had to provide my username and password but run with higher privileges (-e -s).
Give it a go!
answered Oct 12 '16 at 9:25
WillWill
334
answered Oct 12 '16 at 9:25
WillWill
334
answered Oct 12 '16 at 9:25
WillWill
334
answered Oct 12 '16 at 9:25
WillWill
334
334
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f734692%2fpsexec-error-establishing-communication-with-psexec-service%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Are you running this as administrator? If not, does that make a difference?
– Der Hochstapler
Mar 28 '14 at 12:06
2
is the user account you are running psexec under, or the account specified in the command itself an admin on the target system? psexec needs the rights on the target system to install and start a service.
– Frank Thomas
Mar 28 '14 at 12:32
@FrankThomas Ok, looks like it really was some kind of account problem. I've tried to use -u and -p to connect with username and password, that didn't work. But starting a cmd prompt under the user that has access to the server works.
– Feroc
Mar 28 '14 at 13:09
As the answers allude to, I've seen similar issues happen when a server is managed with different versions of PSEXEC, and one doesn't exit cleanly. Some versions don't seem to be cross compatible. This is why running the version on the server may work (if it was the one that got stuck) or why stopping the service usually works (to clear the way for any version).
– GuitarPicker
Oct 30 '17 at 16:19