Pega RPA Service : Runtime not starting in Windows 2016
Hi,
Our Pega Server is 8.3 and Pega Runtime version is 19.1. We are using Pega RPA service to start/stop bots. We followed the steps as per the below links. Created a windows user and registration user id as per given instructions.
RPA service starts fine, it created two user ids in Pega server one for Service operator and one for runtime robot.
However Pega runtime is not getting started when we click start option from Robot manager. There is no error in RPAService log too.
Attached the RPAService log for reference.
Accepted Solution
Wipro Technologies
IN
This issue has been resolved by changing the Matchsets (Commenting the Disclaimer matchset) in SchedulerDefinitions.xml. Also increased the timeout in Robot Manager.
Pegasystems Inc.
US
From the log it appears as though the session was unlocked and the machine logged-in. I do see that IsRuntimeReady is false. Do you have any adapters in your solution? If so, there is a property yu must set in each of them called RobotReadyForWork. This must be true before work is assigned to that bot. Could that be your issue?
Pegasystems Inc.
US
Looking at your log it appears that the Runtime start did not succeed. What happens when you start the Pega.Loader from the desktop icon? There should be logging in %appdata% that will assist. It is possible that there is no package assignment in Robot Manager or the package could not be found on the Package Server. Those would show up in the logs and testing with Pega.Loader manually should do the same.
Wipro Technologies
IN
It works fine when I start Pega.Loader from desktop icon and BOT shows "green" icon in Robot manager. Loaded packages and created runtime log too.
There is NO runtime log if we use RPA service and start BOT from Robot manager. There is no errors in RPAService log (same I shared already).
Wipro Technologies
IN
Yes, I have deployed one of the version from available list and mapped the WorkGroup using Assign new option. This is working fine when I start the Pega Loader directly from desktop icon. We are having issues only when using RPA service.
Pegasystems Inc.
IN
Hi BHABANISHANKARJ ,
We have just tried to restart the RPA Service and delete the operator id , but when we try to start a robot through a robot manager , it tries to stay in a standby mode . Do you see any other blockers that is causing this issue.
Thanks,
Kamala Krishna
Accepted Solution
Wipro Technologies
IN
This issue has been resolved by changing the Matchsets (Commenting the Disclaimer matchset) in SchedulerDefinitions.xml. Also increased the timeout in Robot Manager.
Boubyan Bank
KW
want to add some points related to Matchsets
- Matchset plays a vital role for Windows Logon .
- matchset has to be tweaked according to the login sequence (the RPAService log collects all identified modules) , based on this the SchedulerDefinition file can be tweaked.
- additionally , each matchset has a continuity option, where , for certain sets , we have to make it continued , instead of stop..
Example
