title: Recent problems with the MSXML2 library in ASP classic
body: <p>For several years now, we have been able to use MSXML2 to read RSS feeds from third party suppliers without issue. A couple of weeks however, several customers sites suddenly had issues and the feeds could now longer be read. This was done with the library opening the .xml files directly from the third party servers. </p>
  
  <p>The error messages I got were messages like "access denied", "cannot read" or "system error". On one of the occations, the library refused to read the xml file from its original source, but it read it fine if it was moved to another server. However, if I used other libraries in other programming languages, they were able to read the xml from the same third party location MSXML were unable to read it from. It read from this source fine just a few weeks ago. </p>
  
  <p>On the other site, the error message was "access denied", but it was actually able to read the xml file from the third party location. The error was rather that the xml file had "." in the name of element tags, like ". It did read the exact file just fine a few weeks ago. </p>
  
  <p>Anybody know some changes to that library that can have caused this or any other issue that have showed up recently with this library and/or its use?</p>