Protractor gives "Unable to start a WebDriver session" error

19,892

According to the relevant github issue, the problem is that chromedriver cannot find chrome browser executeable - on different operating systems it searches for it in different places.

You need to either have chrome installed where chromedriver expects it to be, or specify the path to the chrome executeable in the binary setting:

capabilities: {
    "browserName": "chrome",
    "chromeOptions": {
        binary: "D:/Program Files/Chrome/chrome.exe",
        args: [],
        extensions: [],
    }
},
Share:
19,892

Related videos on Youtube

cgsd
Author by

cgsd

Updated on June 18, 2022

Comments

  • cgsd
    cgsd about 2 years

    I already have started a server with webdriver-manager start, but I get this error when I try to run protractor:

    Using the selenium server at http://127.0.0.1:4444/wd/hub
    [launcher] Running 1 instances of WebDriver
    ERROR - Unable to start a WebDriver session.
    
    C:\...\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\atoms\error.js:113
      var template = new Error(this.message);
                     ^
    UnknownError: unknown error: cannot find Chrome binary
    

    My config file looks like this:

    exports.config = {
        specs: [
            'test/*.js'
        ],
    
        capabilities: {
            'browserName': 'chrome'
        },
        seleniumAddress: 'http://127.0.0.1:4444/wd/hub'
    
    };
    

    I have also tried pointing to the binary in the capabilities object as well as adding chromeDriver and seleniumServerJar keys to no avail. Any ideas?

  • cgsd
    cgsd over 9 years
    Thanks! I was trying to put "binary" a level down inside "capabilities" ... didn't know it should have been in "chromeOptions"