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.
Solved
Bot Deploy Failed
+4Best answer by Stefano 5934
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:
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:
+4Logs were where you stated. They got me on the track to find out that our URL had been misconfigured in the control room somehow. That isn’t something we’ve ever changed in the past, but apparently upon installation this time around it was missing the “s” in the url from https.
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.