PowerShell did not response in a timely fashion - trying to test a Hello World script

PowerShell Universal
1 
Product: PowerShell Universal
Version: 1.4.6

Hi everyone

I’ve just set this up as a hosted instance within a local network and trying to run Write-Host “Hello World” script to test it out. Unfortunately I cannot diagnose this error correctly. From the logs:

[10:49:18 INF] Error executing job 17: PowerShell did not respond in a timely fashion. PowerShell Universal is currently waiting 5 seconds for PowerShell to start running the script.
You can increase the timeout by setting the ‘Job Handshake Timeout’ setting in the Settings \ General \ Automation page.
If you are still experiencing issues, you may need to consider increasing the resources available on your system or take advantage of the Random Delay parameter for schedules to stagger jobs.
at UniversalAutomation.Services.GrpcExecutionService.ExecuteScript(Job job, ExecutionEnvironment environment, ExecuteScriptRequest request, ExecutionCallback executionCallback) in C:\actions-runner_work\universal\universal\src\Universal.Server\Services\Automation\GrpcExecutionService.cs:line 113
at UniversalAutomation.ExecutionService.ExecutePowerShell(Script script, IEnumerable`1 parameters, Job job, Schedule schedule, ExecutionCallback callback) in C:\actions-runner_work\universal\universal\src\Universal.Server\Services\Automation\ExecutionService.cs:line 734
at UniversalAutomation.ExecutionService.TryExecute(Job job, Schedule schedule) in C:\actions-runner_work\universal\universal\src\Universal.Server\Services\Automation\ExecutionService.cs:line 381
at UniversalAutomation.ExecutionService.TryExecute(Job job, Schedule schedule) in C:\actions-runner_work\universal\universal\src\Universal.Server\Services\Automation\ExecutionService.cs:line 487
at UniversalAutomation.ExecutionService.Execute(Job job, Schedule schedule) in C:\actions-runner_work\universal\universal\src\Universal.Server\Services\Automation\ExecutionService.cs:line 208 System.Exception

I’m running v 4.2.20 on PowerShell 7. So far all the other setup has looked like it’s good. I’ve tried other commands like $PSVersionTable and same error. I assume I have some setup errors, but can’t pinpoint anything yet. Has anyone had anything like this before?

Some other information that’s hopefully helpful.

  • Login is the admin
  • IIS app pool identity is a domain login with admin access on the VM
  • running the same script on the VM itself is successful under the same login
  • Tried running as with the domain login as a username/password secret with the same error as well

Any tips?

Thanks in advance!