Skip to main content
Solved

A360 bot agent won't connect after install, and the installer also has a bug

  • December 18, 2024
  • 3 replies
  • 68 views
B
Forum|alt.badge.img+5

Hi,

After installing the A360 bot agent, the Control Room shows the machine’s agent as disconnected. Previously, it was showing as Connected.

Please see attached picture. When I uninstalled A360 bot agent and then tried reinstalling it again, in the installer it says “Install this application for:” with “0” for both options, which is not what’s expected. You would expect the top option to be “For all users” and the bottom option to be “Only me”

We’ve been able to reproduce this issue through our IT spinning up a VM with the latest Windows updates. Additionally, we bought a whole new Windows computer and still get this same problem.

Thanks

Best answer by bradwyatt

Following up on this, the cause seemed to be our anti-virus, SentinelOne.

We updated to the latest version of that, and this issue went away. To be extra sure this issue doesn’t happen again, we added exclusion rules from https://apeople.automationanywhere.com/s/article/A2019-How-to-add-Bot-Agent-into-Anti-Ware-exception-list

View original
1 Attachments
Did this topic help answer your question?

3 replies

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+10
  • Aaron.Gleason
  • Automation Anywhere Team
  • 503 replies
  • December 18, 2024

Have you tried our Community Edition on your personal (non-work) computer? It uses the same bot agent. If it works on your personal computer, then it is likely some software or a system policy at your work that is affecting the installer.

Since this is the first report I’ve seen on it, I would lean toward this being some software or policy at your work that is affecting it.

Vatsy
1 person likes this
  • Vatsy
    Vatsy
B
Forum|alt.badge.img+5
  • bradwyatt
  • Author
  • Navigator | Tier 3
  • 10 replies
  • Answer
  • January 14, 2025

Following up on this, the cause seemed to be our anti-virus, SentinelOne.

We updated to the latest version of that, and this issue went away. To be extra sure this issue doesn’t happen again, we added exclusion rules from https://apeople.automationanywhere.com/s/article/A2019-How-to-add-Bot-Agent-into-Anti-Ware-exception-list

Lu.Hunnicutt
1 person likes this
  • Lu.Hunnicutt
    Lu.Hunnicutt
Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+10
  • Aaron.Gleason
  • Automation Anywhere Team
  • 503 replies
  • January 14, 2025

Thanks for reporting back to us. This information may be useful to other developers here.

Lu.Hunnicutt
1 person likes this
  • Lu.Hunnicutt
    Lu.Hunnicutt

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings