I've installed the 832483 MDAC fix on an SBS 4.5 system (MDAC 2.8), but
WinUp is still reporting that I have to install the fix. Either the fix
isn't installing properly or WinUp isn't seeing the installed fix. How can I
rectify this?

GaryK

Gary,
Many people are reporting a similar problem with KB828026. Did you manage
to install KB828026 (see "View installation history")?
Derek Nicholson


"Gary Karasik" <gkarasik2fea.net> wrote in message
news:OK2Roq39DHA.2308@TK2MSFTNGP09.phx.gbl...

I have INSTALLED KB828026 THREE TIMES ans I am STLL GETTING the balloon telling me I have to update Media Player...I have tried the "fixes"...none seem to work. WHY won't MS FIX THIS...or at least FIND A PATCH that will end this craziness!!? Can someone please help?....Starchild
"Derek" <FredFlintstone@hotmail.com> wrote in message news:4035d405$0$781$ba620e4c@news.skynet.be...

Thanks, Derek.

Yes, 828026 is installed.

Re 832483, via Google I did see other posts about this. Several posts say
they were able to fix this on Win2K machines by manually installing MDAC
2.8, then installing the update, but this approach didn't work on my NT4
box.

GaryK

"Derek" <FredFlintstone@hotmail.com> wrote in message
news:4035d405$0$781$ba620e4c@news.skynet.be...

Gary,

Look at 837188 on MS KB. It details the problem.

Chris Wood
Alberta Department of Energy
CANADA

"Gary Karasik" <gkarasik2fea.net> wrote in message
news:OK2Roq39DHA.2308@TK2MSFTNGP09.phx.gbl...

Thanks for the reference, Chris. It didn't solve the problem.

GaryK

"Chris Wood" <chris.wood@gov.ab.ca> wrote in message
news:#XMIbN#9DHA.1268@TK2MSFTNGP12.phx.gbl...

Gary..did you you try uninstalling the update from add / remove
programs, then manually downloading the fix from the windows update
catalog and installing it manually? If so then sorry for the duplicate
suggestion.

Gary Karasik wrote:
--

Hilary

Remove DELETE from email address to message me

Thanks, Hilary. I can't find any entry for 832483 in Add-Remove Programs.
The "details" section of the update info says, "Once installed, the update
cannot be removed."

GaryK

"Hilary" <hilarykarp@comcast.delete.net> wrote in message
news:eWqI8FD#DHA.3812@TK2MSFTNGP09.phx.gbl...

Gary,
The entry for 832483 is not listed with the other KB hotfixes in the
ADD/Remove Listing but under Internet Explorer Q832483.
Derek

"Gary Karasik" <gkarasik2fea.net> wrote in message
news:O1ejfGE%23DHA.3176@TK2MSFTNGP11.phx.gbl...

Sorry Gary, I got the number wrong the entry I saw was in fact Internet
Explorer Q832894 and not 832483.
Derek

"Derek" <FredFlintstone@hotmail.com> wrote in message
news:40371e94$0$320$ba620e4c@news.skynet.be...

I have been having this same issue on an NT4 system (SP6A) - the 832483
update appears to go through its cycle successfully, but every time I check
on the Windows Update site the update is still presented.

I took the liberty of downloading the fix, and after I'd downloaded it I
looked at the executable with "WinZip" to see what was in it. I found
something interesting: there are "*.cat" and "*.inf" entries for
Windows2000, WindowsMillenium, WindowsXP, but the entry for NT4 is referred
to as "DLvl". It looks like it should work, but doesn't. I checked the
versions of the various "odbc" DLLs before and after running the fix, and
there is no change. The registry key does get written to the registry,
though.

Installing this update "by hand" may be the only option. This will have two
objectives: one, to actually install the correct DLLs so as to close the
security leak, and two, to make it so the update doesn't show up on the
"windows update" site (signifying a successful install).

I'll post back with the results.

YC


"Gary Karasik" <gkarasik2fea.net> wrote in message
news:OxBEg8B%23DHA.3808@TK2MSFTNGP09.phx.gbl...

Yes, please.

I've tried and continue to try a few things too. I'll also post back with
the results.

GaryK

"Young Coot" <reply@newsgroup.OnlyPlease> wrote in message
news:ulBVRYX#DHA.2212@TK2MSFTNGP10.phx.gbl...

My NT4/SP6a system is loaded with MDAC28. Following up on your thought, I
just looked at an unzipped version of the MDAC fix. Apart from a couple of
files (ODBCDBP_280.DLL and SQLSVR32_280.DLL, both of which, after renaming
them, I substitutes for the equivalent MDAC28 files in /SYSTEM32 (and which
didn't fix the problem), I can't figure out which of the other files go
where. Maybe you'll see something I didn't.

GaryK


"Young Coot" <reply@newsgroup.OnlyPlease> wrote in message
news:ulBVRYX#DHA.2212@TK2MSFTNGP10.phx.gbl...

For starters, here's what was in my "dahotfix.log" file:

***
[18:07:05]: Welcome to the Microsoft Data Access Components Hotfix
Installer.
[18:07:05]: Windows Version Information:
Type: WinNT/2000/XP
Version: 4.0 (Service Pack: 6 ("Service Pack 6"))
Terminal Services: No
MUI Enabled: No
[18:07:05]: Parsing Command Line options.
[18:07:05]: Opening .ini file: C:\TEMP\IXP000.TMP\dahotfix.ini
[18:07:05]: Loading System Setup Engine (SETUPAPI.DLL)
[18:07:05]: Checking system dependencies.
[18:07:05]: Processing .ini file data and building job list.
[18:07:05]: Initializing Job Queues.
Job queue root: SOFTWARE\Microsoft\DataAccess\dahotfix
[18:07:05]: The registry value (SOFTWARE\Microsoft\Windows\CurrentVersion,
"CommonFilesDir") was found. Setting the directory path to "C:\Program
Files\Common Files".
[18:07:05]: Job #1 added to job list.
[18:07:05]: The registry value (SOFTWARE\Microsoft\Windows\CurrentVersion,
"CommonFilesDir") was found. Setting the directory path to "C:\Program
Files\Common Files".
[18:07:05]: Job #2 added to job list.
[18:07:05]: The registry value (SOFTWARE\Microsoft\Windows\CurrentVersion,
"CommonFilesDir") was found. Setting the directory path to "C:\Program
Files\Common Files".
[18:07:06]: Job #3 added to job list.
[18:07:06]: The registry value (SOFTWARE\Microsoft\Windows\CurrentVersion,
"CommonFilesDir") was found. Setting the directory path to "C:\Program
Files\Common Files".
[18:07:06]: Job #4 added to job list.
[18:07:06]: The registry value (SOFTWARE\Microsoft\Windows\CurrentVersion,
"CommonFilesDir") was found. Setting the directory path to "C:\Program
Files\Common Files".
[18:07:06]: Job #5 added to job list.
[18:07:06]: The registry value (SOFTWARE\Microsoft\Windows\CurrentVersion,
"CommonFilesDir") was found. Setting the directory path to "C:\Program
Files\Common Files".
[18:07:06]: Job #6 added to job list.
[18:07:06]: Standard user interface mode enabled. Creating user interface
components.
[18:07:06]: Creating Main Dialog.
[18:07:06]: Setting Main Dialog visible.
[18:07:06]: Beginning Windows Message Pump.
[18:07:10]: Creating worker thread to handle installation of files.
[18:07:10]: Executing PreInstallActions for package.
[18:07:10]: Loading function (CheckMDACVersionExact) from internal function
list.
[18:07:10]: 2.52,false[18:07:10]: Checking version of Microsoft Data Access
Components that is currently installed on the machine.
[18:07:10]: An error occurred while setup was trying to verify the version
of Microsoft Data Access Components current installed on the machine.
Either the version currently installed does not match the version of this
hotfix package, or setup was unable to determine the version currently
installed.
[18:07:10]: The action (NULL!CheckMDACVersionExact) returned FALSE.
Either all of the PreInstallActions for this package returned FALSE, or
there was a fatal error while executing an action.
The package will not be installed. This error will not halt the setup
process.
[18:07:10]: Executing PreInstallActions for package.
[18:07:10]: Loading function (CheckMDACVersionExact) from internal function
list.
[18:07:10]: 2.53,false[18:07:10]: Checking version of Microsoft Data Access
Components that is currently installed on the machine.
[18:07:10]: An error occurred while setup was trying to verify the version
of Microsoft Data Access Components current installed on the machine.
Either the version currently installed does not match the version of this
hotfix package, or setup was unable to determine the version currently
installed.
[18:07:10]: The action (NULL!CheckMDACVersionExact) returned FALSE.
Either all of the PreInstallActions for this package returned FALSE, or
there was a fatal error while executing an action.
The package will not be installed. This error will not halt the setup
process.
[18:07:10]: Executing PreInstallActions for package.
[18:07:10]: Loading function (CheckMDACVersionExact) from internal function
list.
[18:07:10]: 2.62,false[18:07:10]: Checking version of Microsoft Data Access
Components that is currently installed on the machine.
[18:07:10]: An error occurred while setup was trying to verify the version
of Microsoft Data Access Components current installed on the machine.
Either the version currently installed does not match the version of this
hotfix package, or setup was unable to determine the version currently
installed.
[18:07:10]: The action (NULL!CheckMDACVersionExact) returned FALSE.
Either all of the PreInstallActions for this package returned FALSE, or
there was a fatal error while executing an action.
The package will not be installed. This error will not halt the setup
process.
[18:07:10]: Executing PreInstallActions for package.
[18:07:10]: Loading function (CheckMDACVersionExact) from internal function
list.
[18:07:10]: 2.70,false[18:07:10]: Checking version of Microsoft Data Access
Components that is currently installed on the machine.
[18:07:10]: The action (NULL!CheckMDACVersionExact) returned TRUE.
[18:07:10]: Loading function (AllOrNoneFileByFileVersionCheck) from internal
function list.
[18:07:10]: Checking if any of the package files are already installed on
this machine.
[18:07:10]: Opening .inf file: C:\TEMP\IXP000.TMP\Q832483_270_DLvl.inf
Version check passed for Target file : C:\WINNT\System32\DBnetlib.dll
version:[ version:[2000.81.9002.0]
...against Source file version:[2000.81.9002.0]
Version check passed for Target file : C:\WINNT\System32\ODBC32.dll
version:[ version:[3.520.9002.0]
...against Source file version:[3.520.9002.0]
Version check passed for Target file : C:\WINNT\System32\odbcbcp.dll
version:[ version:[2000.81.9002.0]
...against Source file version:[2000.81.9002.0]
Version check passed for Target file : C:\WINNT\System32\ODBCCP32.dll
version:[ version:[3.520.9002.0]
...against Source file version:[3.520.9002.0]
Version check passed for Target file : C:\WINNT\System32\SQLSRV32.dll
version:[ version:[2000.81.9002.0]
...against Source file version:[2000.81.9002.0]
Version check passed for Target file : C:\Program Files\Common
Files\System\ole db\oledb32.dll version:[ version:[2.70.9002.0]
...against Source file version:[2.70.9002.0]
Version check passed for Target file : C:\Program Files\Common
Files\System\ole db\sqloledb.dll version:[ version:[2000.81.9002.0]
...against Source file version:[2000.81.9002.0]
[18:07:10]: The action (NULL!AllOrNoneFileByFileVersionCheck) returned TRUE.
[18:07:10]: Installing the inf: C:\TEMP\IXP000.TMP\Q832483_270_DLvl.inf.
[18:07:10]: File copy complete:
Source file: C
TargetFile: C
[18:07:10]: File copy complete:
Source file: C
TargetFile: C
[18:07:10]: File copy complete:
Source file: C
TargetFile: C
[18:07:10]: File copy complete:
Source file: C
TargetFile: C
[18:07:10]: File copy complete:
Source file: C
TargetFile: C
[18:07:10]: File copy complete:
Source file: C
TargetFile: C
[18:07:10]: File copy complete:
Source file: C
TargetFile: C
[18:07:10]: Executing PreInstallActions for package.
[18:07:10]: Loading function (CheckMDACVersionExact) from internal function
list.
[18:07:10]: 2.71,false[18:07:10]: Checking version of Microsoft Data Access
Components that is currently installed on the machine.
[18:07:10]: An error occurred while setup was trying to verify the version
of Microsoft Data Access Components current installed on the machine.
Either the version currently installed does not match the version of this
hotfix package, or setup was unable to determine the version currently
installed.
[18:07:10]: The action (NULL!CheckMDACVersionExact) returned FALSE.
Either all of the PreInstallActions for this package returned FALSE, or
there was a fatal error while executing an action.
The package will not be installed. This error will not halt the setup
process.
[18:07:10]: Executing PreInstallActions for package.
[18:07:10]: Loading function (CheckMDACVersionExact) from internal function
list.
[18:07:10]: 2.80,false[18:07:10]: Checking version of Microsoft Data Access
Components that is currently installed on the machine.
[18:07:10]: An error occurred while setup was trying to verify the version
of Microsoft Data Access Components current installed on the machine.
Either the version currently installed does not match the version of this
hotfix package, or setup was unable to determine the version currently
installed.
[18:07:10]: The action (NULL!CheckMDACVersionExact) returned FALSE.
Either all of the PreInstallActions for this package returned FALSE, or
there was a fatal error while executing an action.
The package will not be installed. This error will not halt the setup
process.
[18:07:10]: Destroying Job Queues.
[18:07:12]: Ending Windows Message Pump.
[18:07:12]: Destroying Main Dialog.
[18:07:12]: Checking state of setup at end of installation.
Setup was successful.
[18:07:12]: Shutting down Hotfix Installer.

***

I note that the only version of MDAC that registered positively was 2.70.
The setup is pronounced successful and the registry key is in place. The
DLLs mentioned are indeed upgraded. Apparently the fix has been applied, but
the "Windows Update" site seems to be looking for something else besides
these things.

Looking in "wuhistv3.log", I see that the earlier version of 832483, dated
January 15 of 2004, was successful and didn't keep repeating. The February
version is the one that is giving trouble.

Next step is to find the key that the Windows Update is looking for and make
the necessary addition/correction. More as it develops.

YC

"Gary Karasik" <gkarasik2fea.net> wrote in message
news:Ote3prX%23DHA.3220@TK2MSFTNGP10.phx.gbl...

In my case it's 2.8, but otherwise ditto. On a Win2K server where the hotfix
successfully installed and doesn't come back as uninstalled, the only reg
entry I could find is under
HKLM\Software\Microsoft\Updates\DataAccess\Q832483 . The same entry exists in
the NT4 registry.

GaryK

"Young Coot" <reply@newsgroup.OnlyPlease> wrote in message
news:ewMJ4ZY#DHA.220@TK2MSFTNGP09.phx.gbl...

I updated the data access components to 2.8 on my NT4 machine to see if that
would help. No joy - after running the update successfully, with all DLLs
properly updated, the fix still shows on Windows Update.

Here's something for comparison, Gary: in my registry, there is another
registry key where data access info is stored:

HKLM\Software\Microsoft\DataAccess

The keys are as follows right now:

Full21Install = 0xffffffff(4294967295)
FullInstallVer = 2.80.1022.3
IE5_Version = 02.10.3711.3
RollbackVersion = 2.80.1022.3
SavedRollbackVersion = 2.70.9001.0
Version = 2.80.1022.3

On the machine that had the successful install, could you compare this
listing with what you might have in the registry? Might be a clue there.

YC



"Gary Karasik" <gkarasik2fea.net> wrote in message
news:uov0r7Z%23DHA.2316@TK2MSFTNGP11.phx.gbl...

Exactly the same except:
IE5_Version=0.0.0.0 (the machine has (IE6/SP1)
SavedRollbackVersion=2.80.1022.3

Ditton on the NT4 machine except:
SavedRollbackVersion=2.50.4403.9

GaryK

"Young Coot" <reply@newsgroup.OnlyPlease> wrote in message
news:#azM7Dd#DHA.452@TK2MSFTNGP11.phx.gbl...

I just ran "hfnetchk" from the command line, figuring that if there was some
file or part of this update that wasn't installed correctly that the readout
would tell me. No mention of 832483 anywhere in the readout. At least I
have verification that the update really did "take" even though the Windows
Update site tells me otherwise.

When thinking about what file(s) the WindowsUpdate site looks for when
figuring out what to display and what not, I remembered the following
registry key:

HKLM\Software\Microsoft\Acive Setup\Installed Components

There are several keys under this with the cryptic MS "clsid" string, and
most of them carry a description of what update has been installed. Some do
not. At any rate, I scrolled through each one of them looking for signs of
this MDAC update. Nothing mentioned.

This may be a shot in the dark, Gary, but if you could check the registry
keys on the machine that had a successful install and see if any of them
mention 832483? Might prove fruitful, might not, but it's worth a try in
the absence of other ideas.

YC


"Gary Karasik" <gkarasik2fea.net> wrote in message
news:%23L8yxsd%23DHA.3068@tk2msftngp13.phx.gbl...

Good idea, but no joy. The only mention of 832483 in the registry is under
HKLM/Software/Microsoft/Updates/DataAccess/Q832483, and the same key is in
the NT4 registry. I even tried copying/pasting from one reg to the other.

Tomorrow I'm going to call PSS and log a case. I'm deeply concerned that
they're going to put out a fix for this that doesn't include NT4.

GaryK

"Young Coot" <reply@newsgroup.OnlyPlease> wrote in message
news:OY$YKso#DHA.2512@TK2MSFTNGP11.phx.gbl...

You are probably right about that; MS is probably not keen on even hinting
that they are continuing to support NT4, even for something like this.

YC

"Gary Karasik" <gkarasik2fea.net> wrote in message
news:ebNbtFp%23DHA.3536@TK2MSFTNGP10.phx.gbl...