I'm trying to run PA from a utility script server to web servers on another network. In the past this has worked about 98% of the time, with an occasional error that I just run again and it usually goes through. Today I am unable to perform this on any of the machines I had connected with in the past: The only details I can see is: Connecting to [HOST]... Starting PAExec service on [HOST]... Received too little data from [HOST]. The pipe has been ended. [Err=0x6D, 109] Failed to stop PAExec service. The service has not been started. [Err=0x426, 1062] PAExec returning exit code -7 On the target machine I can see System events for the PAExec service being installed and started, but no other details that might shed light on why it no longer completes. Any ideas what would cause the pipe to terminate unexpectedly with the "too little data" message? I already have a meeting set-up with our network/firewall team to troubleshoot any traffic/connectivity issues, but hoped maybe it was something simple or config related since there were no changes to our network since this worked last time. THx.

I'm trying to run PA from a utility script server to web servers on another network. In the past this has worked about 98% of the time, with an occasional error that I just run again and it usually goes through. Today I am unable to perform this on any of the machines I had connected with in the past: The only details I can see is: Connecting to [HOST]... Starting PAExec service on [HOST]... Received too little data from [HOST]. The pipe has been ended. [Err=0x6D, 109] Failed to stop PAExec service. The service has not been started. [Err=0x426, 1062] PAExec returning exit code -7 On the target machine I can see System events for the PAExec service being installed and started, but no other details that might shed light on why it no longer completes. Any ideas what would cause the pipe to terminate unexpectedly with the "too little data" message? I already have a meeting set-up with our network/firewall team to troubleshoot any traffic/connectivity issues, but hoped maybe it was something simple or config related since there were no changes to our network since this worked last time. THx.