PSaexec Multiple connections to a server or shared resource by the same user

Viewed 0

I am trying to connect to another server and it is driving me nuts.... If i remote connect onto the server A .. and run paexec it works.. but for some reason i cannot go any farther

cmd.exe /c d:\psfiles\scripts\paexec \\XXXXXXps01 -s -u XXX\service-XXXadmin -p PSsvc2! "C:\PROGRAM Files\Microsoft Office\Office14\excel.exe" "\\XXXXXXps01\psfiles\EXCEL\Excel64Work20121 114.1745.xlsm"

I have tried with and with out Userid.. and with out -s and without cmd.exe /c and -w and that did not work it is killing me....

I am using another process to actually submit the process . the service is defined as an administrator on both systems. This process (Peoplesoft) executes an the PSexec

and I am getting the following log Connecting to XXXXXXps01... Failed to connect to \\XXXXXXps01\ADMIN$. Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. [Err=0x4C3, 1219]

Failed to copy [d:\psfiles\scriptspaexec.exe] to [\\XXXXXXps01\ADMIN$\paexec.exe] -- going to try to continue anyway. Access is denied. [Err=0x5, 5] Starting PAExec service on XXXXXXps01... Failed to connect to \\XXXXXXps01\IPC$. Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. [Err=0x4C3, 1219] Failed to connect to Service Control Manager on XXXXXXps01.

6 Answers

I have the same problem but I went a little further in my investigation:

  • I reduced the test network to two computers (a local executing paexec, a remote receiving the commands)
  • If I try to do two paexec.exe one after the other, the second one fails every time
  • I have to wait +-60 seconds before doing the second one
  • It does not do it with all computer configurations and only the remote configfuration is important
  • I have observed that the paexec.exe in the ADMIN$ share stays there for 60 seconds, and I can do another paexec as soon as it disappears and not before
  • If I explicitly delete the paexec in the ADMIN$ share, it makes no difference (as if I did nothing)
  • This behaviour started recently and is related to either a driver or some config change (no idea what change)

When you do the two PAExec commands close together, are the same username and password being used?

yes, and both computers are set to the same username and password. It does the same whether I provide them or not.

I also tried most of the standard (psexec compatible) options to no avail.

We just put out update v1.17 which will create a uniquely named service and use a unique filename for each PAExec service

PAExec-{calling PID}-{calling computername}.exe

This way multiple commands can be running at exactly the same time and they shouldn't overlap or interact in any way.

That solved it.

When you get the "multiple connections to a server..." error, run the following from a command prompt:

net.exe use

I expect you'll see there is already a connection to that server, but using a different username. You could do a "net.exe use delete" command to remove the existing connection before trying to make another connection.

Has anyone come up with an answer ??? or do I have to wait 60 sec to actually Process ????

I have tried to connect to an IP address and I get farther But no Messages to give me a clue what is happening.. Connecting to xx.1.50.252... Starting PAExec service on 10.1.50.252... Failed to connect to Service Control Manager on 10.1.50.252.

PAExec returning exit code -6

the script d:\psfiles\scripts\paexec.exe \\xx.1.50.252 -u xxxxx\service-xxxxx -p xxxxxx -lo d:\psfiles\PAExec.log "C:\PROGRAM Files\Microsoft Office\Office14\excel.exe" "\\yyyyyy1\psfiles\EXCEL\Excel64Work20130102.1541.xlsm" /e/2012/10/11/ReFresh_Info/readonly/readonly/PSFINDEV//////

There should have been an error message showing but it looks like it's missing. We've just updated it to show the reason why it can't connect to the Service Control Manager. Please give that a try. Also, use the -lo {filename} to create a log file and paste it -- maybe it will show more details then are going to the screen.

That solves my problem. Thanks.

But if you ever find out why it does that, drop me a comment :)

Related