Subscribe Subscribe | Subscribe Comments RSS


Mitch

Reinstalling MDAC in XP SP3

I had a customer that just couldn’t get MDAC to work under XP. Reinstalling XP SP3 didn’t work. Microsoft doesn’t make anything available to reinstall MDAC individually. So it’s a complete nightmare to fix it. Luckily, I was able to solve the issue with these steps:

1. Click Start > Run and type %windir%\inf and click OK.

2. Right-click mdac.inf and select Install.

This is where the nightmare started for me. I didn’t have any of the files below. I had to copy the OLE DB, msadc, Ole DB and Binaries folders from another computer and place them in the C:\Program Files\Common Files\System\ folder. If you are missing the servicepackfiles folder, you will have it after you reinstall XP Service Pack 3. You can also just extract the files from the SP3 file by using the windowsxp-kb936929-sp3-x86-enu.exe –x command.

3. When prompted for each of the following files, try to browse and locate them in the directories specified.

  • adcjavas.inc – C:\Windows\servicepackfiles\i386
  • handler.reg – C:\Program Files\Common Files\System\msadc
  • MDACRdMe.htm – C:\Program Files\Common Files\System\AdoI had to rename MDACReadme.htm to MDACRdMe.htm first.
  • oledbjvs.inc – C:\Program Files\Common Files\System\Ole DB
  • mssoap1.dll – C:\Program Files\Common Files\MSSoap\Binaries
  • mssoapr.dll – C:\Program Files\Common Files\MSSoap\Binaries

After all these steps, MDAC was working again.

This article was adapted from the article How to Repair MDAC 2.8 Under Windows XP with SP2 Installed. They also have a pretty useful MDAC repair tool, although it didn’t work for me in this case.

13 Responses to “Reinstalling MDAC in XP SP3”

  1. Bruno says:

    Awesome, u saved my life with this article!

  2. Mark Berry says:

    Awesome, thanks a bunch. MS has a similar article here:

    http://support.microsoft.com/kb/899861

    but having that list of file sources saved a lot of hunting around. As the first comment mentions, the last path (mssoapr.dll) needs to be extended, but I did NOT need to restart my computer.

  3. Leonardo Artuzo says:

    TANKS!!!! Perfect!!!! Excelent!!!! Tanks and more tanks!!!!

  4. Angel Escamilla says:

    Excelent! struggled with this for quite some time, now it’s fixed!

  5. Elena says:

    Thanks a lot. It was very helpful

  6. Rahul says:

    I tried something differnt i have XP SP3 CD , I just run the above mentioned mdac.inf and then Giveen only one path G:\I386 folder , Thats work for me , I needed MDAC for load runner, Thanks a ton for your help.

    It really saves lots of time for me

  7. mahdi says:

    it was the right solution,
    really, so tanx

  8. Melelen says:

    Your information was very helpfull!!
    Thankss!! =)

  9. Vigilance says:

    YOU THA MAN/WOMAN, THAN YOU VERY MUCH. Saved me having to reinstall the whole operating system again.Don’t know why it corrupted though, if you know post it, pls.

  10. sergio says:

    exelent!!!

    thanks

  11. DN says:

    THANK YOU THANK YOU THANK YOU! This solution just saved the day! My user started getting the following error after logging in to an Access 2000 database:
    The expression On Click you entered as the event property setting produced
    the following error: License information for this component not found. You do not have an appropriate license to use this functionality in the design environment.
    * The expression may not result in the name of a macro, the name of a user-defined function, or [Event Procedure].
    * There may have been an error evaluating the function, event, or macro.

    Your solution fixed the problem!!!

    (Sidenote: I too had to change the path for
    mssoapr.dll – “C:\Program Files\Common Files\MSSoap\Binaries\Resources\1033″)

  12. Joe says:

    this is awesome .. fixed an Access issue

  13. Japie Die Skapie says:

    Thanks, this saved us a lot of time.
    The only thing that I had to change was the one path :

    mssoapr.dll – “C:\Program Files\Common Files\MSSoap\Binaries\Resources\1033″

    and you should also mention that you need to restart the computer for it to start working again.

    Thanks again.

Leave a Reply