|
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. |
|
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.
(09 Jan '13, 09:31)
Galaga
|
|
I have the same problem but I went a little further in my investigation:
When you do the two PAExec commands close together, are the same username and password being used?
(18 Dec '12, 09:15)
Doug ♦♦
yes, and both computers are set to the same username and password. It does the same whether I provide them or not.
(18 Dec '12, 10:43)
Galaga
I also tried most of the standard (psexec compatible) options to no avail.
(18 Dec '12, 10:44)
Galaga
This problem occurs on Win7 64 bit.
(18 Dec '12, 10:45)
Galaga
The net use shows nothing and net use delete does not solve anything.
(18 Dec '12, 10:50)
Galaga
Are you using the latest version of PAExec?
(18 Dec '12, 10:57)
Doug ♦♦
Yes, latest version (as of last week).
(19 Dec '12, 09:52)
Galaga
Can you show an example script (maybe edit your original post above) that shows the command lines you are using?
(21 Dec '12, 09:07)
Doug ♦♦
I really don't see what that will accomplish. The first instance works fine. I copy and pasted the same line twice in a batch file. And I have tried nearly all combinations of the standard options (psexec options). That sounds more like the typical "is your computer plugged in" kind of question. So here is a typical example, but not the only one: paexec.exe \\Bingo -i -d -u Foo -p Bar ipconfig
(21 Dec '12, 09:52)
Galaga
For our side, when reproducing a problem it's important to try the same command as the customer rather than making up our own. In this case, I tried your example command in a batch file and it works fine for me. I've tried altering the command line options as well and can't find a configuration where the second instance fails. I don't know what is different. In my case I tried with and without -u and -p. When I tried -u and -p, I used the same credentials that I'm logged in with. Maybe that makes a difference?
(01 Jan '13, 11:00)
Doug ♦♦
Like I said, the problem is in the configuration of the computer. Something in the configuration makes the service file impossible to delete for 60 seconds. I understand it is next to impossible to track the problem without reproducing it, but I was hopping that since you know which functions you use, there could be an article somewhere mentioning that the service file may be locked for a while after uninstalling/stopping the service.
(01 Jan '13, 13:11)
Galaga
Update: I cannot delete the service like I mentioned in my post, it is an illusion of the network. It lets me believe it is deleted while trying to delete it in the background, and the timer before reporting an error must be larger than 60 seconds so I never saw an error. But I confirmed that locally, the service file cannot be deleted for 60 seconds. On the machine without the problem, the file is deleted right away.
(01 Jan '13, 13:11)
Galaga
Hmmm, I've been programming services on Windows for 15+ years and haven't seen that happen before. And just to be sure we're using the same terminology, you're talking about the PAExec service (seen in services.msc and via the "sc.exe query" command) and not about the ADMIN$ share connection or the actual PAExec.exe file, right? I did some investigation of the service deletion (which basically uses the same API as the sc.exe delete command) and found it could be done a little better, especially considering the case where there are multiple clients connecting to the service. This is v15 now.
(01 Jan '13, 23:40)
Doug ♦♦
Sorry about that, I am actually talking about the file itself (in ADMIN$). The service seems to be shut down and unavailable right after running its command is run (as it should). But the file lingers for 60 seconds, which seems to cause the problem because the next paexec fails to copy its file to start the service.
(07 Jan '13, 09:15)
Galaga
PAExec ought to work even if it can't copy its file -- it will log an error and then continue on to try to create the service. Is the error the same as what travelingwilly below shows -- namely that the second instance of PAExec can't connect to the remote Service Control Manager?
(07 Jan '13, 09:27)
Doug ♦♦
Here is what comes out exactly. I counted to 5 before starting the second execution. C:UsersMeDesktoptests>paexec.exe \mycomp -d -u User -p Password ipconfig PAExec v1.14 - Execute Programs Remotely Copyright (c) 2012 Power Admin LLC www.poweradmin.com/PAExec Connecting to mycomp... Starting PAExec service on mycomp... ipconfig started with process ID 3304 PAExec returning exit code 0
(08 Jan '13, 14:02)
Galaga
Second exec here because comments are limited (why exactly are we conversing in the comments?) C:UsersMeDesktoptests>paexec.exe \mycomp -d -u User -p Password ipconfig PAExec v1.14 - Execute Programs Remotely Copyright (c) 2012 Power Admin LLC www.poweradmin.com/PAExec
(08 Jan '13, 14:03)
Galaga
Connecting to mycomp... Failed to copy [C:UsersMeDesktoptestspaexec.exe] to [\mycompADMIN$paexec.exe] -- going to try to cont inue anyway. Access is denied. [Err=0x5, 5] Starting PAExec service on mycomp... Failed to start service on mycomp The system cannot find the file specified. [Err=0x2, 2] Failed to stop PAExec service. The service has not been started. [Err=0x426, 1062] PAExec returning exit code -6
(08 Jan '13, 14:03)
Galaga
I did more timing tests and as funny as it sounds, the exact delay is 62 seconds! PS: These are Corei7 computers on 100Mb Ethernet.
(08 Jan '13, 14:23)
Galaga
Please see latest post (posting here so you're notified there was an update)
(08 Jan '13, 16:43)
Doug ♦♦
showing 5 of 20
show all
|
|
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.
(07 Jan '13, 11:52)
Doug ♦♦
|