Skip to main content

Hi Team,

We have reset the password for our DEV runner machine. After reset, the new password is updated in the folollwing places.

  1. AAE client in runner machine (Tools→ Login Settings). Legal disclaimer is checked. Client version is 11.3.1
  2. Web CR - Administration→ Bots to upload the bot files into SVN
  3. All the services are stopped. Reset the login information and restarted
  4. Runner machine is rebooted

Still we are getting the error “Unable to acquire the bot runner's remote desktop session as the bot runner's machine state is unlock” when we try to run the bots and they are not getting invoked at all. Please assist us to resolve the issue.

Hi @Saranya Narayanasamy5 ,

 

Please check that whether the Bot runner machine is allowing Remote desktop session or not.

Dear @Saranya Narayanasamy5,

 

If you are getting the error "Unable to acquire the bot runner's remote desktop session as the bot runner's machine state is unlock" when trying to run bots in Automation Anywhere, it could be due to a number of issues. Here are a few possible causes and potential solutions:

  1. Make sure that the Automation Anywhere Enterprise Client is running on the runner machine and that you are using the correct login credentials. You can check the login credentials by going to Tools -> Login Settings in the AAE Client.

  2. Check that the Automation Anywhere Control Room service is running on the runner machine. You can do this by going to Start -> Run, typing "services.msc", and pressing Enter. In the Services window, look for the Automation Anywhere Control Room service and make sure it is started.

  3. Make sure that the runner machine is not locked or in sleep mode. The bot runner needs an active session to run bots, so if the machine is locked or in sleep mode, the bots will not run.

  4. Check that the bot files are uploaded correctly to the Automation Anywhere Control Room. Go to Administration -> Bots in the Control Room and make sure that the bot files are uploaded and listed there.

  5. If the issue persists, try restarting the runner machine and the Automation Anywhere services. You can do this by going to Start -> Run, typing "services.msc", and pressing Enter. In the Services window, right-click on the Automation Anywhere Control Room service and select "Stop". Then right-click on the service again and select "Start". Repeat this process for any other Automation Anywhere services that are running.

I hope these suggestions help to resolve the issue. Let me know if you have any questions or if you need further assistance.

 

Regards,

Login into VDI and controlroom / botagent,  update auto login credentials   in settings.

Reply


Terms & ConditionsCookie settings