Re: A DLL gone bad ?

Martin wrote:
Some further comments and "wonderings"...

The Component Checker tells me that I have MDAC 2.8 SP1 on this
machine. I've gone through the file manifest for this version
( http://support.microsoft.com/kb/899456 )
and verified that all but one of the files are present and their
version is equal to or higher than what's listed in the manifest.

Do the file versions between the two machines match? Should be easy to
check on. Don't assume because a version is newer on the first PC that it's
"better"; it could be a source of a problem.

The
one missing file (OLEDB32A.DLL) is also missing from the "other"
computer that the programs are working ok on - so I assume this file
is not a factor and perhaps shouldn't even be on the manifest list..

More significantly, the manifest page states: "If you try to run the
MDAC 2.8 SP1 MDAC_TYP.exe file on a computer that is running Windows
XP or Windows Server 2003, installation fails, and you receive an
error message. To update the MDAC version that is installed together
with Windows XP or with Windows Server 2003, you must use operating
system service packs or Windows Update."

Woof, that's an unusual way to state it, even for Microsoft.


So, in order to "fix" this, it looks like I'm going to have to go back
and re-install Service Pack 2 again!? And then all of the various

But ... you DO have XP SP2 installed, right? Are you saying you installed
it, then took it off for some reason?

If you're trying to run XP at SP1 then what does the other computer have for
the XP service packs? If it's SP2, well ... .

OTOH if you think you need to reinstall SP2 over itself, well, it wouldn't
hurt anything, but I'd be surprised if it's the cause of your issues. And
as for post-SP2 fixes, just let AutoUpdate pull them down for you
automatically. It's really no big deal.

updates that have occurred since then? This is going to affect
everything on this computer.

Well, if you aren't updating XP then there could be lots of things that
would "fix" too!

I guess, if both machines you tested on are at the same service pack, and
even if it's SP1, then, you better look into the post-SP1 hot fixes between
the machines. LOTS of changes went on. SP2 is basically nothing but a
compilation of all those post-SP1 hotfixes added to SP1, and called SP2, and
then of course 2 continued on with a bunch more hot fixes.

Best of luck,

Pop`


Can anyone suggest a more "conservative" approach to this problem?



.

Relevant Pages

  • Re: A DLL gone bad ?
    ... version is equal to or higher than what's listed in the manifest. ... MDAC 2.8 SP1 MDAC_TYP.exe file on a computer that is running Windows ...
    (microsoft.public.vb.general.discussion)
  • Re: SMS Administrator Console
    ... Windows XP SP1 and an SMS Admin console that is SP1. ... On certain machines, it always works. ...
    (microsoft.public.sms.admin)
  • Re: SMS Administrator Console
    ... Windows XP SP1 and an SMS Admin console that is SP1. ... On certain machines, it always works. ...
    (microsoft.public.sms.admin)
  • RE: SBS RDC Disconnect during add user wizard
    ... We have seen something similar to this on machines after Windows 2003 ... Server SP1 was installed but the machine was not updated to SBS SP1. ...
    (microsoft.public.windows.server.sbs)
  • Re: SMS Administrator Console
    ... Windows XP SP1 and an SMS Admin console that is SP1. ... On certain machines, it always works. ...
    (microsoft.public.sms.admin)
Loading