>Thanks again Antonio.
>
>I notice there's no download for MSXML3 (probably why I skipped over it in my searching), just MSXML6, but I guess I should be using MSXML6 anyway if that works. I've swapped the code ref and I get the exact same error using CREATEOBJECT("MSXML2.ServerXMLHTTP.6.0") anyway. I'm presuming this explicit version reference works - it doesn't throw an error running from my desktop...
>
>It seems odd to me that both DLLs would be corrupted (MSXML3.DLL and MSXML6.DLL), but I don't have anything else to try, so I'll download and reinstall at a quiet time. I tried running the same exe from another Win 2008 R2 server and it ran fine so I guess that supports your theory...

Here's something from my notes:

*[2016/02/08 18:59] ndragan - fixing this for the last time... the 4.0 has the insane security bug.
* because when it is not involved in any HTTP, the selected URL has a bad certificate :facepalm: unless you're admin, then it's ok.
* THIS.ODOM=CREATEOBJECT("MSXML2.DOMDocument.4.0")
This.Odom=Createobject("Microsoft.XMLDOM")

The versionless call goes for some old version, probably back from NT4 or some such, when they didn't think that security should complicate our lives at every step. That just worked for me. Now since you're dealing with HTTP here, this may not be related at all. I'm just throwing it in as a hunch.

nb. The first line of comments is not meant to mention any insane bug about security, it's just a bug caused by insane security.