Hi

I just noticed that the Start Browser command is throwing an error in WDG Automation Studio 20.10.1: "unknown error: cannot find Chrome binary"
After some investigation, since Chrome 85, Chrome is using "Program Files" as the Installation folder and no longer "Program Files (x86)".
Temporary workaround is to create a symbolic link.


------------------------------
nordine
------------------------------

Thanks, Nordine for finding and diagnosing the problem!   I tried to reproduce this by updating to the latest version of Chrome but I could not reproduce this, so I am curious why it broke.   Did you restart WDG studio after upgrading Chrome?

------------------------------
NIGEL CROWTHER
------------------------------

Hi Nigel

I should have mentioned it, but I only had this problem on a freshly installed virtual machine. On my personal development workstation, I didn't had the issue although I also use the latest Chrome release. So I guess that a Chrome update still uses "Program Files (x86)" but a new install uses "Program Files".

------------------------------
nordine vandezande
------------------------------

Original Message:
Sent: Tue November 10, 2020 04:01 AM
From: NIGEL CROWTHER
Subject: WDG Automation: Error with Start Browser command

Thanks, Nordine for finding and diagnosing the problem!   I tried to reproduce this by updating to the latest version of Chrome but I could not reproduce this, so I am curious why it broke.   Did you restart WDG studio after upgrading Chrome?

------------------------------
NIGEL CROWTHER
------------------------------

Ah, so it may be a VM issue.   I will notify the WDG labs.  Thanks!

------------------------------
NIGEL CROWTHER
------------------------------

Original Message:
Sent: Tue November 10, 2020 04:11 AM
From: nordine vandezande
Subject: WDG Automation: Error with Start Browser command

Hi Nigel

I should have mentioned it, but I only had this problem on a freshly installed virtual machine. On my personal development workstation, I didn't had the issue although I also use the latest Chrome release. So I guess that a Chrome update still uses "Program Files (x86)" but a new install uses "Program Files".

------------------------------
nordine vandezande
------------------------------


Original Message:
Sent: Tue November 10, 2020 04:01 AM
From: NIGEL CROWTHER
Subject: WDG Automation: Error with Start Browser command

Thanks, Nordine for finding and diagnosing the problem!   I tried to reproduce this by updating to the latest version of Chrome but I could not reproduce this, so I am curious why it broke.   Did you restart WDG studio after upgrading Chrome?

------------------------------
NIGEL CROWTHER

I am not sure that is a VM issue because my development workstation is also a VM. It looks like it is more a 'update Chrome' vs 'new install of Chrome' issue.

------------------------------
nordine vandezande
------------------------------

Original Message:
Sent: Tue November 10, 2020 04:17 AM
From: NIGEL CROWTHER
Subject: WDG Automation: Error with Start Browser command

Ah, so it may be a VM issue.   I will notify the WDG labs.  Thanks!

------------------------------
NIGEL CROWTHER
------------------------------


Original Message:
Sent: Tue November 10, 2020 04:11 AM
From: nordine vandezande
Subject: WDG Automation: Error with Start Browser command

Hi Nigel

I should have mentioned it, but I only had this problem on a freshly installed virtual machine. On my personal development workstation, I didn't had the issue although I also use the latest Chrome release. So I guess that a Chrome update still uses "Program Files (x86)" but a new install uses "Program Files".

------------------------------
nordine vandezande


Original Message:
Sent: Tue November 10, 2020 04:01 AM
From: NIGEL CROWTHER
Subject: WDG Automation: Error with Start Browser command

Thanks, Nordine for finding and diagnosing the problem!   I tried to reproduce this by updating to the latest version of Chrome but I could not reproduce this, so I am curious why it broke.   Did you restart WDG studio after upgrading Chrome?

------------------------------
NIGEL CROWTHER

Hi Nordine!

You are correct. The issue is that the Studio's webStart command, when configured to use Chrome, is looking from Chrome from wrong installation folder. This should be fixed in next release though.

------------------------------
Jukka Juselius
Senior Solution Architect - IBM EMEA
WDG Automation Program Lead for EMEA
IBM Digital Business Automation
------------------------------

Original Message:
Sent: Tue November 10, 2020 04:22 AM
From: nordine vandezande
Subject: WDG Automation: Error with Start Browser command

I am not sure that is a VM issue because my development workstation is also a VM. It looks like it is more a 'update Chrome' vs 'new install of Chrome' issue.

------------------------------
nordine vandezande
------------------------------


Original Message:
Sent: Tue November 10, 2020 04:17 AM
From: NIGEL CROWTHER
Subject: WDG Automation: Error with Start Browser command

Ah, so it may be a VM issue.   I will notify the WDG labs.  Thanks!

------------------------------
NIGEL CROWTHER


Original Message:
Sent: Tue November 10, 2020 04:11 AM
From: nordine vandezande
Subject: WDG Automation: Error with Start Browser command

Hi Nigel

I should have mentioned it, but I only had this problem on a freshly installed virtual machine. On my personal development workstation, I didn't had the issue although I also use the latest Chrome release. So I guess that a Chrome update still uses "Program Files (x86)" but a new install uses "Program Files".

------------------------------
nordine vandezande


Original Message:
Sent: Tue November 10, 2020 04:01 AM
From: NIGEL CROWTHER
Subject: WDG Automation: Error with Start Browser command

Thanks, Nordine for finding and diagnosing the problem!   I tried to reproduce this by updating to the latest version of Chrome but I could not reproduce this, so I am curious why it broke.   Did you restart WDG studio after upgrading Chrome?

------------------------------
NIGEL CROWTHER