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]

I have this issue too. After rolling back to chrome 37,the console shows null

Original comment by StephenWang1011 on 23 Oct 2014 at 1:37

[GoogleCodeExporter]

When rolling back to Chrome 37 I was unable to install Chrome for all users. 
For Jenkins I had to set the user account associated with the service to the 
same user I installed Chrome 37 with. Only then did it start working. I believe 
the cause is that the Chrome installer for v37 does NOT install it for ALL 
users. Basically, Google is actively avoiding supporting the installation of 
old versions of Chrome, which unfortunately leaves a lot of people in a broken 
state.

Original comment by kevinmac...@gmail.com on 23 Oct 2014 at 2:52

[GoogleCodeExporter]

In directory "C:\Program Files (x86)\Google\Chrome\Application" You have file 
named "old_chrome.exe", You could change name from "chrome.exe" to 
"chrome_temp.exe" and rename "old_chrome.exe" to "chrome.exe". In gpedit.msc 
You need to download template for google chrome update and disable automatic 
updates. This method prevent feature problems. I recommend testing the new 
version on the development machine.

Original comment by tsztur...@gmail.com on 23 Oct 2014 at 7:10

[GoogleCodeExporter]

My resolution: 

I didn't want to be stuck on chrome 37 without the possibility of knowing if 
google will eventually fix the problem with interacting with the jenkins 
service.

1) autologon to my VM's
2) put a batch file in the startup directory for all users which is essentially 
the "java -jar slave.jar..."
3) make the slaves go into a lock screen after a minute.

This way, it allows for the VM's (Jenkin slaves) to be auto logged in and start 
their jenkin slave. If you need instructions on how to do this: write a script 
to enable remote registry editing, then writing another script to allow you to 
auto logon with the credentials you want, then write a third script to place a 
batch file of your choosing into the start up folder.

Original comment by ast...@zoosk.com on 23 Oct 2014 at 9:55

[GoogleCodeExporter]

We are also facing the same issue on
Chromedriver : 2.10 & 2.11 
chrome version : 38
Windows server
Jenkins  

I tried by reverting back to Chrome version 37 but getting following exception 
"org.openqa.selenium.WebDriverException: unknown error: cannot find Chrome 
binary"

But chromedriver binary was placed in the path and it is defined through 
system.setproperty().

When i installed chrome version 37, i couldn't able to see chrome binary fine 
in the following path "C:\Program Files"

please suggest me to overcome this issue.

Original comment by k.sivaku...@gmail.com on 24 Oct 2014 at 2:03

[GoogleCodeExporter]

 #55 k.sivaku...@gmail.com 

Use chromedriver ver. 2.10 instead of 2.11. 

Original comment by cap...@zeoalliance.com on 24 Oct 2014 at 2:05

[GoogleCodeExporter]

The v37 installer of Chromedriver is installing it for the current user only, 
probably under Users\<username>\AppData\Local\Chrome\Application, or similar.

Original comment by kevinmac...@gmail.com on 24 Oct 2014 at 2:56

[GoogleCodeExporter]

Same here.

Original comment by oljat...@gmail.com on 24 Oct 2014 at 4:39

[GoogleCodeExporter]

#56 - What does chrome driver v2.10 get you?  

When my set up was Jenkins as a service, I tried chrome driver 2.9, 2.10, and 
2.11 and none of them worked with chrome v38.

Original comment by ast...@zoosk.com on 24 Oct 2014 at 4:48

[GoogleCodeExporter]

As a workaround on Jenkins, we have had some success running the Jenkins slave 
from a command prompt rather than as a service(early days, we'll see how it 
fares over the weekend).

Steps:
1: Open Windows services on the slave.
2: Stop, and disable, the Jenkins agent service.
3: Navigate to the agent's page in Jenkins
4: Run the command it offers you to run on the agent, something like: 
javaws http://<your-jankes-xenkins-hostname>/computer/<jenkins slave 
name>/slave-agent.jnlp

Since the problem only appears to manifest when people run selenium via 
something running as a service(or similar), running the jenkins agent as a user 
process seems to workaround the issue. I've no idea if there are similar things 
people can do for their TeamCity setups, but good luck!

Original comment by jake.ben...@bromium.com on 24 Oct 2014 at 5:17

[GoogleCodeExporter]

After rolling back to v37, I was able to get past the Chrome binary not found 
issue (Jenkins) by overriding the location of chrome via a Selenium option:

String path = 
"C:\\Users\\Administrator\\AppData\\Local\\Google\\Chrome\\Application\\chrome.e
xe";
ChromeOptions options = new ChromeOptions();
options.setBinary(path);
WebDriver driver = new ChromeDriver(options); 

Original comment by mbo...@mirthcorp.com on 24 Oct 2014 at 9:40

[GoogleCodeExporter]

Issue 935 has been merged into this issue.

Original comment by barancev on 25 Oct 2014 at 9:08

[GoogleCodeExporter]

After rolling back to v37, i can able to execute my tests, solved temporary.

Original comment by k.sivaku...@gmail.com on 26 Oct 2014 at 9:47

[GoogleCodeExporter]

This matches what I'm seeing. In our case there's a maven project testing a web 
application; running from a Windows 7 machine at the command line works, but 
the same job fired using Jenkins on a Windows 8.1 slave fails with timeouts - 
weeks ago it was working fine. In both cases our chromedriver.exe is dated May 
2014.

I suggest the title of this issue is changed as right now it appears to be 
limited to Windows 2008 rather when run as a Windows service.

Original comment by james.mk...@gmail.com on 27 Oct 2014 at 1:27

[GoogleCodeExporter]

Well, you might want to temporarily swap to Firefox until this is fixed...

Original comment by jmachado...@gmail.com on 27 Oct 2014 at 7:47

[GoogleCodeExporter]

:download for chrome 37: 
http://www.filepuma.com/download/google_chrome_37.0.2062.124-6932/download/ . 
also using the latest version of chrome ie 38 and chrome driver 2.9 somehow 
worked. didnt try latest chrome browser with chromedriver 2.10 though.

Original comment by jumpingf...@gmail.com on 27 Oct 2014 at 10:34

[GoogleCodeExporter]

I also have the same problem running latest version of Chrome with TeamCity. 
Could NOT solve it by downgrading to ChromeDriver 2.9.0.1, didn't try 2.9.0.0 
though. I'm switching to another browser until problem has been solved.

Original comment by valtechs...@gmail.com on 29 Oct 2014 at 9:06

[GoogleCodeExporter]

I tried ChromeDriver 2.9 too with Chrome v38. It seemed to work in interactive 
mode - however I didn't run our full suite of regression tests. Running under a 
service account failed.

I also tried downgrading to Chrome 37 using the link in #33. Unfortunately this 
seems to be the installer for the current user only. For service accounts, we 
need to install for all users.

The link in #66 seems to be Chrome 37 for All Users.

Original comment by tim.buck...@gmail.com on 29 Oct 2014 at 9:57

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

did you try to use ChromeDriver v2.12 with Chrome Browser 38?

Original comment by denys.st...@gmail.com on 29 Oct 2014 at 10:36

[GoogleCodeExporter]

Denys, 
do you suppose that it can fix the issue? 
I don't see any information in the release notes that can be related to this:  
http://chromedriver.storage.googleapis.com/2.12/notes.txt

Original comment by igoro1...@gmail.com on 29 Oct 2014 at 10:50

[GoogleCodeExporter]

I've just tried it and 2.12 is still not working.
(Session info: chrome=38.0.2125.111)
(Driver info: chromedriver=2.12.301325 
(962dea43ddd90e7e4224a03fa3c36a421281abb7),platform=Windows NT 6.3 x86_64) (100)

Original comment by augustyn...@gmail.com on 29 Oct 2014 at 11:21

[GoogleCodeExporter]

Steps to downgrade Chrome to earlier version on Win 7/Win Server :
>> Go to "Program Files (x86)\Google\Chrome\Application" and rename 
"old_chrome.exe" to "chrome.exe".
>> Go to "%LOCALAPPDATA%\Google\Chrome\User Data\" and rename the folder 
"Default" to some other name. 
>> Launch the Chrome and disable Auto Update ( hit "chrome://plugins/" in 
browser and disable auto update)

Original comment by navi.heb...@gmail.com on 29 Oct 2014 at 11:40

[GoogleCodeExporter]

We are facing same issue with Jenkins and selenium. As a workaround, we have 
rolled back to Chrome 37 and continued with our tests. What is the plan 
regarding a fix for this issue?

Original comment by amol.gar...@gmail.com on 30 Oct 2014 at 9:29

[GoogleCodeExporter]

Eagerly waiting for the solution. As a workaround stopped jenkins slave service 
and manually Launch agent from browser on slave.

Original comment by jamnagar...@gmail.com on 30 Oct 2014 at 12:53

[GoogleCodeExporter]

I've tried downgrading to Chrome 37 using the link in #66 
(http://www.filepuma.com/download/google_chrome_37.0.2062.124-6932/download/) 
but when chrome starts it is still 38.  What am I missing?  I disabled Google 
update in plugins.  I don't see one called Chrome update.
Thanks.

Original comment by jl...@ksmpartners.com on 30 Oct 2014 at 2:26

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I updated ChromeDriver to the latest (2.12) and it's still not working for me 
either. I don't know if this is congruent with the issues you all are seeing, 
but when I run my RSpec script (written in Ruby), the instance of Chrome 
launches, it just doesn't do anything afterwards; my window resize command 
doesn't happen and the navigate.to() doesn't fire.

I'm using Windows 7 Enterprise and my Chrome is version 38.0.2125.111 m. Very 
frustrating as we have automation we're working on as well, and this is 
basically a huge blocker.

Original comment by DaveCB1...@gmail.com on 30 Oct 2014 at 3:08

[GoogleCodeExporter]

Hi all, we had a similar issue and we solved it yesterday, the problem was with 
the anti-virus, the anti-virus wasn't allowing the chromedriver to connect, we 
talk with our IT department and we asked them to add an exception rule on 
chromedriver, now the driver is allowed connections and our tests run with no 
problem.

Hope this helps, becauseI know you may be frustrated with all the "downgrade 
Chrome/Chromedriver" solutions

Original comment by lukasqua...@gmail.com on 30 Oct 2014 at 5:08

[GoogleCodeExporter]

In our case we have AVG and Microsoft Security Essentials - we've made no 
changes to either but I've not checked if your suggestion works for us yet 
either. Maybe a job for tomorrow.

Original comment by james.mk...@gmail.com on 30 Oct 2014 at 5:16

[GoogleCodeExporter]

We don't have any antivirus on our servers and the problem remains.

Original comment by augustyn...@gmail.com on 30 Oct 2014 at 5:19

[GoogleCodeExporter]

See https://code.google.com/p/chromium/issues/detail?id=422218 which was 
referenced in link #32. It appears they will be fixing this in Chrome rather 
than ChromeDriver.

Original comment by shirley....@gmail.com on 30 Oct 2014 at 6:33

[GoogleCodeExporter]

Its working fine in Chrome37 & chromedriver 2.9.

But Chrome is automatically updated to version 38.0.2125.111 m. Even I set the 
Google update in Disabled mode. using chrome://plugins/.

Option2: I tried to set the Google update -disabled using "regedit" . But i 
didnt find the Update folder itself.

Original comment by degalees...@gmail.com on 31 Oct 2014 at 7:41

[GoogleCodeExporter]

Same problem as #83.

Automatic update is disabled, yet it seems overnight we now have Chrome version 
38 on another one of our automation controllers. I double checked the automatic 
update settings - it is still disabled!

Does anyone know how to truly prevent Chrome from updating? Ideally we need a 
solution where even if someone requested a manual update of Chrome, it would 
fail.

Option 2 also does not work for us - the registry entries described don't exist.

Original comment by tim.buck...@gmail.com on 31 Oct 2014 at 9:56

[GoogleCodeExporter]

Looks like this issue is related with that Chrome bug:

https://code.google.com/p/chromium/issues/detail?id=422218

Hope the Chromium guys get to fix it for the next Chrome release. Please star 
that issue so we make it more urgent.

Original comment by victor.p...@datahug.com on 31 Oct 2014 at 9:58

[GoogleCodeExporter]

Hello,

Today I got latest version of Chrome exe V 2.12 and Standalone server 2.44, and 
we started facing same issue. Everything works when we run Standalone Hub and 
Node manually but when we run them using task scheduler then nothing works.

Please update if someone found solution related to this issue.

Original comment by praveent...@gmail.com on 31 Oct 2014 at 11:02

[GoogleCodeExporter]

#84 to stop Chrome from updating you need to get the "Google Update 
Administrative Template" and add it to your group policies in Windows. There 
you can disable the update function reliably.

Original comment by Alexande...@googlemail.com on 31 Oct 2014 at 11:31

[GoogleCodeExporter]

Facing same issue,

Not able to run my test case in chrome 38, using robotframework, 
Selenium2Library
 (Session info: chrome=38.0.2125.111)
 (Driver info: chromedriver=2.12.301325 (962dea43ddd90e7e4224a03fa3c36a421281ab
7),platform=Windows NT 6.1 SP1 x86_64),

Original comment by devgunra...@gmail.com on 1 Nov 2014 at 10:43

[GoogleCodeExporter]

Hello guys,
I have configure a windows slave that runs bdd-security using chromedriver 2.9 
and chrome Locally (in slave windows) everything is running fine. However, when 
I run the job on master Jenkins, the chromerdriver is up but hanging. Does any 
one have any idea?

Thanks               

Original comment by laminf...@gmail.com on 2 Nov 2014 at 5:24

[GoogleCodeExporter]

Yes, I have this idea that few people trouble to read the thread and realize 
that everybody is having the same problem, thus making the thread so noisy I 
have to sign off it and not know when an actual solution has materialized. Oh 
well.  

Original comment by kevinmac...@gmail.com on 2 Nov 2014 at 6:44

[GoogleCodeExporter]

This is a regression in Chrome, so I'm merging this bug into the bug in the 
Chromium issue tracker. Updates will appear in that bug.

Original comment by samu...@chromium.org on 5 Nov 2014 at 10:47

• Changed state: Duplicate

[GoogleCodeExporter]

@samu - can you provide a link to the chromium issue so that we can follow it?

Original comment by nieveg...@gmail.com on 6 Nov 2014 at 2:32

[GoogleCodeExporter]

That's the related chrome issue:

https://code.google.com/p/chromium/issues/detail?id=422218

Original comment by victor.p...@datahug.com on 6 Nov 2014 at 2:33

[GoogleCodeExporter]

Hope this will be fixed.

Original comment by mingz...@gmail.com on 10 Nov 2014 at 11:07

[GoogleCodeExporter]

Same problem here. 
Jenkins, 
Windows 7 Professional x64
Chrome 38.0.2125.111 m (64-bit)
ChromeDriver (v2.9.248315)

Original comment by stephenj...@gmail.com on 11 Nov 2014 at 5:07

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

New version of chrome was released - 38.0.2125.122. Has any body checked, is 
problem already fixed?

Original comment by logos.goo on 12 Nov 2014 at 10:35

[GoogleCodeExporter]

Thread #97, Its not working in new release 38.0.2125.122

Original comment by degalees...@gmail.com on 12 Nov 2014 at 10:57

[GoogleCodeExporter]

You'll need to wait for Chrome 39 which should be released in a week, or you 
can try the beta in the meantime.

Original comment by matthew....@exony.com on 12 Nov 2014 at 11:03

[GoogleCodeExporter]

So is it expected to be fixed on Chrome 39?

Original comment by ma...@betware.com on 13 Nov 2014 at 12:22