Errors launching or spying with Chrome browser

[Michael Sunderlin]

I am getting two different errors trying to launch or spy items w/the Chrome browser. On the server I cannot open the Chrome browser with the spy tool and it throws this error:

Error starting browser: no such session
(Driver info: chromedriver=2.24.417431...)

On one of the agent machines I can launch the Chrome browser with the spy tool but when I click on the magnifying glass to spy out a control I get this error:

Error getting html page from browser: no such session

(Driver info: chromedriver=2.24.417431...)

Both of the errors had more details but not sure they're helpful. 

My setup:
1. both computers have this version of Chrome: 126.0.6478.115
2. on the "Scripts" tab, the ivy.xml file had 3.4.0 for the version of selenium for java, server, and support

What I did to try to fix:
1. Downloaded latest chromedriver.exe I could find (version 126.0.6478.63), renamed "chromedriver.exe" on the "Scripts" tab under the "bin" folder to "oldchromedriver.exe" and uploaded the new one to the "bin" folder then restarted both the Agent and RedwoodHQ server
2. I tried changing the version from 3.4.0 to "latest.release" in the ivy.xml file then saved and did a build on the scripts but that didn't fix it. I even tried restarting RedwoodHQ and the Agent

I don't understand why the errors mention chromedriver=2.24.417431 when I tried several times to upload the latest driver. I also am not sure if there are other copies of old chromedriver files hanging around and not sure how or if I should delete those.

Any assistance would be greatly appreciated because I cannot automate any browser interactions now. I would be willing to use a different browser, if that was the only solution but I also tried Firefox and it wasn't working either.

Thanks!

[Michael Sunderlin]

Can anyone provide any guidance on this?

Maybe nobody uses RedwoodHQ anymore?

[Michael Sunderlin]

I got it working. I basically followed instructions here: https://groups.google.com/g/primatest-automation/c/g2S33tKtPJg/m/8tiiqqwuAgAJ

Wish I had the right instructions for doing this. I've seen various different suggestions on how to do this on this forum but nothing that said this is the ultimate right way to do it.

Anyways, Chrome is now working for me.