Log in failed. Machine is not available. Check credential provider setup

Is there any way to check if this is an issue? Because my client said they didn’t log in and they blame a robot 🙁

Yes, check the Gatekeeper log for the day when the job finished with an error. The Gatekeeper log always contains information about active sessions. Here’s an example of how another active console session is shown in the log file:

2024-10-18 09:35:24.407 +02:00 [INF] Query session
SESSIONNAME USERNAME ID STATE TYPE DEVICE
>services 0 Disc
console second_user 4 Active
31c5ce94259d4… 65536 Listen
rdp-tcp 65537 Listen
{ ThreadId: 94 }
2024-10-18 09:35:24.524 +02:00 [INF] Retrieving /c query session robot1 output { ThreadId: 94 }
2024-10-18 09:35:24.524 +02:00 [INF] Query session with username: robot1 { ThreadId: 94 }
2024-10-18 09:35:24.525 +02:00 [INF] Query session with username robot1 does not exist. { ThreadId: 94 }
2024-10-18 09:35:24.525 +02:00 [INF] User session is not active. { ThreadId: 94 }
2024-10-18 09:35:24.525 +02:00 [INF] <—- Exited from State: RobotiqGatekeeper.States.CheckingInteractiveSessionState { ThreadId: 94 }
2024-10-18 09:35:24.525 +02:00 [INF] —-> State transition to: RobotiqGatekeeper.States.CreatingUserSessionState { ThreadId: 94 }
2024-10-18 09:35:24.535 +02:00 [INF] Attempting to connect to credential provider { ThreadId: 94 }
2024-10-18 09:35:26.569 +02:00 [WRN] Delaying for 00:00:01 ms, then making retry 1. { ThreadId: 94 }
2024-10-18 09:35:29.613 +02:00 [WRN] Delaying for 00:00:02 ms, then making retry 2. { ThreadId: 94 }
2024-10-18 09:35:33.660 +02:00 [WRN] Delaying for 00:00:04 ms, then making retry 3. { ThreadId: 94 }
2024-10-18 09:35:39.856 +02:00 [ERR] Failed to connect to credential provider. Reason is : System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (10061): No connection could be made because the target machine actively refused it. 127.0.0.1:32788
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at RobotiqGatekeeper.CredentialsProviderCommunication.CredentialsProviderTcpClient.<>c__DisplayClass3_1.<ConnectAndSendCredentials>b__0()
at Polly.Policy.<>c__DisplayClass108_0.<Execute>b__0(Context ctx, CancellationToken ct)
at Polly.Policy.<>c__DisplayClass138_0.<Implementation>b__0(Context ctx, CancellationToken token)
at Polly.Retry.RetryEngine.Implementation[TResult](Func`3 action, Context context, CancellationToken cancellationToken, ExceptionPredicates shouldRetryExceptionPredicates, ResultPredicates`1 shouldRetryResultPredicates, Action`4 onRetry, Int32 permittedRetryCount, IEnumerable`1 sleepDurationsEnumerable, Func`4 sleepDurationProvider)
at Polly.Retry.RetryPolicy.Implementation[TResult](Func`3 action, Context context, CancellationToken cancellationToken)
at Polly.Policy.Implementation(Action`2 action, Context context, CancellationToken cancellationToken)
at Polly.Policy.Execute(Action`2 action, Context context, CancellationToken cancellationToken)
at Polly.Policy.Execute(Action action)
at RobotiqGatekeeper.CredentialsProviderCommunication.CredentialsProviderTcpClient.ConnectAndSendCredentials(String credentials) { ThreadId: 94 }

As you can see from the query session, there is an active console session with the username “second_user.” This log shows the same process on the same robot after the session is killed. Therefore, the active console session is only with the robot user “robot1” (and robot finished without error):

2024-10-18 09:40:00.841 +02:00 [INF] Query session
SESSIONNAME USERNAME ID STATE TYPE DEVICE
>services 0 Disc
console robot1 1 Active
31c5ce94259d4… 65536 Listen
rdp-tcp 65537 Listen

I hope this helps you determine if this causing the issue.