You should not attempt to install MDAC 2.8 on a Windows XP Service Pack 2 machine. The ComponentChecker has not yet been updated to be able to check the stack protected MDAC that ships with Windows XP Service Pack 2. Now run the MDAC installer ( MDAC_TYPE.EXE) and reboot.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\RollbackVersionĪnd replace the current data with the value 2.5. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ExceptionComponents Remove registry entries protecting the MDAC Download the latest MDAC releaseĬurrently the latest MDAC version is 2.8. If none of the categories have “MISMATCH” or “UNKNOWN” entries, you should not attempt to reinstall the MDAC as it is configured correctly. There will be up to three categories under each: |-MATCH In the left hand panel there are three tree views: |Įxpand these views. Then click the “scan” button (the “Play” icon in the toolbar) and choose the second option: ‘Perform analysis against a selected version”, choosing the version that the utility detected. Launch the program and run a default scan to see which version of the MDAC you have installed. Microsoft provide a tool for checking the MDAC subsystem to check to see if it is installed correctly. Using ComponentChecker to verify the integrity of MDAC components
A damaged MDAC installation, particularly when it affects the Jet component, can lead to a large number of ambiguous errors and can leave the computer unusable. The MDAC is a critical peice of the Windows infrastructure because among other things it provides the handlers for connecting to and modifying the Windows SAM. Under certain situations the ODBC subsystem in Windows can be corrupted For example, during an application install part of the driver set is overwritten set but not the whole thing because some of the files are locked by another process. Forcing a reinstall of the Microsoft Data Access Components
0 kommentar(er)
