E/launcher - session not created exception and it gets exited with error code 199

[Dilip-Vaze]

PS D:\VDSS_SDM_PROTRACTOR> protractor conf.js
(node:15140) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[14:42:43] I/launcher - Running 1 instances of WebDriver
[14:42:43] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
[14:43:47] E/launcher - session not created exception
from disconnected: unable to connect to renderer
(Session info: chrome=67.0.3396.99)
(Driver info: chromedriver=2.40.565498 (ea082db3280dd6843ebfb08a625e3eb905c4f5ab),platform=Windows NT 10.0.16299 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 62.60 seconds
Build info: version: '3.13.0', revision: '2f0d292', time: '2018-06-25T15:32:19.891Z'
System info: host: 'BANWOR488', ip: '10.20.3.184', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_102'
Driver info: driver.version: unknown
[14:43:47] E/launcher - SessionNotCreatedError: session not created exception
from disconnected: unable to connect to renderer
(Session info: chrome=67.0.3396.99)
(Driver info: chromedriver=2.40.565498 (ea082db3280dd6843ebfb08a625e3eb905c4f5ab),platform=Windows NT 10.0.16299 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 62.60 seconds
Build info: version: '3.13.0', revision: '2f0d292', time: '2018-06-25T15:32:19.891Z'
System info: host: 'BANWOR488', ip: '10.20.3.184', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_102'
Driver info: driver.version: unknown
at Object.checkLegacyResponse (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:546:15)
at parseHttpResponse (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13)
at doSend.then.response (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
From: Task: WebDriver.createSession()
at Function.createSession (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:769:24)
at Function.createSession (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\chrome.js:761:15)
at createDriver (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:170:33)
at Builder.build (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:626:16)
at Hosted.getNewDriver (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\built\driverProviders\driverProvider.js:53:33)
at Runner.createBrowser (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\built\runner.js:195:43)
at q.then.then (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\built\runner.js:339:29)
at _fulfilled (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:834:54)
at self.promiseDispatch.done (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:863:30)
at Promise.promise.promiseDispatch (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:796:13)
[14:43:47] E/launcher - Process exited with error code 199
PS D:\VDSS_SDM_PROTRACTOR>

[balintbabics]

I have the exact same problem...

I didn't change anything on the test cases, on Thursday I could execute them w/o any problem, today I can't.

[IgorSasovets]

Hi, @Dilip-Vaze ! Please provide your config file and test example.

[dilipvaze]

Hello @IgorSasovets

Its a very basic simple test script what i m trying, anyways i have attached for reference.
Conf_Test.zip

Thanks,
Dilip Vaze

[IgorSasovets]

@dilipvaze , I ran test provided by you and it passed. Here is console output:

[dilipvaze]

@IgorSasovets

Thank you for looking into. But the same fails for us.
The above console of mine has all the details, did you tried on the same setup?
Because here i tried in different machine too no success i get the same error message.

@balintbabics
Did you find any solution?

Thanks & Regards,
Dilip Vaze

[balintbabics]

@dilipvaze
Unfortunately not yet, and now it's a quite big issue for me.

[CrispusDH]

try to remove seleniumAddress: 'http://localhost:4444/wd/hub', and add instead directConnect: true. Also, I have found that issue appears if you use obsolete chromedriver but in your case I see that it is up to date.

[IgorSasovets]

@dilipvaze , try directConnect option as @CrispusDH said. Also, please provide step by step command which you're using.

[dilipvaze]

@CrispusDH
Tried with direct connect also didn't help i get the same issue as above.
@IgorSasovets
Steps:

1. Installed npm version 5.6.0
2. installed protractor: 5.3.2
3. Webdriver-manager update
4. Webdriver-manager start (to start selenium server) and then just executing the example file also i get the same error please find below the console message.

Microsoft Windows [Version 10.0.16299.248]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\example>protractor conf.js
(node:16172) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[16:10:48] I/launcher - Running 1 instances of WebDriver
[16:10:48] I/direct - Using ChromeDriver directly...

DevTools listening on ws://127.0.0.1:49370/devtools/browser/3fcd6fbd-465b-4ef8-9da6-91fa577e7f6b
[16:11:53] E/launcher - session not created exception
from disconnected: unable to connect to renderer
(Session info: chrome=67.0.3396.99)
(Driver info: chromedriver=2.40.565498 (ea082db3280dd6843ebfb08a625e3eb905c4f5ab),platform=Windows NT 10.0.16299 x86_64)
[16:11:53] E/launcher - SessionNotCreatedError: session not created exception
from disconnected: unable to connect to renderer
(Session info: chrome=67.0.3396.99)
(Driver info: chromedriver=2.40.565498 (ea082db3280dd6843ebfb08a625e3eb905c4f5ab),platform=Windows NT 10.0.16299 x86_64)
at Object.checkLegacyResponse (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:546:15)
at parseHttpResponse (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13)
at doSend.then.response (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
From: Task: WebDriver.createSession()
at Function.createSession (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:769:24)
at Function.createSession (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\chrome.js:761:15)
at Direct.getNewDriver (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\built\driverProviders\direct.js:77:33)
at Runner.createBrowser (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\built\runner.js:195:43)
at q.then.then (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\built\runner.js:339:29)
at _fulfilled (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:834:54)
at self.promiseDispatch.done (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:863:30)
at Promise.promise.promiseDispatch (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:796:13)
at C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:556:49
at runSingle (C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:137:13)
[16:11:53] E/launcher - Process exited with error code 199

C:\Users\dva\AppData\Roaming\npm\node_modules\protractor\example>

Thanks & Regards,
Dilip Vaze

[balintbabics]

@IgorSasovets

Unfortunately directConnect: true did not worked.

Installed and used versions:

• npm: 6.1.0
• protractor: 5.3.2
• selenium standalone: 3.13.0
• chromedriver: 2.40
• geckodriver: v0.21.0

Steps:

• from command line: webdriver-manager update
• webdriver-manager start
• in another command line window from the protractor test and conf's folder: protractor conf.js
• then fail with error code 199: E/launcher - Process exited with error code 199

[IgorSasovets]

Flow that I used:

1. npm install protractor --save-dev
2. node node_modules\protractor\bin\webdriver-manager update
3. node node_modules\protractor\bin\webdriver-manager start
4. In other console window node node_modules\protractor\bin\protractor conf.js
   Also, I would recommend you to run npm cache clean --force command before modules installation

[Galileo1]

I got the same issue today. Chromedriver website shows that chromedriver version 2.40 is the compatible chrome version 66-68. Any clue??
E/launcher - SessionNotCreatedError: session not created exception from disconnected: unable to connect to renderer (Session info: chrome=67.0.3396.99) (Driver info: chromedriver=2.40.565386 (45a059dc425e08165f9a10324bd1380cc13ca363),platform=Mac OS X 10.13.5 x86_64) (WARNING:The server did not provide any stacktrace information) Command duration or timeout: 489 milliseconds Build info: version: '3.13.0', revision: '2f0d292', time: '2018-06-25T15:32:19.891Z' System info: host: 'xxxxx', ip: 'xx', os.name: 'Mac OS X', os.arch: 'x86_64',os.version: '10.13.5', java.version: '9.0.4' Driver info: driver.version: unknown

Selenium standalone server @3.13 and protractor @5.3.2

[zuzusik]

Had the same issue today, solved using this answer: https://stackoverflow.com/questions/46807596/webdrivererror-disconnected-unable-to-connect-to-renderer#comment90246515_49985242

[jjelev]

@zuzusik You are right.
Everyone please check your /etc/hosts file. I my 127.0.0.1 rule was being commented.

[karthikn1610]

I faced the same issue. Just install or update the protractor. If you still installed the protractor also Do the following steps, run the following in cmd prompt or PowerShell

npm install protractor -g 

npm install webdriver-manager -g

If you got the error as running in the background, check the running processor and close all the running processor and try.

After the above steps run the following

webdriver-manager update
webdriver-manager start

OR
check below
https://stackoverflow.com/a/59194801/12485492