-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not launch IE #6
Comments
Same issue here. OS: Win 7 x 64 I also set the path to IE_BIN to C:\Program Files (x86)\Internet Explorer\iexplore.exe |
I'm having the same issue. Here's some console output for reference, maybe it helps:
I can see the browser opening three times. |
I'm experiencing the exact same thing as @sjmulder. |
Same thing here ! |
I also have the same!!! |
Same :) |
I also have the same!!! IE opened three times, and console print message: "Can't start IE" |
The issue does not occur for me on Windows 8.1 + IE 11:
This is the same system that previously had this issue on Windows 8 + IE 10. |
Having the same issue on Windows 8 + IE 10, karma v0.10.2. |
I had the same issue on Win 7 + IE 10, Workaround by CoffeeAndMe [https://github.com//issues/3#issuecomment-23428943] on a other issue helped me. Co-workers suggestion at disabling Automatic Crash Recovery seems to have helped. It will now restart IE when it encounters an issue and the subsequent launch will attach to the test runner correctly. http://windows.microsoft.com/en-us/internet-explorer/reopen-previous-session#ie=ie-10 |
Worked for me. Thank you very much! |
The methods above as well as disabling automatic crash recovery didn't resolve issue for me. I'm still getting three windows opening and then no tests being run. Win 7 + IE10 . Any other ideas? |
I'd like to know if anyone is still experiencing this issue? Thanks! |
I also experienced this issue after upgrading from IE9 to IE11 on our build server (Windows Server 2008 R2 64bit). It seems like karma-ie-launcher was unable to kill the initial ie process (see wmic comment section in index.js), resulting in the tests actually running but without being connected to karma. During the testrun three IE instances were launched, one of which actually ran the tests, one with "karma disconnected" on screen, and the last with "unable to connect" on screen. For me the solution was: change IE_BIN env variable from:
to:
And disabling Automatic Crash Recovery as mentioned in #6 (comment) made the tests run when logged into the server as a normal user. I also had to use PSTools to get IE configured on the system account. Without this the system account will not be able to connect because of the initial configuration dialog that pops up the first time you launch IE, leaving karma sad with the following log statement:
To launch IE as the system account which is the same account jenkins uses:
Then just complete the initial config steps in the dialog. Env: Excerpt from log:
|
@kenglxn Follwing your method worked but it spawns ie without localStorage support.Says "This function is not supported on this system." |
@kenglxn +100000 I had a feeling that the initial prompt was causing it not to run but I didn't have access to the system account. Running your steps fixed my issue. |
I'm still having this error, I have followed all steps and I doesn't seem to be doing anything different but it also now throws in the error of Here is the full log when I run
Below is my karma.conf.js file // Karma configuration
Also apologies if I am doing something wrong, I am extremely new so please bear with me. |
I, too, am having the same issue. Win 7 x64, IE 11. If I have IE opened, then Karma will attempt to start three browsers and fails. Although my tests run. Here is the output D:\Code\movie-app>karma start --log-level debug I have turned off automatic crash recovery, as suggested by SathishN did not resolve the issue. The work around I have is to run karma first and then open a new browser. But then if I stop karma all my browsers close out. This is inconvenient when watching videos on Angular JS testing. It is interesting that this issue has been open for 3 years with no solution. |
I have the exactly same issue. Win 7 x64, IE 11, Karma v1.1.2. If no IE was open before, Karma works fine. But if an IE was opened already, Karma will attempt to start three browsers and fails. although tests were ran. Here is the output: C:\Workspace\Node.js\UnitTestingJasmine>karma start 05 08 2016 10:29:33.913:INFO [launcher]: Trying to start IE again (1/2). 05 08 2016 10:29:34.809:INFO [launcher]: Trying to start IE again (2/2). 05 08 2016 10:29:35.576:ERROR [launcher]: IE failed 2 times (cannot start). Giving up. |
@jsouthwo Same here. This solved it: IE11: {
base: "IE",
flags: ['-extoff']
}, |
I had the same issue, but rather than change the IE browser config to have the -extoff flag, I went into the IE options and manually disabled every extension. Seems to have worked. |
Hi,
I have
OS: Win 7 x 64
Karma: v0.9.3
Grunt:grunt-cli v0.1.9
grunt v0.4.1
I am getting error below:
WARN [config]: "/" is proxied, you should probably change urlRoot to avoid conflicts
INFO [karma]: Karma v0.9.3 server started at http://localhost:9876/
INFO [launcher]: Trying to start IE again.
ERROR [launcher]: Cannot start IE
INFO [launcher]: Trying to start IE again.
ERROR [launcher]: Cannot start IE
INFO [launcher]: Trying to start IE again.
ERROR [launcher]: Cannot start IE
I set the path to IE_BIN to C:\Program Files (x86)\Internet Explorer\iexplore.exe
http://localhost is added to Local Intranet zone and Protected mode is disabled.
The issue is still happening.
I looked at karma-runner/karma/issues:
#605
#369
#429
Please advise
The text was updated successfully, but these errors were encountered: