Skip to main content
  • Home
  • Forums
  • Developers Forum
  • Chrome Browser does not open in Unattended mode but works fine when viewing it live on the Unattended device

Bot executes fine and opens Chrome Browser as the default browser in the Virtual Machine when viewing the deployment live. However, when scheduling the deployment unattended to the same VM, it is failing to open the chrome browser. 

Actions taken:

  1. Browser and Recorder packages are up to date
  2. I’ve tried changing the deployment type from Regular to RDP (did not resolve issue)
  3. I verified that the chrome browser is up to date and the AA360 extension
  4. I made sure the VM has google chrome as the default browser to open
  5. I’ve restarted the VM several times
  6. I’ve unpaired/paired VM device in the control room (including uninstalling/re-installing the bot agent)

Please help determine what could be the issue. Again, the Bot executes flawlessly if I manually log into the VM and watch it. 

Do you get any error messages? Are you using the same user account when you manually log in, and for the unattended log in? If you use a different user account for the unattended login, you will need to log in as the unattended user and enable the Chrome extension.

@joe_zuniga  No, I’m not getting an error message from the control room itself but If Identifying the error because I’m using the Try/Catch error handler. Yes, I’m using the same user account for the unattended device. The chrome extension is enabled.

Hi @aadewale86 ,

It’s possible that the same user is logged into the server multiple times, once by the bot and another time manually. This can occasionally happen.

  • Check Active Users: Use Task Manager (Ctrl + Shift + Esc), go to the “Users” tab to see all signed-in users and their resource usage.
  • Concurrency Control: Ensure only one session per user is active.
  • To ensure that bot uses Google Chrome instead of the default browser, you can set Chrome as the browser to open.
  • Check the auto login settings on the Edit Device Configuration page.

 

 

@DK 964 I’ve checked for Active Users, no multiples found. Yes, it is one session per user active. For some reason the bot will fail when using the Google Chrome option instead of default browser (same issue occurred when I did my build in DEV environment). I’ve had to make sure that google chrome is the default browser in windows in bot DEV/UAT environments. This is the error message I get from the CR when using chrome as the browser option to open:

This may be due to the following reason: Unable to find the browser. Verify that a browser is installed and try again.

Hi @aadewale86,

Check the chrome installation path in both environments? It's should be same.

@DK 964 The installation path in both environments are there but different paths

@aadewale86, Move the chrome.exe to working path? Or you can open chrome using open program file as a work around.

Reply


Terms & ConditionsCookie settings