Error executing job: Did not receive port from client process

PowerShell Universal
1

Attempting to use vaulted creds to run as - worked for a while, but subsequently just throws “Error executing job: Did not receive port from client process” each time a run as is attempted. Log of the error is below. Confirmed that the process is being created with the specified credentials, but have not made any headway on debugging this issue.

2020-07-12T21:47:08.7475853-04:00 [INF] Error executing job 53: Did not receive port from client process. at UniversalAutomation.ExecutionService.ExecutePowerShell(Script script, IEnumerable`1 parameters, Job job, Schedule schedule, Int32 port, ExecutionCallback callback) in E:\src\universal\src\UniversalAutomation\Services\ExecutionService.cs:line 371
at UniversalAutomation.ExecutionService.TryExecute(Job job, Schedule schedule) in E:\src\universal\src\UniversalAutomation\Services\ExecutionService.cs:line 275
at UniversalAutomation.ExecutionService.Execute(Job job, Schedule schedule) in E:\src\universal\src\UniversalAutomation\Services\ExecutionService.cs:line 138 System.Exception (adf67afd)

2

Also found that if two PSCredentials are added to the vault, it will always use the first one that was vaulted for run as, regardless of which secret is selected. So if you enter PSCred A followed by PSCred B into the vault, you will always run as PSCred A, even if you select PSCred B.

3

If you run without the credentials the job completes successfully?

4

Yes - the job will run successfully either without credentials, or with the specified first credential - it just won’t ever use a different credential than the first one entered if run as is specified.

5

Ok. Thanks. Looking into it

6

I am having this same issue now. Was there ever a fix?

My script runs fine when using “Default” creds and fails when running as a vaulted service account. I ensured the local security policy settings are set correctly for the service acount.