Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by GoogleCodeExporter
, 1 year ago
Unable to either launch or connect to Chrome. Please check that ChromeDriver is up-to-date. Using Chrome binary at: C:\Users\Administrator\AppData\Local\Google\Chrome\Application\chrome.exe (WARNING: The server did not provide any stacktrace
via GitHub by GoogleCodeExporter
, 1 year ago
Unable to either launch or connect to Chrome. Please check that ChromeDriver is up-to-date. Using Chrome binary at: C:\Users\Administrator\AppData\Local\Google\Chrome\Application\chrome.exe (WARNING: The server did not provide any stacktrace
via GitHub by GoogleCodeExporter
, 1 year ago
Unable to either launch or connect to Chrome. Please check that ChromeDriver is up-to-date. Using Chrome binary at: C:\Users\Administrator\AppData\Local\Google\Chrome\Application\chrome.exe (WARNING: The server did not provide any stacktrace
via Google Groups by Dean Blechman, 1 year ago
duration or timeout: 63.87 seconds Build info: version: '2.24.1', revision: '17205', time: '2012-06-19 16:53:24' System info: os.name: 'Windows Server 2008 R2', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_66' Driver info: driver.version: ChromeDriver Session ID: db858e0e720d15d82c6a4a9da6d90eef
via varunin.com by Unknown author, 1 year ago
chrome not reachable (Driver info: chromedriver=2.2,platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 28.67 seconds Build info: version: '2.24.1', revision: '17205
via Stack Overflow by MacTire
, 1 year ago
); duration or timeout: 60.03 seconds Build info: version: '2.10.0', revision: '14416', time: '2011-10-27 23:00:15' ystem info: os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-45-generic', java.version: '1.6.0' Driver info: driver.version: ChromeDriver
org.openqa.selenium.WebDriverException: Unable to either launch or connect to Chrome. Please check that ChromeDriver is up-to-date. Using Chrome binary at: C:\Users\Administrator\AppData\Local\Google\Chrome\Application\chrome.exe (WARNING: The server did not provide any stacktrace information)Command duration or timeout: 91.29 secondsBuild info: version: '2.15.0', revision: '15105', time: '2011-12-08 09:56:43'System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.6.0_22'Driver info: driver.version: ChromeDriver at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:147) at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:113) at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:424) at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:123) at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:78) at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:120) at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:87) at com.minted.SeleniumTestCase.setUp(SeleniumTestCase.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:550) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:212) at org.testng.internal.Invoker.invokeMethod(Invoker.java:638) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:891) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1215) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) at org.testng.TestRunner.privateRun(TestRunner.java:758) at org.testng.TestRunner.run(TestRunner.java:613) at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) at org.testng.SuiteRunner.run(SuiteRunner.java:240) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:87) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1170) at org.testng.TestNG.runSuitesLocally(TestNG.java:1095) at org.testng.TestNG.run(TestNG.java:1007) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:109) at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:202) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:173)