I have an Attended Bot license and I'm running a bot through a trigger, but the Control Room gets stuck on the message "Connecting to device" and does not proceed.
To fix this, I have to restart the services 2 to 5 times, which is quite tedious.
Has anyone encountered this issue? Is there any configuration or setting I might be missing to prevent this from happening?
Hello community
I´m having issues when running my triggered bot on a device with a runner attended license. This bot is triggered with a mail trigger.
However, when I import the bot to the public folder to trying make test for execution i get this issue:
Connecting to device: “Device Name”
And the bot stay with the Pending execution status.
This only happens for this bot, because there are another bots with no issues.
The Bot Agent connects over port 443, just like regular HTTPS traffic over the web. I would check to see if there is firewall or anti-virus software that is interfering with the communication with the Control Room.
Alternately, you could try uninstalling the Bot Agent, clearing out the cache and configuration files, and reinstalling the Bot Agent.
Folders to clean:
c:\windows\system32\config\systemprofile\appdata\local\automationanywhere
C:\ProgramData\AutomationAnywhere
On that same server, with the same bot agent and in the same control room, other bots connect without any issues. That's why I believe the problem is with the bot itself rather than the environment configuration. But what could it be?
Hello community
I´m having issues when running my triggered bot on a device with a runner attended license. This bot is triggered with a mail trigger.
However, when I import the bot to the public folder to trying make test for execution i get this issue:
Connecting to device: “Device Name”
And the bot stay with the Pending execution status.
This only happens for this bot, because there are another bots with no issues.
That is very interesting. Typically, when I see the bot agent “stuck” in this state, it is because the Bot Runner has been stopped at an inopportune time. It makes me wonder if the bot is crashing something, kind of what
One way to figure that out is to look at the bot runner logs, typically at C:\ProgramData\AutomationAnywhere\BotRunner\Logs (note that “c:\programdata” is a hidden folder).
You can also reset the bot agent using this site I made: https://developer.automationanywhere.com/deletedevice.php which isn’t a solution to the problem here, but rather a way to get the bot runner unstuck from its current state.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.