An unexpected error occurred. Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure

Hi @Anindya Kurniawan​ ,

Good Day!

Please find the below KB article for the reported issue and follow the steps.

https://apeople.automationanywhere.com/s/article/A360-An-unexpected-error-occurred-Could-not-start-a-new-session-Response-code-500-Message-session-not-created(people login required).

Thank you.

Unable to create session ''Arrears'' as it already exists.

Why the browser can't be opened ? through Browser: Open package Please check below once

1. Chromedriver and Chrome Version Mismatch

• The error "Could not start a new session" often occurs when the Chromedriver version doesn't match the installed Chrome browser version.
• You're using Chrome 102.0.5005.63 and Chromedriver version 102. However, Chromedriver versioning can be specific down to the minor version. For Chrome 102.0.5005.63, you need the exact Chromedriver version 102.0.5005.63, not just a generic "version 102." If the Chromedriver version bundled with Automation Anywhere's Web Automation package (4.0.10) doesn't match exactly, this error can occur.
• Automation Anywhere's Web Automation package typically bundles Chromedriver, but if Chrome auto-updates (e.g., to a newer patch like 102.0.5005.115), the bundled Chromedriver becomes incompatible.

2. Bot Agent and Web Automation Package Compatibility

• Bot Agent version 21.80 was released around early 2022, and Web Automation package 4.0.10 was released on May 18, 2022 (based on the timestamp in the package name). These versions are quite old compared to the latest A360 releases (e.g., Bot Agent 21.250 as of late 2023).
• Older versions of the Web Automation package might have compatibility issues with Chrome 102, especially if there are known bugs that were fixed in later package versions.

3. Chrome Extension Issues

• Automation Anywhere A360 requires the Automation 360 extension to be installed and enabled in Chrome for web automation to work.
• If the extension isn't installed, disabled, or incompatible with Chrome 102, the browser won't launch properly.
• Additionally, the extension needs "Allow access to file URLs" enabled, and Chrome must allow extensions in Incognito mode if that's how the bot is trying to launch it.

4. Browser Launch Configuration

• The bot might be trying to launch Chrome with an incorrect path, user profile, or settings (e.g., wrong port, invalid address, or missing flags).
• The error mentions "invalid address of the remote server," which could indicate a misconfiguration in the Web Automation package's browser launch settings.
• 5. System-Level Issues
• Chrome might be running in the background, causing port conflicts.
• Security software (e.g., antivirus or firewall) might be blocking Chromedriver or the Automation Anywhere process from launching Chrome.
• Missing dependencies, such as Microsoft Visual C++ Redistributables, can also cause Chromedriver to fail.

Steps to Resolve

1. Ensure Chromedriver and Chrome Versions Match

• Download the exact Chromedriver version for Chrome 102.0.5005.63:
• Visit the Chromedriver download page (https://chromedriver.chromium.org/downloads).
• Download Chromedriver 102.0.5005.63.
• Replace the Chromedriver bundled with Automation Anywhere:
• Locate the Chromedriver used by A360, typically in C:\Program Files\Automation Anywhere\Bot Agent\chromedriver or a similar directory.
• Back up the existing Chromedriver, then replace it with the downloaded version.
• Alternatively, update Chrome to a version supported by the Web Automation package 4.0.10, or update the Web Automation package to a newer version that supports Chrome 102.0.5005.63.

2. Update Bot Agent and Web Automation Package

• Your Bot Agent (21.80) and Web Automation package (4.0.10) are outdated. Update to the latest versions:
• Bot Agent: Update to at least 21.250 (a stable version as of late 2023 [Ref web ID: 5]).
• Web Automation Package: Update to the latest version available in your Control Room (e.g., version 4.15.0 or higher as of early 2025 )

Steps:

• Log into the A360 Control Room.
• Go to Administration > Packages, check for updates to the Web Automation package, and install the latest version.
• Update the Bot Agent via Administration > Devices, or download the latest installer from the Automation Anywhere Support site.
• Newer versions often include updated Chromedriver binaries and better compatibility with Chrome.

3. Verify Chrome Extension

• Ensure the Automation 360 extension is installed in Chrome:
• Open Chrome, go to chrome://extensions/.
• Look for the "Automation 360" extension. If it's missing, install it via the Control Room or Chrome Web Store (your admin might need to provide the link).
• Enable the extension and ensure:
• "Allow in Incognito" is enabled.
• "Allow access to file URLs" is enabled under the extension's details.
• If the extension is outdated, update it to the latest version compatible with Chrome 102.

4. Check Browser Launch Configuration

• In your bot, verify the Browser: Open action (from the Web Automation package):
• Ensure the browser path points to the correct Chrome executable (e.g., C:\Program Files\Google\Chrome\Application\chrome.exe).
• Check if a specific user profile or port is specified. If not needed, leave these fields blank to use the default profile.

5. Resolve System-Level Issues

    Close Chrome Instances:

• Ensure no Chrome processes are running in the background:
• Open Task Manager (Ctrl + Shift + Esc), find chrome.exe, and end all instances.
• Retry running the bot.

   Disable Security Software Temporarily:

• Temporarily disable antivirus or firewall software to check if they're blocking Chromedriver.
• If this resolves the issue, add exceptions for chrome.exe, chromedriver.exe, and Automation Anywhere processes in your security software.

   Install Dependencies:

• Ensure Microsoft Visual C++ Redistributable (2015 or later) is installed, as Chromedriver requires it. Download it from the Microsoft website if missing.

6. Check Node Manager Logs for More Details

• The log you provided (Node_manager.log) indicates the failure but lacks detailed Chromedriver logs.

      Check for additional logs:

• Look in C:\ProgramData\AutomationAnywhere\BotRunner\Logs for other log files, such as Bot_Launcher.log

Contact automation anywhere through customer portal if issue persists