PAExec seems to have the same problem as PSExec when it comes from running the command from other languages.

The problem seems to be the stdin, stdout and stderr pipes aren't properly terminated after command execution.




MS/Sysinternals don't seem very interested in fixing this problem (PSExec hasn't been updated since 2009!), so I'm hoping PA is a little more responsive and is able to look into and perhaps fix the bug.


asked 14 Dec '12, 13:55

chrismar's gravatar image

accept rate: 0%

edited 14 Dec '12, 16:37

I have got the same problem when I try to run paexec process from my c# application.


answered 17 Dec '12, 22:32

odinmillion's gravatar image

accept rate: 0%

I'm having a hard time understanding what the problem actually is (and maybe nobody actually knows yet?). PAExec forwards stdin to the remote process, and forwards stdout and stderr from the remote process back to the PAExec process. Where does this break down?


answered 18 Dec '12, 09:09

Doug's gravatar image

Doug ♦♦
accept rate: 21%

The problem (for me) seems to be with the redirected pipes. For example, when my PAExec process hangs I see the stdout, stdin and sterr pipes in the open files portion of computer management. It seems that once the process is executed there's a problem removing those pipes. I can do 1 of 3 things to get things to move along, all 3 seem to have the same effect:

1) Remove the open files from computer management on the remote host.

2) Kill the PAExec process on the remote host.

3) Kill the PAExec process on the local host.

I haven't verified whether or not either of those 3 actions will also remove the service on the remote host. I seem to recall they do, but I can't say for certain.

PSExec behaves exactly the same way, and rumor has it this problem didn't exist prior to version 1.72. Of course I've been unable to locate PSExec 1.71 to try.


answered 18 Dec '12, 09:21

chrismar's gravatar image

accept rate: 0%

Do you have a simple PAExec command line that will replicate this so we can see it here? Ideally the simplest example that will reproduce the issue.

(21 Dec '12, 09:10) Doug ♦♦

Running PAexec directly on the CLI doesn't produce the problem. For me, it's run from a perl script that's started by a java executor, so it's the 3rd level down. Running it directly from perl also doesn't cause the issue to happen, it's only when you throw the java bit in.

Here are the full commands:

paexec.exe \\$Host_Name -u $Host::User -p $Host::Password -n 150 reg query "HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727"

paexec.exe \\$Host_Name -u $Host::User -p $Host::Password -n 150 findstr /S /C:" Error time stamp" C:\io_test\*.txt

(21 Dec '12, 09:17) chrismar

(Please excuse the extra escape chars, that's how the commands are in the perl script.)

Nevermind, it looks like the forum software stripped them out.

(21 Dec '12, 09:17) chrismar

Any updates on this issue? I've been experiencing the same problem - when run from java, stdout and stderr are redirected beautifully in their entirety, but at the end of it all, when PAExec should exit, it hangs. Hoping for some support from PowerAdmin on this peculiar behaviour.


answered 16 Oct '13, 03:17

Copperfield's gravatar image

accept rate: 0%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 14 Dec '12, 13:55

Seen: 13,180 times

Last updated: 16 Oct '13, 03:17