Question
Australia and New Zealand Banking Group Ltd
IN
Last activity: 7 Feb 2024 21:55 EST
Bot Unable to login VDI via Robot Manager
We are useing 19.1.118 and i think we need to edit "SchedulerDefinitions.xml" . I attached RPA Service logs and current SchedulerDefinitions.xml file.
Note: VDI/Bot is on Microsoft Cloud PC
***Edited by Moderator Marissa to add Support Case details***
Pegasystems Inc.
US
@RohitkumarP7721 The log does contain the means with which to create a new match set that would handle the particular one you are encountering; however, I don't find these particularly easy or necessary to handle. In most cases, the match sets work fine after a restart and don't require any customization to work. Given that, I would simply restart the VDI after you have connected to it rather than disconnecting.
If you want to create a match set for this particular scenario, it is possible using the log you attached, but it is an art and may take some time. You can open a support request and get one of the team to assist if required.
Australia and New Zealand Banking Group Ltd
IN
I restart Microsoft Cloud PC VDI multiple time and it is not working.
I update ScheduleDefinition.xml and i can see in log it is login but still not is not started.. I attached new RPAService Log & ScheduleDefinition.xml For your reference.
Pegasystems Inc.
US
@RohitkumarP7721 I suggest opening a support request. I can't really suggest changes to address your specific login screens without having access to see them. It appears though from the log that you logged in, but there was still something else happening.
Coforge Limited
GB
Based on the log, changes in New_SchedulerDefinitionsxml_0.txt works fine. This is enough to login to VDI using start option from Robot Manager.
Check the following for runtime not getting launched:
1. Check in Robot Manager if a valid automation package is assigned to the workgroup where ASWRobotPOC workqueue is present.
2. Check if any logs (loader / productloader / runtime) in %appdata%\pegasystems has any other information
3. Start the runtime.exe manually in the VDI and see if it is starts without any issues. It should load the package mapped in the workgroup in which the machine is mapped in RM. If not, refer the logs in appdata folder. If there are issues in automation also, runtime may not launch properly.
Australia and New Zealand Banking Group Ltd
IN
Appology for late reply,
We tried your suggestion but unfortunately it is not worked. We raised pega support request INC-B3106.
RPAService Login to system then create task scheduler and immediately it logoff from system those observation found from event-viewer. support team fining root cause why it is logoff immediately.