man I hate MDAC!
-
I spent the last two days, literally, on the phone trying to get a user's MDAC installed correctly, if there is such a thing, since I've never ran Component Checker on a machine and ended up without any mismatchs whatsoever. This particular user was running W2K SP4; last quarter the software was working, yet once the user updated to the current quarter the software started bombing saying that MDAC 2.6 or above is required, so something must have happened over the course of the quarter. Component Checker, however, said MDAC 2.8 was installed, yet a whole mess of dll files had versions not corresponding to 2.8, particularly the oledb32.dll file, and all bets are off if this file is jacked! To top things off, it seems that the MDAC 2.8 installation does not do anything, yet still says "installation complete", if it detects that MDAC 2.8 is already installed, yet just because your registry or one more files back this assertion up, the system may still have files that are out of sync and, therefore, should be updated. I wish the MDAC install would always do its thing and just make sure not to overwrite newer files instead of not doing anything at all if it "thinks" the version in question is already installed. Man, it's no fun spending hours with a user over the phone having him/her search the registry, run component checker, check file versions, etc... fortunately, this user was a bit more computer savy, unfortunately, however, I'm not always that lucky. Man, just had to blow off some steam!
I had a similar issue with trying to install .NET 1.1. My machine says .NET 1.1 isn't installed (yet it clearly is) so when I try and run the .NET 1.1 installer it says ".NET 1.1 is installed - exiting". At least give us a "Trust me - I know what I'm doing" button. I can't quite understand the rationale for not allowing an install to run twice, especially if the install doesn't offer a "repair install" option. cheers, Chris Maunder
-
I spent the last two days, literally, on the phone trying to get a user's MDAC installed correctly, if there is such a thing, since I've never ran Component Checker on a machine and ended up without any mismatchs whatsoever. This particular user was running W2K SP4; last quarter the software was working, yet once the user updated to the current quarter the software started bombing saying that MDAC 2.6 or above is required, so something must have happened over the course of the quarter. Component Checker, however, said MDAC 2.8 was installed, yet a whole mess of dll files had versions not corresponding to 2.8, particularly the oledb32.dll file, and all bets are off if this file is jacked! To top things off, it seems that the MDAC 2.8 installation does not do anything, yet still says "installation complete", if it detects that MDAC 2.8 is already installed, yet just because your registry or one more files back this assertion up, the system may still have files that are out of sync and, therefore, should be updated. I wish the MDAC install would always do its thing and just make sure not to overwrite newer files instead of not doing anything at all if it "thinks" the version in question is already installed. Man, it's no fun spending hours with a user over the phone having him/her search the registry, run component checker, check file versions, etc... fortunately, this user was a bit more computer savy, unfortunately, however, I'm not always that lucky. Man, just had to blow off some steam!
I've had a similar problem with MDAC a few years ago. However, I cannot remember if it was exactly the same problem or not. Luckily, I just remembered details about the post that helped me fix the problem and I found it for you ;) Search for "Repair a corrupted MDAC 2.71 installation - the Solution" in Google Groups. The first post is what you're looking for. I hope it will help!
-
I had a similar issue with trying to install .NET 1.1. My machine says .NET 1.1 isn't installed (yet it clearly is) so when I try and run the .NET 1.1 installer it says ".NET 1.1 is installed - exiting". At least give us a "Trust me - I know what I'm doing" button. I can't quite understand the rationale for not allowing an install to run twice, especially if the install doesn't offer a "repair install" option. cheers, Chris Maunder
-
I spent the last two days, literally, on the phone trying to get a user's MDAC installed correctly, if there is such a thing, since I've never ran Component Checker on a machine and ended up without any mismatchs whatsoever. This particular user was running W2K SP4; last quarter the software was working, yet once the user updated to the current quarter the software started bombing saying that MDAC 2.6 or above is required, so something must have happened over the course of the quarter. Component Checker, however, said MDAC 2.8 was installed, yet a whole mess of dll files had versions not corresponding to 2.8, particularly the oledb32.dll file, and all bets are off if this file is jacked! To top things off, it seems that the MDAC 2.8 installation does not do anything, yet still says "installation complete", if it detects that MDAC 2.8 is already installed, yet just because your registry or one more files back this assertion up, the system may still have files that are out of sync and, therefore, should be updated. I wish the MDAC install would always do its thing and just make sure not to overwrite newer files instead of not doing anything at all if it "thinks" the version in question is already installed. Man, it's no fun spending hours with a user over the phone having him/her search the registry, run component checker, check file versions, etc... fortunately, this user was a bit more computer savy, unfortunately, however, I'm not always that lucky. Man, just had to blow off some steam!
*grin* Are you using VB6, or does .NET require MDAC as well ? Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
-
*grin* Are you using VB6, or does .NET require MDAC as well ? Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
-
*grin* Are you using VB6, or does .NET require MDAC as well ? Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
VB6? You're messing with me, right? I hope to never ever write another line of VB6 code again :laugh:! Actually, ADO.NET requires MDAC 2.6 or above Nice hearing from you again dude :-D! C#, man, what a piece of crap ;P! I'm just kidding dude; I just like pulling your buttons :laugh:. Talk to ya soon
-
VB6? You're messing with me, right? I hope to never ever write another line of VB6 code again :laugh:! Actually, ADO.NET requires MDAC 2.6 or above Nice hearing from you again dude :-D! C#, man, what a piece of crap ;P! I'm just kidding dude; I just like pulling your buttons :laugh:. Talk to ya soon
Giancarlo Aguilera wrote: Actually, ADO.NET requires MDAC 2.6 or above Oh, OK. Even for SQL Server ? That plain sucks. I've not had trouble with it yet, but I have distributed an app that used MSDE database recently. I didn't think I distributed MDAC. Giancarlo Aguilera wrote: C#, man, what a piece of crap I agree - C++ is the way to go. I'm knee deep in C++ image processing code, and loving it.... Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
-
I think .NET needs MDAC for accessing Access databases. But I don't work with Access so I cannot be 100% sure of this.
Certainly for the oledb provider MDAC is required, but now I am curious whether it's required when accessing SQL through the native sql provider, I'm not sure.
-
Giancarlo Aguilera wrote: Actually, ADO.NET requires MDAC 2.6 or above Oh, OK. Even for SQL Server ? That plain sucks. I've not had trouble with it yet, but I have distributed an app that used MSDE database recently. I didn't think I distributed MDAC. Giancarlo Aguilera wrote: C#, man, what a piece of crap I agree - C++ is the way to go. I'm knee deep in C++ image processing code, and loving it.... Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
Yes, even for SQL, although I just now cleared that doubt up http://support.microsoft.com/default.aspx?scid=kb;en-us;315467[^]
-
I think .NET needs MDAC for accessing Access databases. But I don't work with Access so I cannot be 100% sure of this.
SQL too, I just cleared that doubt up http://support.microsoft.com/default.aspx?scid=kb;en-us;315467[^]
-
I spent the last two days, literally, on the phone trying to get a user's MDAC installed correctly, if there is such a thing, since I've never ran Component Checker on a machine and ended up without any mismatchs whatsoever. This particular user was running W2K SP4; last quarter the software was working, yet once the user updated to the current quarter the software started bombing saying that MDAC 2.6 or above is required, so something must have happened over the course of the quarter. Component Checker, however, said MDAC 2.8 was installed, yet a whole mess of dll files had versions not corresponding to 2.8, particularly the oledb32.dll file, and all bets are off if this file is jacked! To top things off, it seems that the MDAC 2.8 installation does not do anything, yet still says "installation complete", if it detects that MDAC 2.8 is already installed, yet just because your registry or one more files back this assertion up, the system may still have files that are out of sync and, therefore, should be updated. I wish the MDAC install would always do its thing and just make sure not to overwrite newer files instead of not doing anything at all if it "thinks" the version in question is already installed. Man, it's no fun spending hours with a user over the phone having him/her search the registry, run component checker, check file versions, etc... fortunately, this user was a bit more computer savy, unfortunately, however, I'm not always that lucky. Man, just had to blow off some steam!
MDAC was never meant to be uninstalled. Also, MDAC 2.8 is not a complete install because MS dropped many of the core Jet componments for 2.8. Use 2.7 for Access, and never uninstall it after it's been put on the system. Jeremy Falcon
-
Giancarlo Aguilera wrote: Actually, ADO.NET requires MDAC 2.6 or above Oh, OK. Even for SQL Server ? That plain sucks. I've not had trouble with it yet, but I have distributed an app that used MSDE database recently. I didn't think I distributed MDAC. Giancarlo Aguilera wrote: C#, man, what a piece of crap I agree - C++ is the way to go. I'm knee deep in C++ image processing code, and loving it.... Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
So I assume you ended getting that C++ job you were talking about? Good for you. Which compiler out of curiosity (ms, borland)?
-
So I assume you ended getting that C++ job you were talking about? Good for you. Which compiler out of curiosity (ms, borland)?
No, this is just a little outside job, about a months work or so in my spare time. So, VS.NET 2003 :-) Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
-
I spent the last two days, literally, on the phone trying to get a user's MDAC installed correctly, if there is such a thing, since I've never ran Component Checker on a machine and ended up without any mismatchs whatsoever. This particular user was running W2K SP4; last quarter the software was working, yet once the user updated to the current quarter the software started bombing saying that MDAC 2.6 or above is required, so something must have happened over the course of the quarter. Component Checker, however, said MDAC 2.8 was installed, yet a whole mess of dll files had versions not corresponding to 2.8, particularly the oledb32.dll file, and all bets are off if this file is jacked! To top things off, it seems that the MDAC 2.8 installation does not do anything, yet still says "installation complete", if it detects that MDAC 2.8 is already installed, yet just because your registry or one more files back this assertion up, the system may still have files that are out of sync and, therefore, should be updated. I wish the MDAC install would always do its thing and just make sure not to overwrite newer files instead of not doing anything at all if it "thinks" the version in question is already installed. Man, it's no fun spending hours with a user over the phone having him/her search the registry, run component checker, check file versions, etc... fortunately, this user was a bit more computer savy, unfortunately, however, I'm not always that lucky. Man, just had to blow off some steam!
I hate MDAC as well. Usually installing 2.8 fixes any problems I have seen, other times you have to take more drastic measures. I have some repair steps that I got off of a website that work for those drastic cases. Email me if you would like me to send it to you.
"Live long and prosper." - Spock
Jason Henderson
blog -
I spent the last two days, literally, on the phone trying to get a user's MDAC installed correctly, if there is such a thing, since I've never ran Component Checker on a machine and ended up without any mismatchs whatsoever. This particular user was running W2K SP4; last quarter the software was working, yet once the user updated to the current quarter the software started bombing saying that MDAC 2.6 or above is required, so something must have happened over the course of the quarter. Component Checker, however, said MDAC 2.8 was installed, yet a whole mess of dll files had versions not corresponding to 2.8, particularly the oledb32.dll file, and all bets are off if this file is jacked! To top things off, it seems that the MDAC 2.8 installation does not do anything, yet still says "installation complete", if it detects that MDAC 2.8 is already installed, yet just because your registry or one more files back this assertion up, the system may still have files that are out of sync and, therefore, should be updated. I wish the MDAC install would always do its thing and just make sure not to overwrite newer files instead of not doing anything at all if it "thinks" the version in question is already installed. Man, it's no fun spending hours with a user over the phone having him/her search the registry, run component checker, check file versions, etc... fortunately, this user was a bit more computer savy, unfortunately, however, I'm not always that lucky. Man, just had to blow off some steam!
So..... How about a REAL component checker, then? Are you going to write one for us?
-
Certainly for the oledb provider MDAC is required, but now I am curious whether it's required when accessing SQL through the native sql provider, I'm not sure.
I think the MSDE requires MDAC as well. It has been a few months, so I might have had false memories implanted in the meantime :doh:
-
I think the MSDE requires MDAC as well. It has been a few months, so I might have had false memories implanted in the meantime :doh:
yes, msde does require mdac
-
So..... How about a REAL component checker, then? Are you going to write one for us?
I highly doubt it :-D. MDAC is a monster I would rather stay away from. Here's another tool though http://www.macropool.com/en/download/repair_mdac.html[^]