KB832483 Microsoft Data Access Components

[James Anthony]

I've installed this update about 15 times via web update
and automatic. Is there a reason this keeps happening?
I've been trying to figure it out, but I don't understand
it. Any suggestions would be appreciated.

 

[Gordon]

I have exactly the same problem and came to this site
seeking a solution.

 

[IBTerry [MSFT]]

Does this happen on all machines or only a few? What OS is this issue
occuring on?
You might want to test installing the patch manually to see if a useful
error is generated.
If you are running at an MDAC version less than 2.8 try installing 2.8 and
see if this changes the behavior.

IBTerry [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Joseph Moore]

As of last night (Jan 24, 2004), we do seem to have a solution for
this. It has stopped its updating on my test machine.
The thread is here:http://www.experts-exchange.com/Security/Win_Security/Q_20854592.html
Take a look, and hopefully it will help you.

 

[Scott MacLean]

Just a quick warning. My W2K SP4 server, running IIS (with .Net framework)
and MSSQL 2000 has been sitting fat, dumb and happy for months. Immediately
after I installed KB832483, it crashed hard, with:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
(0xc0000005, 0x8046b689, 0x00000000, 0x00000004). Microsoft Windows 2000
[v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini011804-05.dmp.

It was showing the problem was with ntoskrnl.exe. It would bluescreen
consistently within 15 seconds of bootup. Safe mode would boot and run OK.

Last known good configuration did not work, recovery using ERD caused the
server to boot into a non-responsive blue screen. In-place update from the
W2K server CD bluescreened consistently with 0x000000c2 0x00000099
BAD_POOL_CALLER after which point nothing would boot, it would continually
try to restart the install routine.

I ended up having to reformat and reinstall. Thank god for mirrored drives
and backups. On a CLEAN W2K Server install, I installed SP4. The machine ran
fine. I then installed 832483. Right away, my server started locking up
again. This is on an Asus P4S-533 board, 512 megs of DDR-333 RAM, and an
NVidia video card, nothing else strange in the box. I tried swapping the
RAM, power supply and video card, with no result. I rebuilt the server for
the THIRD time, this time purposefully not installing 832483. The server has
been running perfectly ever since. I will NOT be installing 832843 on any
other of my machines, ever.

 

[Kathy.Pfeffer]

-----Original Message-----
I've installed this update about 15 times via web update
and automatic. Is there a reason this keeps happening?
I've been trying to figure it out, but I don't understand
it. Any suggestions would be appreciated.
.

I have the same problem on all the Dell & Compaq pcs here.
If anyone responded to you, can you please share. My email
is (e-mail address removed). Thanks

 

[Brett Grayson]

I am having the same problem on two computers.

 

[Kari [MSFT]]

The patch is for MDAC 2.52, 2.53, 2.62, 2.70, 2.71 or 2.80 so if you want to
upgrade to one of those versions that should fix the problem for you.
Otherwise you will have to ignore the update until the fix is published.

 

[R Dunn]

Unfortunately, this is not a solution to the problem, it is only a
work-around.

We have many in-house applications that require MDAC, but have not been
certified for MDAC 2.8. The problem is not the MDAC version, rather it is
the Windows Update method that determines whether or not the PC requires the
update.

Microsoft, when are you going to have a patch? You said on January 17th
that you were looking into the problem and release an updated version of the
patch. Just curious - we have many users that are receiving automatic
updates daily because of this little glitch in the WU process.

The problem can be replicated, just install 2.6 SP1 MDAC on a clean 2000
box, and hit the Windows Update site, "install the hotfix," reboot, repeat.

Rob