Unattended Bot runner not running when I am not logged in to my virtual machine

  • 16 October 2023
  • 7 replies

Badge +1

I have a problem.  If I am logged in to my virtual machine, even if it is not on my monitor (i.e. I have it minimized)  my bots run with out problem.  If however,  I am not using RDP to connect to the VM.  My bots fail as soon as they get to their first AI Sense or standard recorder action.  Any advice would be greatly appreciated.


Best answer by Chris Delaney 25 October 2023, 17:03

View original

7 replies

Badge +1

Hi Chris,

It sounds like an issue that I had a while back. While I was logged into the device with RDP the bots ran fine but unattended they kept failing at the point that a recorder action was used. Like the bot couldn’t find the object it was looking for.


What I found out was it was an issue with the active session on the VMs. My RDP maintained the active session, but with the bot the session either timeout or the device would go to sleep because there was no activity happening on the screen.


What I wound up having to do is adjust the power settings for the VMs, so that they never go to sleep or turn off the “monitor”. 


I hope this helps.

Badge +1

@bmhelton Thanks for this advice I will give it a try. thanks.

Badge +1

Good Afternoon,


I am still having the same problem even though I have changed the Power Settings on my VMs.  Does anyone else have a suggestion? Any help would be appreciated.

Userlevel 3
Badge +8

Hi @Chris Delaney,

Pleas share the bot agent log files to analyze further:

The Bot Agent log files are available at C:\ProgramData\AutomationAnywhere\BotRunner\Logs 

Badge +1

Good Afternoon @ravi.pothana,

Thank you for looking at this for me.  Attached you will find the logs for the bot runner.  The one other thing I have tried based on a different post that surrounds this same issue is I changed the scale in display settings between my develpment PC and the Runner.  Please let me know if you need any other information.  Thank you again for all the help.



Chris Delaney

Userlevel 3
Badge +8

Hi @Chris Delaney,

Ensure the resolution settings on Bot Creator and Bot Runner devices match when you create and run bots. 

After analyzing the logs, I identified several errors and added corresponding solutions for each error below:

Unable to close session for user ESIAABOT1 as we are not actively tracking this session
-------- Try disabling any security tools or exclude bot agent files from security scanning.
Whitelist all Automation360 folders within AV:Paths to be whitelisted:
* C:\Program Files\Automation Anywhere\Bot Agent
* C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources
* C:\ProgramData\ABBYY
* C:\Program Files\ABBYY SDK
* C:\Users\useid\AppData\Local\AutomationAnywhere
* C:\Windows\System32\Windows.Media.Ocr.dll
* C:\Windows\System32\config\systemprofile\AppData\Local
* C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere
* C:\ProgramData\AutomationAnywhere\

Cannot write metadata: C:\Users\ESIAAB~1\AppData\Local\Temp\AISenseLogs\bca630a6-8568-4651-9327-3c5ce3ac2fb2_726b74097aec21b4\learning_metadata.json
- Ensure bot agent service account has required permissions to write logs.

-Ensure AVX is enabled in the VM 
Validate using sysinternals: 
For vmware VM - 

-If your bot agent is running on Server OS - Ensure "Desktop experience" feature is installed.

Cannot find window or application titled 'Search - Delivery Order' that was open during recording.
-Validate if the window title is not dynamic.
-Ensure multiple windows are not open at the same time; if it is, go with "Active window title" in any window-based commands.

Error occurred while getting browser tab from window Tab not found with regex pattern match 
-Automation 360 plugin is enabled
-Update web browser and the extension
-reinstall the bot agent using admin rights if issue persists. 

Unable to perform SETTEXT action. TEXTBOX is unavailable.
- update packages 

Badge +1

Good Morning @ravi.pothana,


Thank you for this help.  It resolved my problem.  I appreciate the time and also the links that gave me the instructions to fix these issues.  Thank you again.


To the community I accidently picked this thread as best answer.  Please refer to the post immediately above this for the resolution.



Chris Delaney