Device Error in Automation 360 On-Premise

  • 21 February 2023
  • 4 replies

Badge +4

I’m using the newest version of AA360 Control Room On-Premise and Bot Agent but I received Device Error notification. I already set the device up correctly include the credential, how do I solve this issue?


Best answer by rbkadiyam 21 February 2023, 15:02

View original

4 replies

Userlevel 6
Badge +16

Hi @Siti Megawati.S1 

Can you restart your bot agent service and give a try? Check whether your device is connected or not

Steps for Restarting Bot Agent Service :

  • Click on Windows+R
  • Type services.msc
  • Hit Enter
  • Check for Automation Anywhere Bot Agent Service
  • Right Click and Restart



Hi @ChanduMohammad 

i currently facing same issue here and i already restart the bot agent service but still not working

any other solutions?

Userlevel 7
Badge +13

Hi @Siti Megawati.S1 ,


Have you added the SSL certificate to the Java Keystore? If yes then, try resetting the Device through API call.

Userlevel 5
Badge +14

@Siti Megawati.S1 

Device error
If the problem persists please contact your system administrator.



When a control room is set up with Load Balancer and HTTPS protocol, this error might occur if the Control room Access URL is not provided in https under administration=>Settings page

If there is any restriction in downloading the files from control room in the runner machine.
example: The customer had implemented content filtering based on file extension due tow which the dependencies could not be downloaded even though the CR URL was whitelisted in Network.

This can be validated from Node manager logs, and will have entries similar to below.

ERROR [pool-29-thread-2] - com.automationanywhere.nodemanager.service.impl.GlobalCacheServiceImpl - {} - lambda$downloadFile$80( - Unexpected error downloading and saving file: java.lang.RuntimeException: Unexpected response code 403 while downloading the file


Resolution for cause 1:
1. Log in to CR as Admin user
2. Go to Administration > Settings > General Tab > General Settings
3. Update the Control room Access URL with https

Resolution for cause 2:
Engage the customer IT/Network team to unblock the restrictions or content filtering and allow the dependencies to be downloaded from the Control room URL.