Windows causes FWH crash: msxml3.dll update

[TimStone]

Last night, Microsoft uploaded an update to msxml3.dll and now my programs are erroring out. Specifically, I use the following to send XML texts to a net server.

Code: Select all  Expand view  RUN

Function SendPostToUrl( cUrl, cParams,cContentType,cAuthorization )
    Local oOle,cRet:='',uRet
    default cContentType:="application/x-www-form-urlencoded"
    default cAuthorization:=""
    Try
        oOle := CreateObject( 'MSXML2.XMLHTTP' )
    Catch
        oOle := CreateObject( 'Microsoft.XMLHTTP' )
    End
    oOle:Open( 'POST', cUrl, .f. )
   
    oOle:SetRequestHeader( "Content-Type",cContentType)
    if !empty(cAuthorization)
        oOle:SetRequestHeader( "Authorization",cAuthorization)
    end if
   
    oOle:Send( cParams )
    cRet := oOle:ResponseBody
Return cRet


 

This has worked perfectly for a long time. After the Microsoft update, we get the following error:

Code: Select all  Expand view  RUN

   Error description: (DOS Error -2147352567) WINOLE/1007  The system cannot locate the resource specified.
 (0x800C0005): msxml3.dll
   Args:
     [   1] = C   <carfax-request>
     <license-plate>FRUGAL</license-plate>
     <state>CA</state>
     <vin></vin>
     <product-data-id>38A304F1C16BA41C</product-data-id>
     <location-id>10000</location-id>
</carfax-request>

 

This is now creating a problem for all of my clients. If I turn off the service ( the XML process ), then the application works fine except we can no longer retireve the data.

Does anyone know of a workaround, or have info related to the msxml3.dll current version that we can use to regain SendPostToURL( ) as shared above ? Thank you.

[Antonio Linares]

Dear Tim,

You may consider using CURL instead of it

[TimStone]

I use CURL on most of my other interfaces so I was thinking about making the change ...

For now I wanted to trap the error, so I put the Open() and next steps into a TRY, and if I get an error, the Catch has an error message but returns a NIL value.

Of course, the company I was interfacing with made some changes on their end and it started working again ... which suggests the error may be the result of the website not being reachable, although that usually gives a different error.

Tim