ChromeDriver 2.11 not working with Chrome 38 in Windows Server 2008R2

[GoogleCodeExporter]

See http://goo.gl/ll2FvQ for common issues.

Issue Description:
ChromeDriver can not communicate with Chrome in Windows Server 2008R2

Environment Details
- Windows Server 2008 R2 SP1 (x64)
- Chrome (38.0.2125.101 m)

Steps to reproduce:
1. Execute simple Selenium test against Chrome (example below)

Example test:
IWebDriver _driver = new ChromeDriver();
_driver.Manage().Window.Maximize();

Error details:

Stacktrace

MESSAGE:
Initialization method WebAppTests.HomePageTests.Initialize threw exception. 
OpenQA.Selenium.WebDriverException: OpenQA.Selenium.WebDriverException: The 
HTTP request to the remote WebDriver server for URL 
http://localhost:3581/session/446827e125ab6df59b48ebfde1a33a9a/window/current/ma
ximize timed out after 60 seconds. ---> System.Net.WebException: The operation 
has timed out.
+++++++++++++++++++
STACK TRACE:
    at System.Net.HttpWebRequest.GetResponse()
   at OpenQA.Selenium.Remote.HttpCommandExecutor.CreateResponse(WebRequest request)
 --- End of inner exception stack trace ---
    at OpenQA.Selenium.Remote.HttpCommandExecutor.CreateResponse(WebRequest request)
   at OpenQA.Selenium.Remote.HttpCommandExecutor.Execute(Command commandToExecute)
   at OpenQA.Selenium.Remote.DriverServiceCommandExecutor.Execute(Command commandToExecute)
   at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
   at OpenQA.Selenium.Remote.RemoteWindow.Maximize()
   at Datahug.AutomationFramework.GUI.CommonUtilities.Browser.Initialize() in c:\buildworkspaces\WebApp-FunctionalTests-Build\Datahug.AutomationFramework.GUI\CommonUtilities\Browser.cs:line 59

Other details:

- All other actions timeout as well (is not an isolated issue with .Maximize())
- It works correctly in Windows 7 SP1
- Issue seen after upgrading Chrome to v38 in the Windows Server machine

Original issue reported on code.google.com by victor.p...@datahug.com on 9 Oct 2014 at 9:55

[GoogleCodeExporter]

This was fixed and released on 11/18 in Chrome 39.0.2171.65. I updated and 
tested with chromedriver 2.42 under a Windows service and it worked.

Original comment by para.sel...@gmail.com on 18 Nov 2014 at 5:50

[GoogleCodeExporter]

Hi everybody,

I had the same issue but it seems to be solved after I updated chrome to 
version: 39.0.2171.65 which was released yesterday. I am using chromedriver 
version: 2.12.

Hope this problem will be fix for all of you folks.

Regards, Karol

Original comment by majuzzz on 19 Nov 2014 at 9:49

[GoogleCodeExporter]

Hi Everybody,

How to upgrade Chrome version on Jenkins.

Please update me asap

Thanks

Original comment by execonli...@gmail.com on 19 Nov 2014 at 10:15

[GoogleCodeExporter]

You don't update chrome on Jenkins but on your (virtual) machine. Plus if you 
want to update chromedriver simply put the newer version to your project 
repository. This is how I do it.

Original comment by majuzzz on 19 Nov 2014 at 11:07

[GoogleCodeExporter]

Is there anyone else who is still facing same issue even after upgrading to 
latest chrome?
My settings:
chrome: 37.0.2062.124/103 and 39.0.2171.65 
Driver: 2.9,10,12
Win 7 64bit
Selenium version 2.42
Got this in log:
org.openqa.selenium.WebDriverException: unknown error: cannot determine loading 
statusfrom timeout: Timed out receiving message from renderer: 600.000 (Session 
info: chrome=39.0.2171.65) (Driver info: chromedriver=2.12.301325 
(962dea43ddd90e7e4224a03fa3c36a421281abb7),platform=Windows NT 6.1 SP1 x86_64) 
(WARNING: The server did not provide any stacktrace information)Command 
duration or timeout: 600.05 secondsBuild info: version: '2.42.2', revision: 
'6a6995d31c7c56c340d6f45a76976d43506cd6cc', time: '2014-06-03 10:52:47'System 
info: host: 'NCEVC-00252', ip: '10.64.158.246', os.name: 'Windows 7', os.arch: 
'x86', os.version: '6.1', java.version: '1.6.0_26'Session ID: 
4dfd6d34926aeb9b5218366ab7a12bcdDriver info: 
org.openqa.selenium.chrome.ChromeDriverCapabilities [{platform=XP, 
acceptSslCerts=true, javascriptEnabled=true, browserName=chrome, 
chrome={userDataDir=C:\Users\$NCEOC~1\AppData\Local\Temp\scoped_dir5788_20334}, 
rotatable=false, locationContextEnabled=true, mobileEmulationEnabled=false, 
version=39.0.2171.65, takesHeapSnapshot=true, cssSelectorsEnabled=true, 
databaseEnabled=false, handlesAlerts=true, browserConnectionEnabled=false, 
nativeEvents=true, webStorageEnabled=true, applicationCacheEnabled=false, 
takesScreenshot=true}]  at 
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)   at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorI
mpl.java:39)    at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorA
ccessorImpl.java:27)    at 
java.lang.reflect.Constructor.newInstance(Constructor.java:513) at 
org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)  a
t 
org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:
156)    at 
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)    at 
org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:304)    at 
org.openqa.selenium.remote.RemoteWebDriver$RemoteNavigation.to(RemoteWebDriver.j
ava:850)    

Original comment by vinay.gu...@gmail.com on 20 Nov 2014 at 1:32