General Error: Error launching web driver! - (Moved)

[HighlanderSword]

Hello,

 

I'm running the demo script ( wd_demo.au3) I select edge and any option from the menu and it fails to launch the edge browser 

Below is what I get from the script , the log file is not created 

__WD_IsLatestRelease: True
_WD_IsLatestRelease ==> Success
_WD_Startup: OS:    WIN_10 WIN32_NT 18363 
_WD_Startup: AutoIt:    3.3.14.5
_WD_Startup: WD.au3:    0.4.1.0 (Up to date)
_WD_Startup: WinHTTP:    1.6.4.2
_WD_Startup: Driver:    msedgedriver.exe
_WD_Startup: Params:    --verbose --log-path="C:\Autoit\edge\WebDriver-0.4.1.0\msedge.log"
_WD_Startup: Port:    9515
_WD_Startup ==> General Error: Error launching web driver!

 

When i run the Msedgedriver manual I get a dos box with the below 

Starting MSEdgeDriver 92.0.902.84 (c04f45e8f08ccf4fb4388efae578d6565cf7a982) on port 9515
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping MSEdgeDriver safe.
MSEdgeDriver was started successfully.

 

Any ideas what I'm doing wrong ?

 

 

 

[Danp2]

Where does  msedgedriver.exe reside? If it's not in the same directory as your script, then you need to change the following line to include the path --

_WD_Option('Driver', 'msedgedriver.exe')

 

[HighlanderSword]

Ok thanks that resolved that issue , now have a new one 

When running the script to test navigation , dos box opens with this 

Starting MSEdgeDriver 92.0.902.84 (c04f45e8f08ccf4fb4388efae578d6565cf7a982) on port 9515
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping MSEdgeDriver safe.
MSEdgeDriver was started successfully.
[5336:256:0827/145353.516:ERROR:storage_reserve.cc(164)] Failed to open file to mark as storage reserve: C:\Users\paul\AppData\Local\Temp\scoped_dir17736_80341943\Default\Code Cache\js

DevTools listening on ws://127.0.0.1:56662/devtools/browser/477da222-323f-4813-8117-195f079c1f2d
[5336:12724:0827/145353.723:ERROR:edge_auth_errors.cc(385)] EDGE_IDENTITY: Get Default OS Account failed: Error: Primary Error: kImplicitSignInFailure, Secondary Error: kAccountProviderFetchError, Platform error: 0, Error string:
 

And the Edge browser opens and has an url of data:,

 

[Danp2]

@HighlanderSwordDifficult to say without more details. Can you post a short script that demonstrates the issue? Do the errors appear when you run wd_demo?

[Jos]

Moved to the appropriate forum, as the AutoIt Example Scripts forum very clearly states:

Quote

Share your cool AutoIt scripts, UDFs and applications with others.

---

Do not post general support questions here, instead use the AutoIt Help and Support forums.

Moderation Team

[HighlanderSword]

Hello,

It is the Wd_Demo that is generating the issues , I've just begun to look at using this method to automate some manual browser  steps

 

 

[Danp2]

54 minutes ago, HighlanderSword said:

MSEdgeDriver 92.0.902.84

I just upgraded to v92.0.902.78 today, which was supposed to be the latest. I tested with it and it ran fine, although it did display the same "Failed to open file to mark as storage reserve" error.

Any errors being displayed in the Scite output panel?

[HighlanderSword]

Below is what is posted 

 

 

_WD_IsLatestRelease: True
_WD_IsLatestRelease ==> Success
_WD_Startup: OS:    WIN_10 WIN32_NT 18363 
_WD_Startup: AutoIt:    3.3.14.5
_WD_Startup: WD.au3:    0.4.1.0 (Up to date)
_WD_Startup: WinHTTP:    1.6.4.2
_WD_Startup: Driver:    C:\LBD1277\Autoit\edge\msedgedriver.exe
_WD_Startup: Params:    --verbose --log-path="C:\LBD1277\Autoit\edge\WebDriver-0.4.1.0\msedge.log"
_WD_Startup: Port:    9515
__WD_Post: URL=HTTP://127.0.0.1:9515/session; $sData={"capabilities": {"alwaysMatch": {"ms:edgeOptions": {"binary": "C:/Program Files (x86)/Microsoft/Edge/Application/msedge.exe", "excludeSwitches": [ "enable-automation"], "useAutomationExtension": false}}}}
__WD_Post: StatusCode=0; ResponseText=WinHTTP request timed out before Webdriver...
__WD_Post ==> Send / Recv error: WinHTTP request timed out before Webdriver
_WD_CreateSession: WinHTTP request timed out before Webdriver
_WD_CreateSession ==> Webdriver Exception: HTTP status = 0

[Danp2]

Not sure that it will make a difference, but you could try this modified $sDesiredCapabilities definition --

$sDesiredCapabilities = '{"capabilities": {"alwaysMatch": {"ms:edgeOptions": {"excludeSwitches": [ "enable-automation"], "useAutomationExtension": false}}}}'

You could also check msedge.log to see if it's contents could help diagnose the issue.

[HighlanderSword]

 

Hello,

 

Below is what I have already , looks like it matches your except for the Binary details

$sDesiredCapabilities = '{"capabilities": {"alwaysMatch": {"ms:edgeOptions": {"binary": "' & "C:/Program Files (x86)" & '/Microsoft/Edge/Application/msedge.exe", "excludeSwitches": [ "enable-automation"], "useAutomationExtension": false}}}}'

I attached the log file, I'm not seeing anything that stands out as an issue

 

msedge.log

[Danp2]

54 minutes ago, HighlanderSword said:

Below is what I have already , looks like it matches your except for the Binary details

Exactly. I wanted you to try without the "binary" portion. It probably won't change anything, but it's worth a shot.

Edit: Your log file appears to be missing a ton of details. I can only guess that there is something wrong with your MSEdge setup.

Edit #2: It appears that your browser version (92.0.902.73) is out of sync with your webdriver version (92.0.902.84). I would recommend addressing that and then report back your findings.

Edited August 28, 2021 by Danp2

[HighlanderSword]

ok got the Driver and Web version in Synch with each other , ran again and see no obvious errors in the attached log.

Rand it with the Binary settings and without and get the same issue 

 

msedge.log

[Danp2]

It's like your browser isn't responding to the WebSocket commands being sent from the webdriver. I'm not sure how to advise you from here other than to say that this doesn't appear to be an issue with the UDF.

[HighlanderSword]

Hello,

Is there a specific _Base64Decode that your UDF works with ?

I had to manually find one on the autoit site  in order to compile and run the demo

[Danp2]

The function was renamed to __WD_Base64Decode. I recently updated the demo code to fix this issue, but haven't pushed the changes to Github yet.

Just updating the function name should resolve that issue. Sorry for the confusion.