Protractor: Protractor fails with error code 199 on WebDriver.createSession()

Created on 20 Jun 2017  路  41Comments  路  Source: angular/protractor

Hi guys. I am using angular-cli and protractor fails to run my tests. I am sitting behind a corporate proxy which I add as a param when updating the webdriver.
This is the output I get:

$ ./node_modules/.bin/webdriver-manager update --proxy=proxy_url_here
[15:11:28] I/update - selenium standalone: file exists C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\protractor\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.4.0.jar
[15:11:28] I/update - selenium standalone: selenium-server-standalone-3.4.0.jar up to date
[15:11:28] E/downloader - undefined
[15:11:28] I/update - geckodriver: file exists C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\protractor\node_modules\webdriver-manager\selenium\geckodriver-v0.17.0.zip
[15:11:28] I/update - geckodriver: unzipping geckodriver-v0.17.0.zip
(node:12156) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Invalid filename
[15:11:28] I/update - chromedriver: unzipping chromedriver_2.30.zip

$ ./node_modules/.bin/protractor ./protractor.conf.js
[15:26:13] I/launcher - Running 1 instances of WebDriver
[15:26:13] I/direct - Using ChromeDriver directly...
[15:26:15] E/launcher - spawn UNKNOWN
[15:26:15] E/launcher - Error: spawn UNKNOWN
    at exports._errnoException (util.js:1022:11)
    at ChildProcess.spawn (internal/child_process.js:313:11)
    at Object.exports.spawn (child_process.js:380:9)
    at exec (C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\selenium-webdriver\io\exec.js:116:27)
    at resolveCommandLineFlags.then.args (C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\selenium-webdriver\remote\index.js:219:25)
    at process._tickCallback (internal/process/next_tick.js:103:7)
From: Task: WebDriver.createSession()
    at Function.createSession (C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\selenium-webdriver\lib\webdriver.js:777:24)
    at Function.createSession (C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\selenium-webdriver\chrome.js:709:29)
    at Direct.getNewDriver (C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\protractor\lib\driverProviders\direct.ts:90:25)
    at Runner.createBrowser (C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\protractor\lib\runner.ts:225:39)
    at q.then.then (C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\protractor\lib\runner.ts:391:27)
    at _fulfilled (C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\protractor\node_modules\q\q.js:834:54)
    at self.promiseDispatch.done (C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\protractor\node_modules\q\q.js:863:30)
    at Promise.promise.promiseDispatch (C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\protractor\node_modules\q\q.js:796:13)
    at C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\protractor\node_modules\q\q.js:556:49
    at runSingle (C:\Users\g8uibf\Projects\mbsportal-ui\node_modules\protractor\node_modules\q\q.js:137:13)
[15:26:15] E/launcher - Process exited with error code 199
  • Node Version: v6.9.5
  • Protractor Version: 5.1.2
  • Angular Version: 4
  • Browser(s): chrome 58
  • Operating System and Version Windows 10
  • Your protractor configuration file
const { SpecReporter } = require('jasmine-spec-reporter');

exports.config = {
  allScriptsTimeout: 11000,
  specs: [
    './e2e/**/*.e2e-spec.ts'
  ],
  capabilities: {
    'browserName': 'chrome'
  },
  directConnect: true,
  baseUrl: 'http://localhost:8080/',
  framework: 'jasmine',
  jasmineNodeOpts: {
    showColors: true,
    defaultTimeoutInterval: 30000,
    print: function() {}
  },
  onPrepare() {
    require('ts-node').register({
      project: 'e2e/tsconfig.e2e.json'
    });
    jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true } }));
  }
};

Thank you for the help in advance!

picture evgenyfedorenko
👍13

Most helpful comment

For those still have this issue, after checking the official FAQ, I fixed the issue by adding the flag --no-sandbox for Chrome 66.

picture alexcheng1982 on 7 May 2018
👍8 🚀1 ❤1 🎉1

All 41 comments

I have the same issue on my CI environment when I want to run e2e using angula cli.

Node Version: v8.1.3
Protractor Version: 5.1.2
Angular Version: 4.2.5
Browser(s): chrome 59.0.3071.115
Operating System: RedHat 7.3

Protractor configuration file:

const {SpecReporter} = require('jasmine-spec-reporter');

exports.config = {
  allScriptsTimeout: 11000,
  specs: [
    './e2e/**/*.e2e-spec.ts'
  ],
  capabilities: {
    browserName: 'chrome',
    chromeOptions: {
      args: ["--headless", "--disable-gpu", "--window-size=800x600"]
    }
  },
  directConnect: true,
  baseUrl: 'http://localhost:4200/',
  framework: 'jasmine',
  jasmineNodeOpts: {
    showColors: true,
    defaultTimeoutInterval: 30000,
    print: function () {
    }
  },
  onPrepare() {
    require('ts-node').register({
      project: 'e2e/tsconfig.e2e.json'
    });
    jasmine.getEnv().addReporter(new SpecReporter({spec: {displayStacktrace: true}}));
  }
};

My error:

** NG Live Development Server is listening on localhost:49152, open your browser on http://localhost:49152 **
(node:24932) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
Hash: 7d2af81fa7cb758e9eb3
Time: 18023ms
chunk    {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 235 kB {4} [initial] [rendered]
chunk    {1} main.bundle.js, main.bundle.js.map (main) 474 kB {3} [initial] [rendered]
chunk    {2} styles.bundle.js, styles.bundle.js.map (styles) 231 kB {4} [initial] [rendered]
chunk    {3} vendor.bundle.js, vendor.bundle.js.map (vendor) 4.17 MB [initial] [rendered]
chunk    {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]
webpack: Compiled successfully.
[08:24:23] I/update - chromedriver: file exists /var/lib/go-agent/pipelines/app-user-manager/node_modules/webdriver-manager/selenium/chromedriver_2.30.zip
[08:24:23] I/update - chromedriver: unzipping chromedriver_2.30.zip
[08:24:24] I/update - chromedriver: setting permissions to 0755 for /var/lib/go-agent/pipelines/app-user-manager/node_modules/webdriver-manager/selenium/chromedriver_2.30
[08:24:24] I/update - chromedriver: chromedriver_2.30 up to date
[08:24:24] I/launcher - Running 1 instances of WebDriver
[08:24:24] I/direct - Using ChromeDriver directly...
[08:25:24] E/launcher - unknown error: Chrome failed to start: crashed
  (Driver info: chromedriver=2.30.477691 (6ee44a7247c639c0703f291d320bdf05c1531b57),platform=Linux 3.10.0-514.el7.x86_64 x86_64)
[08:25:24] E/launcher - WebDriverError: unknown error: Chrome failed to start: crashed
  (Driver info: chromedriver=2.30.477691 (6ee44a7247c639c0703f291d320bdf05c1531b57),platform=Linux 3.10.0-514.el7.x86_64 x86_64)
    at Object.checkLegacyResponse (/var/lib/go-agent/pipelines/app-user-manager/node_modules/selenium-webdriver/lib/error.js:505:15)
    at parseHttpResponse (/var/lib/go-agent/pipelines/app-user-manager/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response (/var/lib/go-agent/pipelines/app-user-manager/node_modules/selenium-webdriver/lib/http.js:440:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:169:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/var/lib/go-agent/pipelines/app-user-manager/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
    at Function.createSession (/var/lib/go-agent/pipelines/app-user-manager/node_modules/selenium-webdriver/chrome.js:709:29)
    at Direct.getNewDriver (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/built/driverProviders/direct.js:77:33)
    at Runner.createBrowser (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/built/runner.js:195:43)
    at q.then.then (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/built/runner.js:339:29)
    at _fulfilled (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:796:13)
    at /var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:556:49
    at runSingle (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:137:13)
    at flush (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:95:7)
    at process._tickCallback (internal/process/next_tick.js:161:9)
[08:25:24] E/launcher - Process exited with error code 199
error Command failed with exit code 199.

It works locally on a windows 10 env !

jogelin picture jogelin on 4 Jul 2017

@jogelin basically I had an issue that my corporate windows machine was blocking chrome driver which I downloaded from the public source. Our security team provided me with our internal chrome driver which I was able to start, so this was entirely local issue on my machine.

evgenyfedorenko picture evgenyfedorenko on 4 Jul 2017

I have same issue +1.

chriseugenerodriguez picture chriseugenerodriguez on 5 Jul 2017

@jogelin ,

What happens if you don't use directConnect:true but a local webdriver manager?

wswebcreation picture wswebcreation on 11 Jul 2017

@premiumwd

Wha tissue do you have, the same issue as mentioned by @deli6z or by @jogelin ?

wswebcreation picture wswebcreation on 11 Jul 2017

@deli6z ,

Is your issue solved then and can we close it?

wswebcreation picture wswebcreation on 11 Jul 2017

@wswebcreation this is the code i get

[09:37:13] I/update - chromedriver: file exists H:\d\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_2.30.zip
[09:37:13] I/update - chromedriver: unzipping chromedriver_2.30.zip
[09:37:13] I/update - chromedriver: chromedriver_2.30.exe up to date
[09:37:14] I/launcher - Running 1 instances of WebDriver
[09:37:14] I/direct - Using ChromeDriver directly...
[09:37:15] E/launcher - Server terminated early with status 1
[09:37:15] E/launcher - Error: Server terminated early with status 1
    at earlyTermination.catch.e (H:\d\node_modules\selenium-webdriver\remote\index.js:252:52)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:169:7)
From: Task: WebDriver.createSession()
    at Function.createSession (H:\d\node_modules\selenium-webdriver\lib\webdriver.js:777:24)
    at Function.createSession (H:\d\node_modules\selenium-webdriver\chrome.js:709:29)
    at Direct.getNewDriver (H:\d\node_modules\protractor\built\driverProviders\direct.js:77:33)
    at Runner.createBrowser (H:\d\node_modules\protractor\built\runner.js:195:43)
    at q.then.then (H:\d\node_modules\protractor\built\runner.js:339:29)
    at _fulfilled (H:\d\node_modules\protractor\node_modules\q\q.js:834:54)
    at self.promiseDispatch.done (H:\d\node_modules\protractor\node_modules\q\q.js:863:30)
    at Promise.promise.promiseDispatch (H:\d\node_modules\protractor\node_modules\q\q.js:796:13)
    at H:\d\node_modules\protractor\node_modules\q\q.js:556:49
    at runSingle (H:\d\node_modules\protractor\node_modules\q\q.js:137:13)
    at flush (H:\d\node_modules\protractor\node_modules\q\q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:95:7)
    at process._tickCallback (internal/process/next_tick.js:161:9)
[09:37:15] E/launcher - Process exited with error code 199
chriseugenerodriguez picture chriseugenerodriguez on 11 Jul 2017

@premiumwd

Some questions because debugging is becoming hard this way:

  • are you using Jasmine, Mocha, CucumberJS
  • which OS
  • which version of Chrome
  • which version of NodeJS
  • have you also tried it with a local webserver?
wswebcreation picture wswebcreation on 11 Jul 2017

@wswebcreation

Chrome 2.3
Node 8.1
Jasmine

protractor.conf.js

// Protractor configuration file, see link for more information
// https://github.com/angular/protractor/blob/master/lib/config.ts

const { SpecReporter } = require('jasmine-spec-reporter');

exports.config = {
  allScriptsTimeout: 11000,
  specs: [
    './e2e/**/*.e2e-spec.ts'
  ],
 capabilities: {
    browserName: 'chrome',
    chromeOptions: {
      args: ["--headless", "--disable-gpu", "--window-size=800x600"]
    }
  },
  chromeOnly: true,
  directConnect: true,
  baseUrl: 'http://localhost:4200/',
  framework: 'jasmine',
  jasmineNodeOpts: {
    showColors: true,
    defaultTimeoutInterval: 30000,
    print: function () {
    }
  },
  onPrepare() {
    require('ts-node').register({
      project: 'e2e/tsconfig.e2e.json'
    });
    jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true } }));
  }
};
chriseugenerodriguez picture chriseugenerodriguez on 11 Jul 2017

And on what OS? Did you also read this post. You are also using --headless. Did you also try it on your machine with just the example project?

wswebcreation picture wswebcreation on 11 Jul 2017

Windows 10. I didn't try example project, but did it with a new angular ng new project and still same issue.

chriseugenerodriguez picture chriseugenerodriguez on 11 Jul 2017

I don't have Windows 10, so I can't test it here, but what if you remove the headless and first check if that works? If not, then remove headless and check if you can use it with a local webdriver instead of directConnect

wswebcreation picture wswebcreation on 11 Jul 2017

@wswebcreation now i get error code 135

[12:57:30] I/file_manager - creating folder H:\d\node_modules\protractor\node_modules\webdriver-manager\selenium
[12:57:32] I/update - chromedriver: unzipping chromedriver_2.30.zip
[12:57:34] I/launcher - Running 1 instances of WebDriver
[12:57:34] E/local - Error code: 135
[12:57:34] E/local - Error message: No update-config.json found. Run 'webdriver-manager update' to download binaries.
[12:57:34] E/local - Error: No update-config.json found. Run 'webdriver-manager update' to download binaries.
    at Local.addDefaultBinaryLocs_ (H:\d\node_modules\protractor\built\driverProviders\local.js:41:23)
    at Local.setupDriverEnv (H:\d\node_modules\protractor\built\driverProviders\local.js:82:14)
    at Local.setupEnv (H:\d\node_modules\protractor\built\driverProviders\driverProvider.js:111:34)
    at q.then (H:\d\node_modules\protractor\built\runner.js:335:41)
    at _fulfilled (H:\d\node_modules\protractor\node_modules\q\q.js:834:54)
    at self.promiseDispatch.done (H:\d\node_modules\protractor\node_modules\q\q.js:863:30)
    at Promise.promise.promiseDispatch (H:\d\node_modules\protractor\node_modules\q\q.js:796:13)
    at H:\d\node_modules\protractor\node_modules\q\q.js:857:14
    at runSingle (H:\d\node_modules\protractor\node_modules\q\q.js:137:13)
    at flush (H:\d\node_modules\protractor\node_modules\q\q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:95:7)
    at process._tickCallback (internal/process/next_tick.js:161:9)
[12:57:34] E/launcher - Process exited with error code 135
chriseugenerodriguez picture chriseugenerodriguez on 11 Jul 2017

Can you please first do a clean install of all the node_modules and try it again?

wswebcreation picture wswebcreation on 12 Jul 2017

I am behind a firewall, could that be issue?

chriseugenerodriguez picture chriseugenerodriguez on 12 Jul 2017

I got the same issue after chrome was updated to v 59.0.3071.115

v-vostretsov picture v-vostretsov on 12 Jul 2017

I am getting this error now. E/launcher - EACCES connect EACCES 127.0.0.1:4444

const { SpecReporter } = require('jasmine-spec-reporter');

exports.config = {
  allScriptsTimeout: 11000,
  specs: [
    './e2e/**/*.e2e-spec.ts'
  ],
  capabilities: {
    'browserName': 'firefox'
  },
  //directConnect: true,
  baseUrl: 'http://localhost:4444/',
  framework: 'jasmine',
  seleniumAddress: 'http://localhost:4444/wd/hub',
  jasmineNodeOpts: {
    showColors: true,
    defaultTimeoutInterval: 30000,
    print: function () {
    }
  },
  onPrepare() {
    require('ts-node').register({
      project: 'e2e/tsconfig.e2e.json'
    });
    jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true } }));
  }
};
chriseugenerodriguez picture chriseugenerodriguez on 12 Jul 2017
👍1

Hmm, not sure what to say - we can't reproduce the problem. It's an issue with chromedriver, chrome, the selenium standalone server or your local machine (corporate configuration). Can you try to do a clean install of protractor (do a git clone of protractor) and run the example-project and see what happens.

I'm going to close this issue sine it's not a general problem, but we can keep discussing here.

wswebcreation picture wswebcreation on 13 Jul 2017

The issue was reproduced with Chrome 59, protractor 5.1.2, chromedriver 2.30, Windows 10.
After removing all latest Windows July updates the issue disappeared. Maybe it helps for somebody.

Pogosov picture Pogosov on 21 Jul 2017
👍2

+1
Solved this issue by downgrading chromedriver to 2.29

v-vostretsov picture v-vostretsov on 21 Jul 2017

Same for me, my issue was solved by downgrading chromedriver to 2.29.

I used the solution of @rkrisztian from the issue #98 to fix my chrome driver version:

package.json

    "preci:e2e": "webdriver-manager update --versions.chrome=2.29",
    "ci:e2e": "ng e2e --progress false --config protractor.ci.conf.js --webdriver-update false"

protractor.ci.conf.js

const parentConfig = require('./protractor.conf').config;

exports.config = Object.assign(parentConfig, {
  capabilities: {
    browserName: 'chrome',
    chromeOptions: {
      args: ["--headless", "--disable-gpu", "--window-size=800x600"]
    }
  }
});

Chromedriver 2.31 still crash....

jogelin picture jogelin on 24 Jul 2017
👍2

I had the same issue and it was resolved by downgrading the chrome driver version (solution of @jogelin)

SaifJerbi picture SaifJerbi on 3 Aug 2017

And what "error code 199" means, after all?

...and "error code 135"?

What sense has "finding the solution", when you don't even know what is the problem?

edgarechm picture edgarechm on 3 Oct 2017

Downgrading a driver seems like a workaround rather than a fix?

Martinspire picture Martinspire on 16 Oct 2017

I have the same issue.

NodeJS : v6.11.4
NPM: v3.10.10
Chromium v57.0.2987.98 with headless option
Debian 8.8 (64-bit) (Docker)
Protractor 5.2.0

My protractor conf (pretty standard, just added headless) :

exports.config = {
  allScriptsTimeout: 18000,
  specs: [
    './e2e/**/*.e2e-spec.ts'
  ],
  capabilities: {
    'browserName': 'chrome',
    'chromeOptions': {
      // 'args': ['show-fps-counter=true', '--no-sandbox']
      'args': ['--headless', '--disable-gpu', '--window-size=800x600']
    },
  },
  directConnect: true,
  baseUrl: 'http://localhost:4201/',
  framework: 'jasmine',
  jasmineNodeOpts: {
    showColors: true,
    defaultTimeoutInterval: 30000,
    print: function () { }
  },
  beforeLaunch: function () {
    require('ts-node').register({
      project: 'e2e/tsconfig.e2e.json'
    });
  },
  onPrepare() {
    // Register jasmine library
    const jasmineReporters = require('jasmine-reporters');
    jasmine.getEnv().addReporter(
      // new SpecReporter({
      //   spec: { displayStacktrace: true }
      // }),
      new jasmineReporters.JUnitXmlReporter({
        savePath: 'test-output',
        filePrefix: 'ng-e2e-results',
        consolidateAll: true
      })
    );
  }
};

In my Docker container, I'm trying to execute my protractor tests with it : (without using a jenkins job yet)

  • My tests work locally on a Windows 7 with success.
  • chromium --headless --disable-gpu works fine, I just have the Multiple AudioManager instances warning displayed.
  • I've seen this issue as well : https://github.com/angular/protractor/issues/4403.
  • I'm running webdriver-manager update --proxy=$HTTP_PROXY --standalone=false --gecko=false in my dockerfile beforehand, grabbing effectively the chrome driver v2.3.3
  • Here is the result with ng e2e --wu=false 
webpack: Compiled successfully.
[17:33:42] I/launcher - Running 1 instances of WebDriver
[17:33:42] I/direct - Using ChromeDriver directly...
[17:33:42] E/launcher - Server terminated early with status 127
[17:33:42] E/launcher - Error: Server terminated early with status 127
    at Error (native)
    at earlyTermination.catch.e (/var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/selenium-webdriver/remote/index.js:252:52)
    at process._tickCallback (internal/process/next_tick.js:109:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/selenium-webdriver/lib/webdriver.js:769:24)
    at Function.createSession (/var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/selenium-webdriver/chrome.js:761:15)
    at Direct.getNewDriver (/var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/protractor/built/driverProviders/direct.js:77:33)
    at Runner.createBrowser (/var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/protractor/built/runner.js:195:43)
    at q.then.then (/var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/protractor/built/runner.js:339:29)
    at _fulfilled (/var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/protractor/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/protractor/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/protractor/node_modules/q/q.js:796:13)
    at /var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/protractor/node_modules/q/q.js:556:49
    at runSingle (/var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/protractor/node_modules/q/q.js:137:13)
    at flush (/var/jenkins_home/workspace/karma-test-CI2/frontend_proto/node_modules/protractor/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:73:7)
    at process._tickCallback (internal/process/next_tick.js:104:9)
[17:33:42] E/launcher - Process exited with error code 199

Still have no clue of what is going on and what I can do to correct this.

Tenmak picture Tenmak on 27 Oct 2017

I had the same issue. The problem is that I tried to start tests on firefox which was not installed on the computer

Art-auto picture Art-auto on 26 Nov 2017

add this line in protractor.config.js file:

ignoreUncaughtExceptions: true,

Jeeva772 picture Jeeva772 on 12 Dec 2017

In my case, chrome was not installed, installing helped: https://askubuntu.com/a/510186

anurbol picture anurbol on 11 Apr 2018

For those still have this issue, after checking the official FAQ, I fixed the issue by adding the flag --no-sandbox for Chrome 66.

alexcheng1982 picture alexcheng1982 on 7 May 2018
👍8 🚀1 ❤1 🎉1

@alexcheng1982 where to add --no-sandbox? can you please tell me . Thanx

amit-kumar88 picture amit-kumar88 on 28 Aug 2018

@amit-kumar88 In your protractor.conf.js: 

capabilities: {
    browserName: 'chrome',
    chromeOptions: {
      args: ['--no-sandbox']
    },
}
bogini picture bogini on 14 Sep 2018
👍2

Hi, While tryin to run conf.js using protractor, i am getting this error. can any one pls help me in solving this :

[11:44:34] I/launcher - Running 1 instances of WebDriver
[11:44:34] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
[11:44:34] E/launcher - unknown error: failed to write automation extension zip
(Driver info: chromedriver=2.42.591088 (7b2b2dca23cca0862f674758c9a3933e685c27d5),platform=Windows NT 10.0.17134 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 40 milliseconds
Build info: version: '3.14.0', revision: 'aacccce0', time: '2018-08-02T20:13:22.693Z'
Driver info: driver.version: unknown
[11:44:34] E/launcher - WebDriverError: unknown error: failed to write automation extension zip
(Driver info: chromedriver=2.42.591088 (7b2b2dca23cca0862f674758c9a3933e685c27d5),platform=Windows NT 10.0.17134 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 40 milliseconds
Build info: version: '3.14.0', revision: 'aacccce0', time: '2018-08-02T20:13:22.693Z'
Driver info: driver.version: unknown
at Object.checkLegacyResponse (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:546:15)
at parseHttpResponse (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13)
at doSend.then.response (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30)
at process._tickCallback (internal/process/next_tick.js:68:7)
From: Task: WebDriver.createSession()
at Function.createSession (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:769:24)
at Function.createSession (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\chrome.js:761:15)
at createDriver (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:170:33)
at Builder.build (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:626:16)
at Hosted.getNewDriver (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\built\driverProviders\driverProvider.js:53:33)
at Runner.createBrowser (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\built\runner.js:195:43)
at q.then.then (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\built\runner.js:339:29)
at _fulfilled (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:834:54)
at C:\Users\test\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:863:30
at Promise.promise.promiseDispatch (C:\Users\test\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:796:13)
[11:44:34] E/launcher - Process exited with error code 199

okvishnuk2 picture okvishnuk2 on 2 Oct 2018

@amit-kumar88 In your protractor.conf.js:

capabilities: {
    browserName: 'chrome',
    chromeOptions: {
      args: ['--no-sandbox']
    },
}

Ubuntu: 18

Worked Perfectly.

muthaka picture muthaka on 30 Jan 2020

Downgrade the node version to 11.15.0

GURUPRASADKP picture GURUPRASADKP on 15 Mar 2020

As I try to run this command, I'm getting this error

~/Documents/automation protractorcode$ protractor conf.js
[12:30:12] I/launcher - Running 1 instances of WebDriver
[12:30:12] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
[12:30:17] E/launcher - unknown error: Chrome failed to start: exited abnormally.
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'pyrios-Vostro-2420', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.3.0-59-generic', java.version: '11.0.7'
Driver info: driver.version: unknown
remote stacktrace: #0 0x5611abfb0579

[12:30:17] E/launcher - WebDriverError: unknown error: Chrome failed to start: exited abnormally.
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'pyrios-Vostro-2420', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.3.0-59-generic', java.version: '11.0.7'
Driver info: driver.version: unknown
remote stacktrace: #0 0x5611abfb0579 

at Object.checkLegacyResponse (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/error.js:546:15)
at parseHttpResponse (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/http.js:509:13)
at /usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/http.js:441:30
at processTicksAndRejections (internal/process/task_queues.js:97:5)

From: Task: WebDriver.createSession()
at Function.createSession (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver.js:769:24)
at Function.createSession (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/chrome.js:761:15)
at createDriver (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/index.js:170:33)
at Builder.build (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/index.js:626:16)
at Hosted.getNewDriver (/usr/local/lib/node_modules/protractor/built/driverProviders/driverProvider.js:53:33)
at Runner.createBrowser (/usr/local/lib/node_modules/protractor/built/runner.js:195:43)
at /usr/local/lib/node_modules/protractor/built/runner.js:339:29
at _fulfilled (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:834:54)
at /usr/local/lib/node_modules/protractor/node_modules/q/q.js:863:30
at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:796:13)

[12:30:17] E/launcher - Process exited with error code 199

npm=6.14.5
protractor =7.0.0
java JDK=11.0.7
nodejs=12.16.1
angular cLI= 9.1.0
jasmine=3.5.0
google chrome=78.0.3904.108
os linux x64

monalimng picture monalimng on 29 Jun 2020

I have the same issue on my CI environment when I want to run e2e using angula cli.

Node Version: v8.1.3
Protractor Version: 5.1.2
Angular Version: 4.2.5
Browser(s): chrome 59.0.3071.115
Operating System: RedHat 7.3

Protractor configuration file:

const {SpecReporter} = require('jasmine-spec-reporter');

exports.config = {
  allScriptsTimeout: 11000,
  specs: [
    './e2e/**/*.e2e-spec.ts'
  ],
  capabilities: {
    browserName: 'chrome',
    chromeOptions: {
      args: ["--headless", "--disable-gpu", "--window-size=800x600"]
    }
  },
  directConnect: true,
  baseUrl: 'http://localhost:4200/',
  framework: 'jasmine',
  jasmineNodeOpts: {
    showColors: true,
    defaultTimeoutInterval: 30000,
    print: function () {
    }
  },
  onPrepare() {
    require('ts-node').register({
      project: 'e2e/tsconfig.e2e.json'
    });
    jasmine.getEnv().addReporter(new SpecReporter({spec: {displayStacktrace: true}}));
  }
};

My error:

** NG Live Development Server is listening on localhost:49152, open your browser on http://localhost:49152 **
(node:24932) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
Hash: 7d2af81fa7cb758e9eb3
Time: 18023ms
chunk    {0} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 235 kB {4} [initial] [rendered]
chunk    {1} main.bundle.js, main.bundle.js.map (main) 474 kB {3} [initial] [rendered]
chunk    {2} styles.bundle.js, styles.bundle.js.map (styles) 231 kB {4} [initial] [rendered]
chunk    {3} vendor.bundle.js, vendor.bundle.js.map (vendor) 4.17 MB [initial] [rendered]
chunk    {4} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]
webpack: Compiled successfully.
[08:24:23] I/update - chromedriver: file exists /var/lib/go-agent/pipelines/app-user-manager/node_modules/webdriver-manager/selenium/chromedriver_2.30.zip
[08:24:23] I/update - chromedriver: unzipping chromedriver_2.30.zip
[08:24:24] I/update - chromedriver: setting permissions to 0755 for /var/lib/go-agent/pipelines/app-user-manager/node_modules/webdriver-manager/selenium/chromedriver_2.30
[08:24:24] I/update - chromedriver: chromedriver_2.30 up to date
[08:24:24] I/launcher - Running 1 instances of WebDriver
[08:24:24] I/direct - Using ChromeDriver directly...
[08:25:24] E/launcher - unknown error: Chrome failed to start: crashed
  (Driver info: chromedriver=2.30.477691 (6ee44a7247c639c0703f291d320bdf05c1531b57),platform=Linux 3.10.0-514.el7.x86_64 x86_64)
[08:25:24] E/launcher - WebDriverError: unknown error: Chrome failed to start: crashed
  (Driver info: chromedriver=2.30.477691 (6ee44a7247c639c0703f291d320bdf05c1531b57),platform=Linux 3.10.0-514.el7.x86_64 x86_64)
    at Object.checkLegacyResponse (/var/lib/go-agent/pipelines/app-user-manager/node_modules/selenium-webdriver/lib/error.js:505:15)
    at parseHttpResponse (/var/lib/go-agent/pipelines/app-user-manager/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response (/var/lib/go-agent/pipelines/app-user-manager/node_modules/selenium-webdriver/lib/http.js:440:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:169:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/var/lib/go-agent/pipelines/app-user-manager/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
    at Function.createSession (/var/lib/go-agent/pipelines/app-user-manager/node_modules/selenium-webdriver/chrome.js:709:29)
    at Direct.getNewDriver (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/built/driverProviders/direct.js:77:33)
    at Runner.createBrowser (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/built/runner.js:195:43)
    at q.then.then (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/built/runner.js:339:29)
    at _fulfilled (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:796:13)
    at /var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:556:49
    at runSingle (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:137:13)
    at flush (/var/lib/go-agent/pipelines/app-user-manager/node_modules/protractor/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:95:7)
    at process._tickCallback (internal/process/next_tick.js:161:9)
[08:25:24] E/launcher - Process exited with error code 199
error Command failed with exit code 199.

It works locally on a windows 10 env !

Is it working for you now?

chimeraTrijay picture chimeraTrijay on 1 Sep 2020

For those still have this issue, after checking the official FAQ, I fixed the issue by adding the flag --no-sandbox for Chrome 66.

Not working for Chrome 85

chimeraTrijay picture chimeraTrijay on 1 Sep 2020

I tried by setting flag --no-sandbox as suggested, but that did not work for chrome 84.0.4147.125. Kindly help to fix this issue as it is blocker for running tests

Also have set directConnect: true in config.js , tried with with different versions of chrome driver e.g ChromeDriver 84.0.4147.30,ChromeDriver 85.0.4183.87 and latest ChromeDriver 86.0.4240.22. But everything fails.

Note: I am behind corporate proxy , and was able to run webdriver-manager using proxy and also tried to set explicitly chromedriver path in config.js

Additional details: Using protractor 7.0.0 and node v10.16.0

H:\ProtractorPocDemo>protractor .\conf\configuration.js
Error :[17:43:50] I/launcher - Running 1 instances of WebDriver
[17:43:50] I/direct - Using ChromeDriver directly...
[17:43:51] E/launcher - Server terminated early with status 1
[17:43:51] E/launcher - Error: Server terminated early with status 1
at earlyTermination.catch.e (H:\ProtractorPocDemo\node_modules\selenium-webdriver\remote\index.js:252:52)
at process._tickCallback (internal/process/next_tick.js:68:7)
From: Task: WebDriver.createSession()
at Function.createSession (H:\ProtractorPocDemo\node_modules\selenium-webdriver\lib\webdriver.js:769:24)
at Function.createSession (H:\ProtractorPocDemo\node_modules\selenium-webdriver\chrome.js:761:15)
at Direct.getNewDriver (H:\ProtractorPocDemo\node_modules\protractor\built\driverProviders\direct.js:77:33)
at Runner.createBrowser (H:\ProtractorPocDemo\node_modules\protractor\built\runner.js:195:43)
at q.then.then (H:\ProtractorPocDemo\node_modules\protractor\built\runner.js:339:29)
at _fulfilled (H:\ProtractorPocDemo\node_modules\q\q.js:834:54)
at H:\ProtractorPocDemo\node_modules\q\q.js:863:30
at Promise.promise.promiseDispatch (H:\ProtractorPocDemo\node_modules\q\q.js:796:13)
at H:\ProtractorPocDemo\node_modules\q\q.js:556:49
at runSingle (H:\ProtractorPocDemo\node_modules\q\q.js:137:13)
[17:43:51] E/launcher - Process exited with error code 199

Help would really be appreciated..

abhijitgit27 picture abhijitgit27 on 6 Oct 2020

I am having the same issue with protractor

[19:54:01] I/launcher - Running 1 instances of WebDriver
[19:54:01] I/direct - Using ChromeDriver directly...
[19:54:31] E/launcher - Timed out waiting for the WebDriver server at http://127.0.0.1:34763/
[19:54:31] E/launcher - Error: Timed out waiting for the WebDriver server at http://127.0.0.1:34763/
at onError (/home/carlos/brandguarde-app/client/node_modules/selenium-webdriver/http/util.js:102:16)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:93:5)
From: Task: WebDriver.createSession()
at Function.createSession (/home/carlos/brandguarde-app/client/node_modules/selenium-webdriver/lib/webdriver.js:769:24)
at Function.createSession (/home/carlos/brandguarde-app/client/node_modules/selenium-webdriver/chrome.js:761:15)
at Direct.getNewDriver (/home/carlos/brandguarde-app/client/node_modules/protractor/built/driverProviders/direct.js:77:33)
at Runner.createBrowser (/home/carlos/brandguarde-app/client/node_modules/protractor/built/runner.js:195:43)
at /home/carlos/brandguarde-app/client/node_modules/protractor/built/runner.js:339:29
at _fulfilled (/home/carlos/brandguarde-app/client/node_modules/q/q.js:834:54)
at /home/carlos/brandguarde-app/client/node_modules/q/q.js:863:30
at Promise.promise.promiseDispatch (/home/carlos/brandguarde-app/client/node_modules/q/q.js:796:13)
at /home/carlos/brandguarde-app/client/node_modules/q/q.js:556:49
at runSingle (/home/carlos/brandguarde-app/client/node_modules/q/q.js:137:13)
[19:54:31] E/launcher - Process exited with error code 199

carloshdelreal picture carloshdelreal on 10 Dec 2020

same issue :
[17:39:49] I/launcher - Running 1 instances of WebDriver
[17:39:49] I/direct - Using ChromeDriver directly...
[17:39:49] E/launcher - spawn Unknown system error -86
[17:39:49] E/launcher - Error: spawn Unknown system error -86
at ChildProcess.spawn (internal/child_process.js:407:11)
at Object.spawn (child_process.js:548:9)
at exec (/Applications/Projects/atom-web/node_modules/selenium-webdriver/io/exec.js:116:27)
at /Applications/Projects/atom-web/node_modules/selenium-webdriver/remote/index.js:219:25
at processTicksAndRejections (internal/process/task_queues.js:97:5)
From: Task: WebDriver.createSession()
at Function.createSession (/Applications/Projects/atom-web/node_modules/selenium-webdriver/lib/webdriver.js:769:24)
at Function.createSession (/Applications/Projects/atom-web/node_modules/selenium-webdriver/chrome.js:761:15)
at Direct.getNewDriver (/Applications/Projects/atom-web/node_modules/protractor/built/driverProviders/direct.js:77:33)
at Runner.createBrowser (/Applications/Projects/atom-web/node_modules/protractor/built/runner.js:195:43)
at /Applications/Projects/atom-web/node_modules/protractor/built/runner.js:339:29
at _fulfilled (/Applications/Projects/atom-web/node_modules/protractor/node_modules/q/q.js:834:54)
at /Applications/Projects/atom-web/node_modules/protractor/node_modules/q/q.js:863:30
at Promise.promise.promiseDispatch (/Applications/Projects/atom-web/node_modules/protractor/node_modules/q/q.js:796:13)
at /Applications/Projects/atom-web/node_modules/protractor/node_modules/q/q.js:556:49
at runSingle (/Applications/Projects/atom-web/node_modules/protractor/node_modules/q/q.js:137:13)
[17:39:49] E/launcher - Process exited with error code 199

above solutions are not working

soundarya-kaplan picture soundarya-kaplan on 8 Jan 2021
👍1

Hi Team, Even i am facing the issue
webdriver-manager status
[14:56:47] I/status - selenium standalone version available: 3.141.59 [last]
[14:56:47] I/status - chromedriver version available: 87.0.4280.88 [last]
[14:56:47] I/status - geckodriver version available: v0.28.0 [last]
[14:56:47] I/status - android-sdk is not present
[14:56:47] I/status - appium is not present

`****** SERVER ALREADY STARTED ******
[14:55:30] I/launcher - Running 1 instances of WebDriver
[14:55:30] I/direct - Using ChromeDriver directly...
[14:55:30] E/launcher - spawn Unknown system error -86
[14:55:30] E/launcher - Error: spawn Unknown system error -86
    at ChildProcess.spawn (internal/child_process.js:366:11)
    at Object.spawn (child_process.js:551:9)
    at exec (/Users/naveensabares/ctp-mobile/node_modules/selenium-webdriver/io/exec.js:116:27)
    at resolveCommandLineFlags.then.args (/Users/naveensabares/ctp-mobile/node_modules/selenium-webdriver/remote/index.js:219:25)
    at process._tickCallback (internal/process/next_tick.js:68:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/Users/naveensabares/ctp-mobile/node_modules/selenium-webdriver/lib/webdriver.js:769:24)
    at Function.createSession (/Users/naveensabares/ctp-mobile/node_modules/selenium-webdriver/chrome.js:761:15)
    at Direct.getNewDriver (/Users/naveensabares/ctp-mobile/node_modules/protractor/built/driverProviders/direct.js:77:33)
    at Runner.createBrowser (/Users/naveensabares/ctp-mobile/node_modules/protractor/built/runner.js:195:43)
    at q.then.then (/Users/naveensabares/ctp-mobile/node_modules/protractor/built/runner.js:339:29)
    at _fulfilled (/Users/naveensabares/ctp-mobile/node_modules/protractor/node_modules/q/q.js:834:54)
    at /Users/naveensabares/ctp-mobile/node_modules/protractor/node_modules/q/q.js:863:30
    at Promise.promise.promiseDispatch (/Users/naveensabares/ctp-mobile/node_modules/protractor/node_modules/q/q.js:796:13)
    at /Users/naveensabares/ctp-mobile/node_modules/protractor/node_modules/q/q.js:556:49
    at runSingle (/Users/naveensabares/ctp-mobile/node_modules/protractor/node_modules/q/q.js:137:13)
[14:55:30] E/launcher - Process exited with error code 199

Process finished with exit code 199
`
naveenBsabares picture naveenBsabares on 8 Jan 2021
👍1
Was this page helpful?
0 / 5 - 0 ratings

Related issues

juliemr picture juliemr  路  3Comments
smarts picture smarts  路  3Comments
davidkarlsen picture davidkarlsen  路  3Comments
luakri picture luakri  路  3Comments
rafalf picture rafalf  路  3Comments