Skip to main content
Question

Bot Deploy Failed

  • 31 August 2024
  • 1 reply
  • 27 views

We have a new A360 on-prem control room installation and any attempt to deploy to a bot runner fails with a generic “deploy failed” message. Upon some investigation, the global cache isn’t getting populated and there is no files in %AppData%\Local\Automation Anywhere directory (resources or messaging) like on our other working on-prem instances.

So far, I’ve tried adding/removing devices from the control room, which necessitates uninstalling and reinstalling the bot agent. The control room will show the device as connected as well. I don’t know exactly what control room log files would have the best info, but most of the ones I check don't have any error messages that look promising for diagnosing what’s going on.

1 reply

Userlevel 1
Badge +4

If you're installing the bot agent system-wide, the logs should be in these folders: 

C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere

C:\ProgramData\AutomationAnywhere\BotRunner\Logs

 

You can find more help here:

Bot Agent log files - Automation Anywhere Documentation

Reply