Skip to main content

We are currently running into an issue with some unattended bots reporting that they failed to deploy.

This only happens with certain bots, and only about once per month (though when it happens, causes any subsequent deploys also fail).

When we log into the bot runner, the bot is stuck on the last line of the task to be executed.

Seems to be an issue where the AA-DB file is locked, and therefore the bot can’t communicate back to the control room that the task is complete??

The control room history indicates this error message when the deploy fails:

“There is already an existing deployment in-progress for this user session - NETWORK\BOTNAME”

The bot runner A360 logs indicate this error:

“Caused by: org.sqlite.SQLiteException: eSQLITE_READONLY] Attempt to write a readonly database (attempt to write a readonly database)”

Our current workaround is to delete the AA-DB file, and restart the bot agent. After we do that, any further deploys are successful.

Posting on this community portal as A360 support has been unsuccessful so far in helping us to determine a fix for this issue. So wondering if any other users have experienced this?

We are on on-prem deployment, control version 33.

 

Thanks!

​@ChrisB3 Thanks for writing! I have seen hang-ups like this in the past but never on a bot runner. Does the frozen bot runner device show up with two user accounts by any chance? 

When this happens, all kinds of weird deployment issues happen. My solution when I see this is to delete the device and re-connect the bot runner device manually. (It sometimes takes 3-4 tries to reconnect.) 

If deleting the AA-DB files and restarting the Bot Agent service works, maybe put that into a batch file that runs daily? Just in case there is something that’s hanging up? I use this batch file for bot creator machines when switching control rooms. Basically does the same thing, but I have to reconnect the bot agent manually. (Run this as administrator.)

@echo off
net stop "Automation Anywhere Bot Agent"
del /f /q c:\windows\system32\config\systemprofile\appdata\local\automationanywhere\*.*
net start "Automation Anywhere Bot Agent"

The other thing to consider is updating your control room. We are on .37 right now, so you’re 4 revisions behind. Hope this helps!

Reply


Terms & ConditionsCookie settings