Hotfix for MSXML 4.0 Service Pack 2 - KB832414
Bob@DPS
hot fix to 1400 machines.
Bob@DPS
machines.
Lawrence Garvin (MVP)
news:8299BA1C-4CBB-441C...@microsoft.com...
> When will this hot fix be included in WSUS updates? I need to deploy this
> hot fix to 1400 machines.
The documentation in the KB832414 article implies that the package was never
released to SUS. WSUS was not in existence at the time of release of this
package. And, the chain of updates superceding the cause of this issue is
long enough that the entire content package is probably obsoleted several
times over by now, which would also explain its absence in the WSUS content
catalog.
If you follow the links in KB832414 for the instructions on how to obtain
the content, you'll find it leads you to KB887606. This is because, 832414
is superceded by 887606.
In KB887606, (dated 7/8/05, btw, so this is not a 'new' issue -- in fact,
the KB points out that the issue is caused by MS04-004 -- a Cumulative
Security Update to Internet Explorer), the 'fix' is noted as applicable to
MSXML 2.6 and MSXML 4.0 SP2 installations. The MSXML 3.0 installations
require the application of MSXML 3.0 SP5 (or, by inference, the installation
of MDAC 2.8 SP1).
IE6.0 installs MSXML 3.0 SP2, IE6SP1 installs MSXML 3.0 SP3, MDAC 2.8
installs MSXML 3.0 SP4, and MDAC 2.8 SP1 installs MSXML 3.0 SP7. It's quite
likely that this hotfix doesn't even apply to your systems, for one of a
couple of reasons that come immediately to mind:
(a) You've upgraded to IE6 and have MSXML 3.0 installed, thus requiring
application of SP5, not the hotfix.
(b) The original 'bug' has probably been fixed in one of the dozen
'updates' released since MS04-004.
MS04-004 was released via WSUS as KB832894, which was superceded by KB867801
(MS04-025).
KB867801 was superceded by KB834707 (MS04-038).
KB834707 was superceded by KB867282 (MS05-014).
KB867282 was superceded by KB890923 (MS05-020).
KB890923 was superceded by KB883939 (MS05-025).
KB883939 was superceded by KB896727 (MS05-038).
KB896727 was superceded by KB896688 (MS05-052).
KB896688 was superceded by KB905915 (MS05-054).
KB905915 was superceded by KB912812 (MS06-013).
KB912812 was superceded by KB916281 (MS06-021) and is the current
Cumulative Security Update for Internet Explorer.
Even if the hotfix did apply, it seems it would be preferable to upgrade to
IE6SP1, apply MS06-021, and install MDAC 2.8 SP1,
rather than continue to use IE5 w/MSXML 2.x, which would seem to be the only
scenario in which this update would be applicable today.
In addition, this hotfix also requires the installation of MS04-038, which
has been superceded a gazillion times, as that update is a Cumulative
Security Update for Internet Explorer. The current update for IE5.5 would be
KB905915 (MS05-054), but also note that IE5.5 is no longer a supported
browser, so 'fixing' that environment really won't get you much.
Either way, I'm challenged to think that none of those six Cumulative
Security Updates in 2005 didn't entirely resolve this 'bug'.
--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
....
Bob@DPS
problem that dates back to 2004. My experience this past week is that we
have an aplication that causes and MSXML4 error that is corretced when the
hot fix to msxml4 SP2 (KB832414) is applied. We are using IE version
6.0.2900.2180 SP2 with all of the latest updates. A couple of questions:
1) Do updates for MSXML2 or MSXML3 apply to MSXML4?
2) Wahat does teh hotfix do besides repalced the msxml4.dll? Are there
registery settings or other changes that may explain why the hot fix fixes
our problem with MSXML4?
Thanks
Bob
"Lawrence Garvin (MVP)" wrote:
> .....
>
>
>
>
Lawrence Garvin (MVP)
> Apparently your know the history of the changes with regard to the
> original
> problem that dates back to 2004.
No.... actually I spent about 20 minutes researching the history. :-)
> My experience this past week is that we
> have an aplication that causes and MSXML4 error that is corretced when the
> hot fix to msxml4 SP2 (KB832414) is applied. We are using IE version
> 6.0.2900.2180 SP2 with all of the latest updates.
Something else upgraded your MSXML 3.0 to MSXML 4.0. I hadn't really
considered that the core issue might be MSXML4.
> 1) Do updates for MSXML2 or MSXML3 apply to MSXML4?
Everything I saw, in the 20 minutes I dug through the history, is that the
update applies to MSXML2 and MSXML4, but not MSXML3. The latter /requires/
application of the SP.
It's hard to say about other updates, since there don't seem to be any.
MSXML 2.6 is the last version of the MSXML2 chain; SP2 is the latest SP for
the MSXML4 chain. Only MSXML3 seems to have been regularly updated, but
apparently only through service packs, as noted in my previous reply.
> 2) Wahat does teh hotfix do besides repalced the msxml4.dll? Are there
> registery settings or other changes that may explain why the hot fix fixes
> our problem with MSXML4?
According to the KB article(s) I read, all it does is update the DLL;
however, I've never seen a KB article document registry changes, if there
are any.
As for why it fixes your MSXML4 issue, I believe that's probably because
nothing else in the chain of updates affects MSXML4. All of the IE6 updates
would have only updated MSXML3 installations.
Honestly, I don't even know what the original source(s) for MSXML4 are! I'm
suspecting they might be Office 2003, and if so, it's possible that the
'fix' is also contained in an Office service pack. I'll have to track the
answer to that question down when I get an extra moment. (You may already
know, of course, since you do have the MSXML4 installed.)
I just looked in the SYSTEM folder of my notebook, and I see MSXML2, MSXML3,
MSXML4, and MSXML6 library files present, as well as an MSXML.DLL which
shows itself as a v8.0 file. Apparently the various versions can coexist
side-by-side. I think my MSXML6 installation is coming from .NET Framework
v2.0 and/or SQL Server.
Bob@DPS
the fact that we need this update, could it be possible that this hot fix be
made into to an MSI file so we could deploy it using group policy?
"Lawrence Garvin (MVP)" wrote:
> .....
Lawrence Garvin (MVP)
> We are using a non-Microsoft application that uses the MSXML4 files.
> Given
> the fact that we need this update, could it be possible that this hot fix
> be
> made into to an MSI file so we could deploy it using group policy?
That would be a question you'd have to direct to Microsoft, or somebody
adept at hacking EXE updates into MSI packages... but I tend to doubt it.
btw.. EXE packages /can/ be distributed/published/installed using
Intellimirror and Group Policy. It does not have to be an MSI package to do
this.