-
-
Notifications
You must be signed in to change notification settings - Fork 498
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
Getting error WebClient.Execute: -2147210493 (11011 / 80042b03), An error occurred during execute #440
Comments
If the only difference between the HTTP and HTTPS urls is the ‘s’ then perhaps it is an SSL handshake problem? Are you running the latest OS? |
Hi zgrose, Sorry, I didn't saw your reply... Yes, I'm running the latest OS. Sometimes I'm also getting an error relating to certificate. But the thing is that, whan I copying the URL to my browser (Chome or IE), the request is correctly processed... Seems like an issue with certificate management in WebClient classes ? |
It's certainly possible. I mostly use the XmlHttpRequest object instead of the WinHTTP API that the WebClient leverages. |
My users are sometimes seeing this error message also. When I try the same macro on my computer, it works. So, the issue is environment dependent. I would like to get this issue solved, but I cannot go to my users computers to test it, so I would just need to find out the most reliable way to make https requests from the macro. The WinHTTP API doesn't seem to be it. |
Experiencing same issue. None of the provided examples seem to be ones that currently run. |
Hi contributors !
I'm getting the following error when trying to execute a GET request using HTTPS protocol
WebClient.Execute: -2147210493 (11011 / 80042b03), An error occurred during execute
[edit] the rest of the error message is the following : -2146885628 (80092004): Impossible de trouver l’objet ou la propriété. (Unable to find object or property)
When using HTTP protocol (and appropriate URL) everything is fine.
Any idea of what I'm doing wrong ?
Many thanks.
The text was updated successfully, but these errors were encountered: