Unexpected error launching Internet Explorer. IELaunchURL() returned HRESULT 80070012 ('There are no more files.')

[lukeis]

Originally reported on Google Code with ID 8545

What steps will reproduce the problem?
1. Launch any with Internet explorer 9 Using WebDriver

What do you see instead?
I get an Exception Caused by: org.openqa.selenium.remote.SessionNotFoundException:
Unexpected error launching Internet Explorer. IELaunchURL() returned HRESULT 80070012
('There are no more files.') for URL 'about:blank' (WARNING: The server did not provide
any stacktrace information)
Command duration or timeout: 21.32 seconds

Selenium version: 2.44
OS: Windows 7 x64
Browser: Internet Explorer
Browser version: 9 (v9.0.8112.16421 Update 9.0.34)

Tried with Protected Mode enabled in all zoned and disabled does not make any difference.
IEDriverServer v.2.44.0.0

I launch a selenium grid node, that connect to a hub with then runs tests.
i've set webdriver.ie.driver.extractpath to C:\node\temp, on the node because IEDriverServer
extracts a library to a temp folder and tries to execute it but fails, because corporate
protection software prevents it.

Attached full log file

Reported by Justinasu on 2015-02-27 09:41:44

---

• Attachment: selenium.log

[lukeis]

Reported by barancev on 2015-03-02 21:18:12

• Labels added: Browser-IE

[lukeis]

Run InternetExplorerDriver with TRACE log level and attach the log here:

InternetExplorerDriverService service = new InternetExplorerDriverService.Builder()
      .withLogLevel(InternetExplorerDriverLogLevel.TRACE)
      .withLogFile(new File("iedriver.log"))
      .build();
InternetExplorerDriver driver = new InternetExplorerDriver(service);

Reported by barancev on 2015-03-08 19:55:42

• Status changed: NeedsClarification

[lukeis]

for future reference, i'm using a binary executable version of InternetExplorer driver.

Reported by Justinasu on 2015-03-09 06:48:17

[lukeis]

Delete that output-log-level.log, it appears in order to set log level to TRACE need
to pass 
-Dwebdriver.ie.driver.loglevel=TRACE
parameter where loglevel is without a dash.

but then the output does not get logged to output.log file specified by the -log output.log
parameter it is just printed out into the command prompt console

Reported by Justinasu on 2015-03-09 07:56:35

[lukeis]

ok found command line argument -Dwebdriver.ie.driver.logfile=trace.log

attached the trace log

Reported by Justinasu on 2015-03-09 08:06:55

---

• Attachment: trace.log

[lukeis]

Just tried with the recently released lates selenium 2.45 both client and driver but
result remains the same

Reported by Justinasu on 2015-03-09 08:16:51

[lukeis]

What happens if you don't specify about:blank as the initial browser URL?

Reported by james.h.evans.jr on 2015-03-09 09:59:59

[lukeis]

Exactly the same.

about:blank is a valid url, it worked before and it works now if you enter in by hand.

it's just the only way to force browser not to load home page, which in our corporate
network is forced by group policy to a intranet site, which is really slow. There is
no point in loading it on every test.

Reported by Justinasu on 2015-03-09 10:23:48

---

• Attachment: output.log.3
• Attachment: trace.log

[lukeis]

Yes, but about:blank is a "special" URL with respect to Protected Mode zones, which
is why by default the browser launches to an internal "This is the initial page..."
page *instead of* the browser's normal home page. 

Reported by james.h.evans.jr on 2015-03-09 10:31:30

[lukeis]

if you, have any suggestions i'm willing to try them out. But as you can see it if don't
pass about:blank as an initial url, IE still does not open.

Reported by Justinasu on 2015-03-09 10:35:50

[lukeis]

Status:     NeedsClarification

James, is there any thing more that i need to provide to clarify this bug ?

Reported by Justinasu on 2015-04-15 10:14:23

[lukeis]

There's nothing further you can provide that I know of. There's also, frankly, little
chance of being able to do anything to actually fix this issue. The driver is using
a valid, supported Windows API function, and is using it correctly. The documentation
on that API function gives little information about what failure cases can result from
that API, nor any indication of what to do to correct those failure cases. The API
is something of a black box, and its behavior is entirely out of the driver's control.

Reported by james.h.evans.jr on 2015-04-15 10:25:16

[lukeis]

I am seeing this very issue using IE 11 and the latest IE web driver 2.45.0.0. Please
let me know if there is any additional information that I can provide.

Reported by fizgiggsr on 2015-04-16 23:56:37

[lukeis]

I am seeing this error too. Selenium 2.47.1 and IEDriver 2.47.0.
All zones have Protected Mode Enabled and the URL is the default "This is the initial
page...".
I have tried disabling Protected Mode for all zones, same error.
I can access the local URL for the initial page manually without any errors.

Reported by silwing on 2015-08-18 08:58:10

[lukeis]

Reported by luke.semerau on 2015-09-17 17:47:31

• Labels added: Restrict-AddIssueComment-Commit