RE: MDAC failed in Windows 2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Kevin Yu [MSFT] (v-kevy_at_online.microsoft.com)
Date: 06/04/04 

Date: Fri, 04 Jun 2004 03:05:26 GMT

Hi Wcharts,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that the MDAC drivers were unable to load in
Visual Studio .NET 2003 when you have upgraded your OS from Windows 2000 to
Windows 2003. If there is any misunderstanding, please feel free to let me
know.

Based on my research, Windows Server 2003 includes the MDAC 2.8 components.
If you try to run the 2.8 MDAC_TYP.exe file on a computer that is running
Windows Server 2003, installation of the MDAC components appears to
complete successfully. However, no files are updated on your system. This
behavior occurs because by default. Please check the following link to find
more information:

http://support.microsoft.com/?kbid=828396

Sometimes after removing an application that uses ODBC drivers, it is
possible that the ODBC drivers are missing from the ODBC Administrator.
This can render any ODBC-dependent application unusable. Rerunning MDAC
may not restore the ODBC driver entries.

The MDAC setup program provides a utility called ODBCCONF.EXE. This
program is the ODBC Configuration program (hence the name), and it can be
used to configure ODBC drivers and DSNs. The MDAC setup program uses this
tool to configure the ODBC drivers.

To observe the usage, you can simply run "odbcconf.exe /?" from a command
line to view the available switches and actions that can be taken. This
utility is located in the \winnt\system32 directory. In addition, MDAC
installations include 4 files with an RSP extension (this number may vary
between different versions of MDAC). These are response files that contain
actions that ODBCCONF.EXE will perform automatically (i.e. they are script
files). These scripts contain the necessary commands to install the ODBC
drivers and configure a few default DSNs.

To run these scripts, we used something similar to the following syntax:

  odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\mdaccore.rsp
  odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\sqlclnt.rsp
  odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\odbcconf.rsp
  odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\redist.rsp

The odbcconf.log file contains the results from each of the above commands.
 The
results are appended in succession to the log file.

HTH.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Relevant Pages

  • Re: Help reqd with database please
    ... eventually MS will stop supporting VB6. ... He'll need to ensure that MDAC is installed, along with the Jet service packs. ... the Jet drivers were no longer included. ... Edition Starter Kit" from Wrox. ...
    (comp.lang.basic.visual.database)
  • Re: Using vfoledb with webservices?
    ... later MDAC package and install that. ... MDAC 2.7 or 2.8 doesn't install specific OLE or ODBC drivers for any ... particular database engines except Oracle and SQL Server. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: odbc driver?
    ... it MDAC but it was previously referred to as Universal Data ... Access and you had the ODBC driver packs, ... MDAC and MDAC is part of the OS so most MS drivers are ... to install the ODBC driver to a Server 2003 R2 box. ...
    (microsoft.public.sqlserver.odbc)
  • Re: ODBC Drivers
    ... Note that you can get ODBC drivers from many sources besides Microsoft. ... those data sources. ...
    (microsoft.public.data.odbc)
  • Re: ODBC Drivers Disappeared
    ... > It depends on the operating system, but with most of the latest ones ... > install and this will also repair the ODBC drivers. ... > Please do not send email directly to this alias. ...
    (microsoft.public.data.odbc)