Forums  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Member List  Search  FAQ  Ticket List  Log Out

 

MDAC Support

 
Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [Networking & Security] >> GFI LANguard >> MDAC Support Page: [1]
Login
Message << Older Topic   Newer Topic >>
MDAC Support - 30.Jan.2004 1:02:00 PM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
Just FYI, MDAC 2.6, 2.7, and 2.8 appear to have been added to the products.xml file pushed out from GFI. It has some updated info/fixes in it compared to what I had before.

eric
Post #: 1
RE: MDAC Support - 2.Feb.2004 10:18:00 AM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
2.5 has supposedly been added too, haven't had a chance to verify that yet though.

eric

(in reply to xnih)
Post #: 2
RE: MDAC Support - 16.Feb.2004 10:50:00 AM   
scottf51

 

Posts: 21
Joined: 18.Jan.2004
Status: offline
It does not detect MDAC as an installed product of any of my XP machines

Is it possible that this is another of the SP1a issues ?

XP Pro SP1a English, with all patches MDAC 2.7 SP1 with newest patch installed.

(in reply to xnih)
Post #: 3
RE: MDAC Support - 16.Feb.2004 11:14:00 AM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
will check, have a laptop here at home with XP on it (holiday today and all here in the US). Will see if it is detecting on mine here.

Also, make sure you have it set to autodownload the latest info from GFI too.

Look in the products.xml file and verify that there is info about MDAC in there, if there isn't you aren't pulling the latest mssecure and other stuff from GFI.

Also, please check your registry and see about the following keys:

SOFTWARE\Classes\MDACVer.Version.2.50" RegKey=""
SOFTWARE\Classes\MDACVer.Version.2.60" RegKey=""
SOFTWARE\Classes\MDACVer.Version.2.70" RegKey=""
SOFTWARE\Classes\MDACVer.Version.2.80" RegKey=""
SOFTWARE\Classes\MDACVer.Version.2.90" RegKey=""

The above are what is being looked for.

eric

[ February 16, 2004, 05:15 PM: Message edited by: xnih ]

(in reply to xnih)
Post #: 4
RE: MDAC Support - 16.Feb.2004 11:35:00 AM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
MDAC 2.7 SP1 is what shows up on my XP SP1 box, but don't have an SP1a box here, so it could be that the registry keys on XP1a are a bit different, so check for what MDAC key, if any shows up on your box(es).

eric

(in reply to xnih)
Post #: 5
RE: MDAC Support - 16.Feb.2004 5:29:00 PM   
ccowling

 

Posts: 4
Joined: 15.Feb.2004
Status: offline
Hi all,
I find that I have several versions of MDAC running and thought I would update them all to 2.8. I can't seem to push this out as a custom patch. Has anyone tried this? I've tried the supplied MS parameters as well as /q and also the MS suggested: mdac_type /q /c:"setup /qnt"
No luck so far. I have a preview copy of another tool that seems to work pushing these out so it can be done. (The other tool does not have the good scanning features though.)

(in reply to xnih)
Post #: 6
RE: MDAC Support - 16.Feb.2004 9:25:00 PM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
I just downloaded mdac_typ.exe (for 2.8) set it up as a custom patch, pushed it to my 2000 box with the options of:

/q /c:"setup /qnt"

and that worked fine on 2 machines so far.

Just made sure I set it to reboot afterwards so I knew it was done (took awhile to do the install).

But a normal /q alone is not enough, because it prompts you to answer some questions.

So not sure what the problem was when you tried it before, all I can say is try again since it worked for me.

eric

(in reply to xnih)
Post #: 7
RE: MDAC Support - 17.Feb.2004 7:40:00 PM   
ccowling

 

Posts: 4
Joined: 15.Feb.2004
Status: offline
OK, I found the problem. I had made a folder under the \download folder called CustomPatches\MDAC\28 and put the mdac_typ.exe there to keep them straight (all the versions have the exact same name). There was a mdac_typ.exe in the download folder and it was a patch or update to an earlier version 2.5 (why MS calls them all the same name I don't know). Even though I was calling my patch from the proper directory, each time it was getting the one from the download directory by default. When I deleted the one from the download directory it copied the proper one to the workstation and everything worked.
The problem is that it also copied the file into the download directory. I think that will end up upgrading every mdac up to 2.8 (due to that crazy naming convention that MS is using for this patch/upgrade) and I may not want to do that without a lot more testing.
Seems like the custom patch section has a little unexpected behavoir. OK once you know about it but it took a little time to figure out. I suppose it only will effect patches that have the same name no what version of product they are patching; I hope that is rare. [Wink]

(in reply to xnih)
Post #: 8
RE: MDAC Support - 18.Feb.2004 4:39:00 AM   
scottf51

 

Posts: 21
Joined: 18.Jan.2004
Status: offline
That would be the problem then, apparently SP1a machines have MDAC 2.71

My registry entry is

"SOFTWARE\Classes\MDACVer.Version.2.71"

I am not usre if my machines are even SP1a, they are just installed using our volume licencing disk that specifies it has SP1 installed. It shows "version build 2600.xpsp2.030422-1633 : service pack 1"

Using the microsoft component checker tool it seems to find some files from what it calls "mdac 2.7 SP1 refresh" as well as the normal ones, at least I think thats what the tool is saying.

whats the betting lots my file versions are different, I can feel a headache coming on [Wink]

By the way Eric, you are famous, you are being mentioned on the patch management mailing list

http://marc.theaimsgroup.com/?l=patchmanagement&m=107704025516076&w=2

[Smile]

Scott

[ February 18, 2004, 12:48 PM: Message edited by: scottf51 ]

(in reply to xnih)
Post #: 9
RE: MDAC Support - 18.Feb.2004 8:42:00 AM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
will see what we can do on the 2.71 thing here in a bit.

eric

(in reply to xnih)
Post #: 10
RE: MDAC Support - 18.Feb.2004 9:06:00 AM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
scottf51,

a quick fix for your issue would be to modify the products.xml, change the following area:

<Product ProductID="146" ProductName="MDAC 2.7" UseOSServicePack="0" GOLDServicePackID="191" DeterminedServicePack="0" DeterminedProductName="">
<Tests>
<Test Type="p" RegPath="SOFTWARE\Classes\MDACVer.Version.2.70" RegKey="" RegValue=""/>
<Test Type="!p" RegPath="SOFTWARE\Classes\MDACVer.Version.2.80" RegKey="" RegValue=""/></Tests>
<ServicePacks>
<ServicePack ID="239" Number="1" Name="Service Pack 1" FileName="MDAC_TYP.EXE" URL="http://download.microsoft.com/download/3/b/f/3bf74b01-16ba-472d-9a8c-42b2b4fa0d76/mdac_typ.exe" SilentInstall="0" Dependencies="">
<Tests>
<Test Type="c" RegPath="Software\Microsoft\DataAccess" RegKey="Version" RegValue="2.71"/>
</Tests>
</ServicePack>
</ServicePacks>
</Product>

-------
So change test type from:

<Test Type="p" RegPath="SOFTWARE\Classes\MDACVer.Version.2.70" RegKey="" RegValue=""/>

to:

<Test Type="c" RegPath="SOFTWARE\Classes\MDACVer.Version.2.7" RegKey="" RegValue=""/>

Also, since it is apparently already SP1 of MDAC 2.7, what is the registry info for here:

HKLM\SOFTWARE\Microsoft\DataAccess

RegKey="Version" RegValue="2.71"

thanks,

eric

(in reply to xnih)
Post #: 11
RE: MDAC Support - 18.Feb.2004 9:35:00 AM   
scottf51

 

Posts: 21
Joined: 18.Jan.2004
Status: offline
Thanks for the reply,

My registry info under

HKLM\SOFTWARE\Microsoft\DataAccess
is
version = "2.71.9030.0"

I will try what you suggested as a quick fix, I had just been checking the XML file and was about to make some tweaks after checking the file using XMLSPY. I just thought I would mention the problem cause I am sure that other people must ne having it and if nobody mentions it, it will never get fixed.

Thanks

Scott

(in reply to xnih)
Post #: 12
RE: MDAC Support - 18.Feb.2004 10:04:00 AM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
Just got an email from the person in charge of updating the file, should be fixed in GFI's stuff here any time (unless he finds something wrong and decides not to update it). So make sure you have LNSS set to autodownload updates and restart it here in the next 30 mins or so, it should be updated by then according to the email I just got.

eric

(in reply to xnih)
Post #: 13
RE: MDAC Support - 18.Feb.2004 10:06:00 AM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
actually already updated:

<Test Type="p" RegPath="SOFTWARE\Classes\MDACVer.Version.2.70 | SOFTWARE\Classes\MDACVer.Version.2.71" RegKey="" RegValue="" />

he ended up doing it a little different, but this way it does exact lookups for both keys, instead of a generic lookup.

So restart LNSS and let me know if it works for you.

eric

(in reply to xnih)
Post #: 14
RE: MDAC Support - 19.Feb.2004 4:14:00 AM   
scottf51

 

Posts: 21
Joined: 18.Jan.2004
Status: offline
Well it seems like it is working, just hope when I do any further upgrades I won't end up with different version numbers from you guys again. I guess at SP2 we should all end up with the same versions for all files if I am lucky [Smile]

Thanks for your help

Scott

(in reply to xnih)
Post #: 15
Page:   [1]
All Forums >> [Networking & Security] >> GFI LANguard >> MDAC Support Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts