3/31/23, 4:09 PM Bot Launcher for user session NAME OF RUNNER crashed last recorded

Title
Bot Launcher for user session NAME OF RUNNER crashed last recorded

Summary
Applicable to Automation 360 (formerly Enterprise A2019):
Scheduled unattended tasks failed intermittently and the below error message is present in
the audit logs:

Bot Launcher for user session NAME OF RUNNER crashed last recorded

Cause
Cause 1 :

Scheduled tasks are being launched to run during the Windows log out session process.

This happens when there are scheduled tasks overlapping each other. You can confirm this by
looking into the audit section on your control room and confirming that tasks are being
overlapped eg:

Task A starting at 8 00 pm and ending at 8 30 pm

Task B starting at 8 30 pm and ending at 9 00 pm

The below scenario will cause Task B to fail with the error and get queued or executed as
wanted.

Cause 2:

In case a machine timeout is configured after some point in time, then the error is
encountered. Refer below screenshot

https://apeople.automationanywhere.com/s/article/Bot-Launcher-for-user-session-NAME-OF-RUNNER-crashed-last-recorded 1/7
3/31/23, 4:09 PM Bot Launcher for user session NAME OF RUNNER crashed last recorded

Cause 3:

The environment variables values are pointing to some third-party applications

IBM_JAVA_OPTIONS
_JAVA_OPTIONS
JAVA_TOOL_OPTIONS

Cause 4:

When the bot is being deployed on a bot agent machine with two concurrent windows users in
unattended mode, the queued bot is throwing user session crashed error message.

Cause 5:

The anti-virus might be blocking Agent access to certain folders.

For example, in a particular case, Carbon black endpoint security software was installed on
the end-user machine. This tool was interfering with the Recorder package and causing the
Recorder command to crash. We identified the problem using the Process Monitor tool.

Cause 6:

If the bot execution fails at a different line number every time, the actual reason for the bot to
crash is the execution time. This typically occurs If the bot continues to run for more than an
hour.

Cause 7:

Package version mismatch for a specific package across all Master and Sub bots.

Cause 8: (applicable for version prior to A360.22)

https://apeople.automationanywhere.com/s/article/Bot-Launcher-for-user-session-NAME-OF-RUNNER-crashed-last-recorded 2/7
3/31/23, 4:09 PM Bot Launcher for user session NAME OF RUNNER crashed last recorded

The error is encountered at a specific line with Window->Close package action on a Terminal
Emulator window.

Cause 9:

This error is encountered when the VMware Tools version 11.1.5.x is used

Cause 10: (applicable for version A360.25 or higher)

after the bot deployment starts and the 'Bot Runtime Window' appears it suddenly goes
missing after a few seconds without showing any kind of progress or the current action line,
resulting into description error on Historic/Audit Log on line 0 of 0. there is no sign of crashs
on Bot Agent nor Event Viewer logs due to external interference on process. Root Cause is
tool 'Application Verifier' causing Java process to crash.

Cause 11:

In the Node manager logs, you see this:

"Error creating RDP session. [x:x:x:x] [x:x] [ERROR]

[com.freerdp.core] - rdp_set_error_info:freerdp_set_last_error_ex

https://apeople.automationanywhere.com/s/article/Bot-Launcher-for-user-session-NAME-OF-RUNNER-crashed-last-recorded 3/7
3/31/23, 4:09 PM Bot Launcher for user session NAME OF RUNNER crashed last recorded

ERRINFO_LOGOFF_BY_USER [0x0001000C]"

This means you could be having graphical issues when using RDP approach.

Cause 12:

Automation Anywhere Bot agent is installed at both the User and System levels.

Resolution/Workaround
For Cause 1:
You can address this problem in two different ways:
1. Increase the interval of time between each execution
2. As admin, navigate to Control Room -> Administration -> Settings -> Devices -> Auto
Login Settings
3. Stay away from the "Log off" option.

For Cause 2:
Disable the GPO setting and set the IDLE time out to never.
For doing so, go to Computer Configuration\Administrative Templates\Windows
Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
and change it.

For Cause 3:
https://apeople.automationanywhere.com/s/article/Bot-Launcher-for-user-session-NAME-OF-RUNNER-crashed-last-recorded 4/7
3/31/23, 4:09 PM Bot Launcher for user session NAME OF RUNNER crashed last recorded

Follow the steps below to fix the issue

1.Navigate to Control Panel > System and Security > System > Advanced system settings
(Advanced Tab)
> Environment Variables

2. Check the following Global variables:

IBM_JAVA_OPTIONS
_JAVA_OPTIONS
JAVA_TOOL_OPTIONS

3. If the variables are pointing to third-party applications, delete them

For Cause 4:

This is a known issue with A360. This is fixed in A360.20

For Cause 5:

Whitelist the below locations of AA Bot Agent from the Antivirus.

C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources\[number of the
package]\Automation.CSharpDLL.Wrapper.exe
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\

For Cause 6:
1. Under circumstances where the bot is running for more than an hour, increase
the maximum amount of time for an idle session (a session without client activity). Add the
below registry key in the problematic machine. Registry changes key below:

a.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\Wins
tations\RDP-TCP
DWORD: MaxIdleTime
Value: 3600000 (Decimal) 10 hours
b. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal
https://apeople.automationanywhere.com/s/article/Bot-Launcher-for-user-session-NAME-OF-RUNNER-crashed-last-recorded 5/7
3/31/23, 4:09 PM Bot Launcher for user session NAME OF RUNNER crashed last recorded

Services
DWORD: MaxIdleTime
Value: 3600000 (Decimal) 10 hours
If the bot runs beyond 10 hours, 0 for Never.

For Cause 7:

It is recommended to keep the version for each Package (e.g. MessageBox, Window,
Recorder etc.) the same across all Master and Sub bots.

For Cause 8: (applicable for version prior to A360.22)

This is identified as a defect and is fixed in A360.22 version. Bot Agent crashes when Terminal
Emulator screen is closed via Window->Close package action.

Release Notes:
https://docs.automationanywhere.com/bundle/enterprise-v2019/page/enterprise-
cloud/topics/release-notes/release-automation-360-v22.html

For Cause 9:
Upgrade "VMware Tools" version to the latest version to fix this issue.

For Cause 10: (applicable for version A360.25 or higher)

Open 'Application Verifier' and uncheck every 'tests' option for JavaW.exe process

For Cause 11:

In order to solve the graphical issue, please add /gfx:AVC444 to the device configuration, as
mentioned in the article:

https://aainc.lightning.force.com/lightning/r/Knowledge__kav/ka02t0000008R3OAAU/view

Should the same alert persist, go to your Runner machine, open the Regedit, go
to SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services and add the
Dword AVC444ModePreferred. Set it to enabled. This will ensure the AVC 444 graphics
mode is used in your Runner.

Reference article: https://admx.help/?

Category=Windows_10_2016&Policy=Microsoft.Policies.TerminalServer::TS_SERVER_AVC4
44_MODE_PREFERRED

For Cause 12:

Install the Gflags by following the below article and check for the below error:-
https://apeople.automationanywhere.com/s/article/Bot-Launcher-for-user-session-NAME-OF-RUNNER-crashed-last-recorded 6/7
3/31/23, 4:09 PM Bot Launcher for user session NAME OF RUNNER crashed last recorded

The process 'C:\Users\RR652156\AppData\Local\Programs\Automation

Anywhere\Bot Agent\jre\bin\javaw.exe' exited with exit code 100. The
creation time for the exiting process was 0x01d9099ed5cae72a.
https://apeople.automationanywhere.com/s/article/How-to-check-the-reason-for-any-windows-
process-getting-crashed-using-GFLAG

From the above path bot agent is installed at the user

level: C:\Users*RR652156*\AppData\Local\Programs\Automation Anywhere\Bot
Agent\jre\bin\javaw.exe

Validate the bot agent is installed at the User and System levels both
Uninstall the older Bot agent and deploy the bot.

https://apeople.automationanywhere.com/s/article/Bot-Launcher-for-user-session-NAME-OF-RUNNER-crashed-last-recorded 7/7