Jump to content

Issues with Windows 10 and winhttprequest.5.1


Recommended Posts

Hi Guys,

I am having an issue with multiple Windows 10 systems (actually all systems running Windows 10 running the same script have this issue) I have a script which calls the winhttp.winhttprequest.5.1 object and allows me to get sites HTML source, I am using multiple Open commands on the same object which I didn't assume would be an issue.

The issue I am getting is quite often the Send command to the object will fail (in fact I have not been able to finish running the script because it fails everytime) with an Error

472) : ==> The requested action with this object has failed.:
$plus7ep.Send()
$plus7ep^ ERROR
>Exit code: 1    Time: 312.5

Now this exact code was working fine in Windows 8/8.1 and Windows 7 before I upgraded the systems to Windows 10, anybody know what's going on here?

P.S when I say I use multiple Open and Send commands I mean I have two instances of winhttprequest objects open and it probably does a total of about 600 Open and Sends but as I mentioned this had never been an issue until Windows 10.

Link to comment
Share on other sites

Hi Danp2,

Thanks for your reply, ok so it appears as though the winhttprequest Send command is not getting the information in time for it to send it from the Open command even though the Open option to wait until all information has been received before allowing it to send it still seems to be lagging behind as I mentioned what is interesting is this issue doesn't happen in Windows 7 or 8/8.1 and has only just reared its head on Windows 10.

Error message is as follows:

COM Error intercepted !
    err.number is:         0x80020009
    err.windescription:    Exception occurred.

    err.description is:     The data necessary to complete this operation is not yet available.

    err.source is:         WinHttp.WinHttpRequest
    err.helpfile is:     
    err.helpcontext is:     0
    err.lastdllerror is:     0
    err.scriptline is:     486
    err.retcode is:     0x8000000A

 perhaps I put a catch for this particular error and make the script sleep for a couple of seconds then try send again, thoughts?

could this be a bug with AutoIT and Windows 10?

Cheers,

 

Edited by Rampantshadow
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...