Prerequisites

Ensure the Automation Anywhere Google Chrome extension you are using corresponds with the Recorder package version in your bots. See Google Chrome browser extension requirements.

To configure your system to run the Google Chrome extension, choose the scenario that applies to you and follow the steps.

Recorder package version 2.0.9 or later:

Verify that Google Chrome extension version 1.1.0.1 or higher is installed and enabled.
To install the extension, see Version 1.1.0.1 or later.
Open the Windows registry to the Google Chrome browser agent: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts\automation.bot.browseragent
Verify that the registry entry points to the Automation 360 Bot Agent installation directory: C:\Program Files\Automation Anywhere\Bot Agent\AABrowserAgent\AAChromeAgentManifest.json
If this configuration is missing, reinstall the Bot Agent.

Recorder package version 2.0.6, 2.0.7, or 2.0.8 (for Version A2019.16 or earlier)

Open the Windows registry to the Google Chrome browser agent: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts\automation.chrome.agent
Verify that the registry entry points to the Automation 360 global cache: C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources\<Recorder package version>\AAChromeAgentManifest.json
For example, C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources\2.0.6-20200626-193519-1bd6fceb-b036-4202-9932-4dc18349bd5c\AAChromeAgentManifest.json
If this configuration is missing, do the following steps as an admin:
1. Open the Automation 360 global cache: C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources\<Recorder package version>
2. Run the install.ps1 file.
3. Repeat steps 2 and 3 to verify the registry entry is updated.

Recorder package version 2.0.5 or earlier, and never installed Automation Anywhere Enterprise Version 11.3 or later

Прим.: Use latest Recorder package version available in your Control Room.

Verify that Google Chrome extension version 11 or 12 is installed and enabled.
To install the extension, see Version 11 or 12.
Open the Windows registry to the Google Chrome browser agent: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts\automation.chrome.agent
Verify that the registry entry points to the Automation 360 global cache: C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources\<Recorder package version>\AAChromeAgentManifest.json
For example, C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources\2.0.5-20200626-193519-1bd6fceb-b036-4202-9932-4dc18349bd5c\AAChromeAgentManifest.json
If this configuration is missing, do the following steps as an admin:
1. Open the Automation 360 global cache: C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources\<Recorder package version>
2. Run the install.ps1 file.
3. Repeat steps 2 and 3 to verify the registry entry is updated.
Verify that the browser agent Automation.BrowserAgent.exe is running with the Google Chrome extension installed and enabled.
If this configuration is missing, restart Google Chrome. Either disable and enable the Google Chrome extension, or close all Google Chrome browser tabs and reopen a new window.

Recorder package version 2.0.5 or earlier, and installed Automation Anywhere Enterprise Version 11.3 or later

Verify that Google Chrome extension version 11 or 12 is installed and enabled.
To install the extension, see Version 11 or 12.
Open the Windows registry to the Google Chrome browser agent: Computer\HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\automation.chrome.agent
- If the above key is available, disable the Google Chrome plug-in version 11.x and enable the Google Chrome plug-in version 12.x.
- If the above key is not available, disable the Google Chrome plug-in version 12.x and enable the Google Chrome plug-in version 11.x.
Restart Google Chrome. Either disable and enable the Google Chrome extension, or close all Google Chrome browser tabs and reopen a new window.
Verify that the browser agent Automation.BrowserAgent.exe is running with the Google Chrome extension installed and enabled.

Automation Anywhere Enterprise Version 11.3 or later is uninstalled

Uninstalling the Enterprise Client does not remove the Google Chrome extension and registry entries. To remove them manually, do these steps:

Disable Google Chrome extension 12.x.
Install and enable Google Chrome extension 11.x.
In the Windows registry editor, remove the following key: Computer\HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\automation.chrome.agent
Open the Windows registry to the Google Chrome browser agent: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts\automation.chrome.agent
Verify that the registry entry points to the Automation 360 global cache: C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources\<Recorder package version>\AAChromeAgentManifest.json
For example, C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources\2.0.6-20200626-193519-1bd6fceb-b036-4202-9932-4dc18349bd5c\AAChromeAgentManifest.json
Restart Google Chrome. Either disable and enable the Google Chrome extension, or close all Google Chrome browser tabs and reopen a new window.

Google Chrome extension installed in Microsoft Edge

Although Microsoft Edge browser settings allow extensions from the Chrome Web Store, we recommend that you do not install the Google Chrome extension in the Microsoft Edge browser. Installing it causes recording and runtime errors in bots that interact with the Google Chrome browser. Even if you did not manually install the Google Chrome extension, the auto-sync settings in the Microsoft Edge browser might have automatically installed the extension.

Unable to view Google Chrome extension in offline mode

Drag the file ChromeExtension.crx to the Google Chrome extension tab. This file is available in the same path where the Automation.BrowserAgent.exe file is available.
Enable the Automation 360 Google Chrome extension.
If the Google Chrome extension is still not visible:
1. Verify if the registry entry automation.chrome.agent is available in the path Computer\HKEY_CURRENT_USER.
  If it is not available, create the registry in the following path: Computer\HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\automation.chrome.agent
  This entry should have the same path as the entry: Computer\HKEY_LOCAL_MACHINE\Software\Google\Chrome\NativeMessagingHosts\automation.chrome.agent
2. Go to the path Computer\HKEY_LOCAL_MACHINE\Software\Google\Chrome\Extensions.
  For the 11.1.0.0 Automation 360 Google Chrome extension ID jjpdebaihkangkfpbgefmnnlafkahebn, create a new string with the name path.
  The value of the string will be the path of the ChromeExtension.crx, which is available in the same folder where the AAChromeAgentManifest.json file is available.
  For example, add the entry C:\ProgramData\AutomationAnywhere\GlobalCache\embedded-resources\2.0.5-20200511-172840-1825fd43-19bc-4dd2-ac56-53a2aed4b0e4\ChromeExtension.crx in the following locations:
  - Computer\HKEY_LOCAL_MACHINE\Software\Google\Chrome\Extensions(ExtensionID)
  - Computer\HKEY_CURRENT_USER\Software\Google\Chrome\Extensions(ExtensionID)
3. Restart Google Chrome. Either disable and enable the Google Chrome extension, or close all Google Chrome browser tabs and reopen a new window.

Google Chrome extension troubleshooting

Automation 360