Skip to main content

Hello Automation Anywhere Community,

I am experiencing a random and intermittent error when trying to execute bot processes from AARI. The issue does not seem to be tied to a specific bot, as it happens across multiple processes. It also does not happen every time, which makes it particularly difficult to troubleshoot.
 

 

​@LAHCEN AGLAGAL A “line zero” error means there was a problem with pre-processing the automation.

Let’s start here: Do you have an on-prem control room or a cloud-based control room?

​@Aaron.Gleason  yeah it’s an op-prem CR 

​@LAHCEN AGLAGAL Thank you for letting me know. This means you have access to a lot more logging and info on your side.

I would check to make sure the server has enough free space, that temp directories are cleared, watch logging on the server, RAM and CPU, and other basic components of the server. Also, are you up-to-date on the control room? 

Yeah I do

I still have 30 GB of free space, and there's still enough RAM and CPU

May be, you can check this points

  • Check AARI Service Health – Verify AARI service, Bot Agent, and Control Room logs for connectivity drops or restarts.

  • Bot Agent Stability – Ensure Bot Agent is up-to-date, properly registered, and not going offline intermittently.

  • Network & Firewall – Look for unstable network, proxy, or firewall rules that could cause random disconnects between AARI and Control Room.

  • Resource Conflicts – Confirm no CPU/memory spikes or multiple bots competing on same runner machine.

  • Error Logging – Enable detailed logs in Control Room & AARI to identify failure patterns.

  • Retry Mechanism – If possible, configure retry logic for AARI-triggered executions.

  • Upgrade/Patch – Apply the latest Automation Anywhere patches (AARI & Control Room), as known bugs can cause such behavior.

​@LAHCEN AGLAGAL were you able to resolve the error? Sharing the solution can help another community member!

Hello ​@Shreya.Kumar , 

Well, I wasn't able to pinpoint the exact root cause of the issue, but I found a successful workaround. Since we had three different users on the VM and the crash occurred at line 0 (before execution started), I suspected a conflict with the user sessions. My solution was to delete the existing users, create a single new user, and then reinstall the Bot Agent on that new profile. This resolved the "Bot Launcher crashed" error immediately. I know this isn't the technical explanation for the crash, but it provides a working fix, and I will share the root cause if I find it.

 

​@LAHCEN AGLAGAL thanks for sharing the workaround!

Terms & ConditionsCookie settingsAccessibility statement