Question

AARI Process - Unable to run the Bot via Scheduler User

  • 4 May 2022
  • 1 reply
  • 3 views

Hi,

 

The Use case is that we have an AARI process which has a form, a bot. Form is used to take the input from user and bot is used to pull the data from underlying application through API call. In order to efficiently manage the licenses, we just want to allocate AARI User license to the users who would be providing the input and run the bot through one unattended bot license only. For this, we have followed the instructions as given in below link: -

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/hbc/prereq-aari-scheduler-user.html

https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-cloud/topics/control-room/devices/cloud-create-device-pool.html

 

Using this, we have taken the below steps: -

  1. Created a scheduler user in Control Room.
  2. Created a custom role in Control Room.
  3. Assign privilege to run the AARI process to this role
  4. Assigned this role to this scheduler user.
  5. Crated device pool
  6. Created Team in AARI app
  7. This user is specified as Run as user in AARI

 

But, for some reason, we are not able to run the bot using this user. We are getting below errors in Audit Logs.

-------------------------------------------------------------

Event Type: Run Bot Finished

Result: Unable to perform auto-login for user r01514

  • R01514 is the bot ID which I am using as scheduler user

Automation Status: Failed

--------------------------------------------------------------

 

When I change the profile of this user and checked the ‘Attest Device Credentials’ checkbox then it started throwing this error: -

 

-------------------------------------------------------------

Event Type: Run Bot Finished

Result: User - r01514 has attested the device credentials, but not chosen to reuse an existing session. Please select the auto login setting as use existing session

  • Whereas, I have done the settings to use existing session in Auto login settings.

Automation Status: Failed

--------------------------------------------------------------

 

Please help to fix this issue. If there is any better way to handle this situation then please let us know. Basically, we don’t want to utilize those many attended bot runner license as of number of users. So, we want to allocate bot task to an unattended bot. Is it possible? If yes, what are the repercussions of this?

 

Thanks


1 reply

Userlevel 4
Badge +8

@Community Edition User Group​ :

 

Please follow the below article and see if that resolves your issue

 

https://apeople.automationanywhere.com/s/article/A360-Java-lang-RuntimeException-User-vdi-has-attested-the-device-credentials-but-not-chosen-to-reuse-an-existing-session

 

https://apeople.automationanywhere.com/s/article/Unable-to-perform-auto-login-for-user-XXXX-post-upgrading-to-A2019-19-Version

 

if you are still facing an issue then please create a support case

 

How to create a support case :

https://apeople.automationanywhere.com/s/article/How-to-create-a-support-case-in-service-cloud

 

if you don't have access to the above link, email the AA Support team "apeopleopsteam@automationanywhere.com" to get access.

 

 

Reply