Web Automation failed to start

FATAL  - com.automationanywhere.botcommand.webautomation.StartSessionWebAutomationCommand {deploymentId=, traceId=} - execute(StartSessionWebAutomationCommand.java:142) - Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure. org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.

Also

Caused by: org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start.
Build info: version: '4.0.0-beta-2', revision: '4ec0cfc112'
System info: host: 'xxx', ip: 'xxx', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '11.0.15.0.101'
Driver info: driver.version: ChromeDriver
    at org.openqa.selenium.remote.service.DriverService.start(DriverService.java:224) ~[WebAutomation-4.0.10-20220518-124540.jar:?]
    at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:86) ~[WebAutomation-4.0.10-20220518-124540.jar:?]
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:620) ~[WebAutomation-4.0.10-20220518-124540.jar:?]

Hi @Murad ADNOC 

Try below steps and let us know if that helps,

1. Can you install latest chrome driver which is compatible with your chrome version using below link, chromedriver_win32.zip

https://chromedriver.storage.googleapis.com/index.html?path=108.0.5359.71/

2. Unzip the Zip file
3. Pass the chromedriver.exe path under WebDriver path in Web Automation : Start Session command
4. The start  session will look like this:

5. Give a try again

Hi @ChanduMohammad ,

Thank you very much for your advise, the provided steps are already applied but still we are getting an error while web automation session starting,

Hi @AhmadJazmawi & @Murad ADNOC ,

Please check for the C:\ProgramData\AutomationAnywhere\BotRunner\Logs\python3wrapper.log, which may answer what is going on. If you don't see that file, then open Node_Manager.log in that same folder.