MSXML problem after 11-14 update

After installing the xml update of 11-14 I can no longer access XMLHTTP
through IIS. Any attempts come up with Server.CreateObject Failed Invalid
class string.

This is happening on XP pro, 2000 Advanced Server, 2000 pro, and server
2003, and it is even affecting MSXML3, which should have not been altered by
the update. Please note that MSXML DOMDocument does not appear to be affected
by this, only HTTP.

The dll's are properly registered, and the xmlhttp works using vbscript and
WSH command line. I know it is a permission issue, and have had this happen
before with scripting permission access after an update, but I am lost at
where to look.

In past problems there were registry keys that needed to have permissions
modified, and I tried to add both everyone and IUSR to the xml and xmlhttp
registry class entries, but it hasn't worked.

I installed the latest MSXML3 service pack and that didn't help.

I added NTFS permissions to the DLLs in system32 for everyone and IUSR and
that didn't work.

Please help as this is affecting 2 commercial web servers plus my
development systems.

Thanks

Bill,

Since this is a CRITICAL security update

> Customers in the U.S. and Canada can receive technical support from Microsoft Product
> Support Services at 1-866-PCSAFETY. There is no charge for support calls that are
> associated with security updates.

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============


Bill wrote:

> After installing the xml update of 11-14 I can no longer access XMLHTTP
> through IIS. Any attempts come up with Server.CreateObject Failed Invalid
> class string.
>
> This is happening on XP pro, 2000 Advanced Server, 2000 pro, and server
> 2003, and it is even affecting MSXML3, which should have not been altered by
> the update. Please note that MSXML DOMDocument does not appear to be affected
> by this, only HTTP.
>
> The dll's are properly registered, and the xmlhttp works using vbscript and
> WSH command line. I know it is a permission issue, and have had this happen
> before with scripting permission access after an update, but I am lost at
> where to look.
>
> In past problems there were registry keys that needed to have permissions
> modified, and I tried to add both everyone and IUSR to the xml and xmlhttp
> registry class entries, but it hasn't worked.
>
> I installed the latest MSXML3 service pack and that didn't help.
>
> I added NTFS permissions to the DLLs in system32 for everyone and IUSR and
> that didn't work.
>
> Please help as this is affecting 2 commercial web servers plus my
> development systems.
>
> Thanks

Thanks MowGreen. I will call tomorrow. I cross-postred this incident into the
XML group also. I will post whatever solution I find in both places.

Meanwhile, we all know how a call to MS support can age someone, so if
anyone else has any input on the subject, it would be appreciated.

Bill

"MowGreen [MVP]" wrote:

> Bill,
>
> Since this is a CRITICAL security update
>
> > Customers in the U.S. and Canada can receive technical support from Microsoft Product
> > Support Services at 1-866-PCSAFETY. There is no charge for support calls that are
> > associated with security updates.
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> Bill wrote:
>
> > After installing the xml update of 11-14 I can no longer access XMLHTTP
> > through IIS. Any attempts come up with Server.CreateObject Failed Invalid
> > class string.
> >
> > This is happening on XP pro, 2000 Advanced Server, 2000 pro, and server
> > 2003, and it is even affecting MSXML3, which should have not been altered by
> > the update. Please note that MSXML DOMDocument does not appear to be affected
> > by this, only HTTP.
> >
> > The dll's are properly registered, and the xmlhttp works using vbscript and
> > WSH command line. I know it is a permission issue, and have had this happen
> > before with scripting permission access after an update, but I am lost at
> > where to look.
> >
> > In past problems there were registry keys that needed to have permissions
> > modified, and I tried to add both everyone and IUSR to the xml and xmlhttp
> > registry class entries, but it hasn't worked.
> >
> > I installed the latest MSXML3 service pack and that didn't help.
> >
> > I added NTFS permissions to the DLLs in system32 for everyone and IUSR and
> > that didn't work.
> >
> > Please help as this is affecting 2 commercial web servers plus my
> > development systems.
> >
> > Thanks
>

FWIW, I did call them once and the response was helpful and it did not
take very long. BUT, I did tell them I was an MVP ... not that they knew
what that was

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============

Bill wrote:

> Thanks MowGreen. I will call tomorrow. I cross-postred this incident into the
> XML group also. I will post whatever solution I find in both places.
>
> Meanwhile, we all know how a call to MS support can age someone, so if
> anyone else has any input on the subject, it would be appreciated.
>
> Bill
>
> "MowGreen [MVP]" wrote:
>
>
>>Bill,
>>
>>Since this is a CRITICAL security update
>>
>>
>>>Customers in the U.S. and Canada can receive technical support from Microsoft Product
>>>Support Services at 1-866-PCSAFETY. There is no charge for support calls that are
>>>associated with security updates.
>>
>>MowGreen [MVP 2003-2007]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>Bill wrote:
>>
>>
>>>After installing the xml update of 11-14 I can no longer access XMLHTTP
>>>through IIS. Any attempts come up with Server.CreateObject Failed Invalid
>>>class string.
>>>
>>>This is happening on XP pro, 2000 Advanced Server, 2000 pro, and server
>>>2003, and it is even affecting MSXML3, which should have not been altered by
>>>the update. Please note that MSXML DOMDocument does not appear to be affected
>>>by this, only HTTP.
>>>
>>>The dll's are properly registered, and the xmlhttp works using vbscript and
>>>WSH command line. I know it is a permission issue, and have had this happen
>>>before with scripting permission access after an update, but I am lost at
>>>where to look.
>>>
>>>In past problems there were registry keys that needed to have permissions
>>>modified, and I tried to add both everyone and IUSR to the xml and xmlhttp
>>>registry class entries, but it hasn't worked.
>>>
>>>I installed the latest MSXML3 service pack and that didn't help.
>>>
>>>I added NTFS permissions to the DLLs in system32 for everyone and IUSR and
>>>that didn't work.
>>>
>>>Please help as this is affecting 2 commercial web servers plus my
>>>development systems.
>>>
>>>Thanks
>>