Jobs failing when using Run As while running service as a service account

PowerShell Universal
1 
Product: PowerShell Universal
Version: 5.6.11

Hello,

I am intermittently receiving the following errors when running jobs on a schedule with a Run As user set:

Error executing job: Failed to login user (1311). System.ComponentModel.Win32Exception (1311): There are currently no logon servers available to service the logon request.

It does not matter what credential is chosen as the Run As user as any will fail randomly after running successfully other times. Running the jobs without a Run As user works without ever receiving this error. I am on Windows Server 2016. Let me know what other information you might need to figure out what might be causing this issue.

Thanks,
Anthony

2

when you run without, how is your PSU instance configured, are you running in the system context or as a service account?

If it runs as a service account, that might rule out issues with dns/intermittent connectivity to your domain controller.

3

The Windows service is configured to use a service account instead of System. I am not certain but we may not be receiving these errors when it is configured as System and is using a Run As user, I was going to perform some more tests to determine that.

4

Do you have any monitoring or are you able to run a script that constantly pings/checks connectivity to your DC from the PSU server to see if there’s any intermittent drops?