START failed for Robot. Timeout waiting for robot to register.
Hi
We have a problem with starting robot from RM
There is a message from Audit: START failed for Robot: robot_name. Timeout waiting for robot to register.
Message from RPAService log: Error | 12/07/2021 03:29:15.110 PM | 1 | MTA | Scheduler | Invalid query System.Management.ManagementException: Invalid query at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext() at Pega.RpaService.Common.UserHelper.GetLocalUserFullName(String userName) at Pega.RpaService.Scheduler.LogonEngine..ctor(Process logonProcess, String userName, SecureString password) at Pega.RpaService.Scheduler.LockScreenLogonProcessor.Logon(String userName, SecureString password, Nullable`1 sessionId) at Pega.RpaService.Scheduler.SchedulerProgram.UnlockScreenAndLogon(String userName, SecureString password, Nullable`1 sessionId) at Pega.RpaService.Scheduler.SchedulerProgram.Main(String[] args)
However, when we run the same package from VM, everything is ok, because the robot starts and processes cases from the queue.
We have checked configuration from these links:
Hi
We have a problem with starting robot from RM
There is a message from Audit: START failed for Robot: robot_name. Timeout waiting for robot to register.
Message from RPAService log: Error | 12/07/2021 03:29:15.110 PM | 1 | MTA | Scheduler | Invalid query System.Management.ManagementException: Invalid query at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext() at Pega.RpaService.Common.UserHelper.GetLocalUserFullName(String userName) at Pega.RpaService.Scheduler.LogonEngine..ctor(Process logonProcess, String userName, SecureString password) at Pega.RpaService.Scheduler.LockScreenLogonProcessor.Logon(String userName, SecureString password, Nullable`1 sessionId) at Pega.RpaService.Scheduler.SchedulerProgram.UnlockScreenAndLogon(String userName, SecureString password, Nullable`1 sessionId) at Pega.RpaService.Scheduler.SchedulerProgram.Main(String[] args)
However, when we run the same package from VM, everything is ok, because the robot starts and processes cases from the queue.
We have checked configuration from these links:
https://docs-previous.pega.com/pega-rpa/enabling-pega-rpa-service-simulate-secure-attention-sequence
Could you please tell me how to resolved it?
Pegasystems Inc.
GB
Hi @PawelB84,
The error doesn't seem to be related with the Package but with the RPA Service configuration. Did you configure the credentials to be used in the CredsUtil? If this is correct it might also be the splash screen what is falling. Did you monitor the startup?, when is it getting stuck, starting the Windows session or starting the Robot Runtime?
Uniqa TU SA
PL
We have configured credentials in the CredentialManagerUI. There are 3 entries: RegistrationOperator - UserName and Password from RobotManager RuntimeUser - UserName is the name of the VM WindowsUser - UserName and Pasword is the data of the robotic account that has access to this VM
We have also checked Event Viewer and there are no entries for the login attempt Maybe this is a problem with user permissions? What should the correct permissions be?
Pegasystems Inc.
GB
@PawelB84 , is the Windows session starting? if not, is the login screen the same for both VMs you used?, did you try to watch the login process for that VM? if so, is it getting stuck on it?
Uniqa TU SA
PL
We use one VM and one robotic account to test this connection. When we try to log in manually on this VM everything is ok.
But when we try the same from Robot Manager, nothing happens. Windows session is not starting,and there is no trace in Event Viewer.
We have no physical preview of the login attempt, but we can try to check something else, maybe different system logs?
Pegasystems Inc.
GB
@PawelB84 , logs should be in the RPAService.log file (%ProgramData\Pegasystems\RPAService\RpaService.log). The log entries there should let us know whether there is an issue with the credentials or with the splash/login screen.
Uniqa TU SA
PL
@AngelHermira, that entry was in my first post.
Message from RPAService log:
Error | 12/07/2021 03:29:15.110 PM | 1 | MTA | Scheduler | Invalid query System.Management.ManagementException: Invalid query at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext() at Pega.RpaService.Common.UserHelper.GetLocalUserFullName(String userName) at Pega.RpaService.Scheduler.LogonEngine..ctor(Process logonProcess, String userName, SecureString password) at Pega.RpaService.Scheduler.LockScreenLogonProcessor.Logon(String userName, SecureString password, Nullable`1 sessionId) at Pega.RpaService.Scheduler.SchedulerProgram.UnlockScreenAndLogon(String userName, SecureString password, Nullable`1 sessionId) at Pega.RpaService.Scheduler.SchedulerProgram.Main(String[] args)
Could you explain what this error means?
Pegasystems Inc.
GB
@PawelB84 , that looks like an issue with Scheduler. Which is the part of the RPA service that performs the login. If you have already verified the credentials I'd open an INC to Pega GCS so they can help you to review the SchedulerDefinition.xml and its configuration for the login screen for the VM that you are using.