Microsoft KB Archive/309166

= PRB: MDAC Installation Rolls Back at the Very End of the Setup Process =

Article ID: 309166

Article Last Modified on 11/4/2003

-

APPLIES TO


 * Microsoft Data Access Components 2.6, when used with:
 * Microsoft Windows 2000 Standard Edition
 * Microsoft Data Access Components 2.6 Service Pack 1, when used with:
 * Microsoft Windows 2000 Standard Edition
 * Microsoft Data Access Components 2.6 Service Pack 2, when used with:
 * Microsoft Windows 2000 Standard Edition
 * Microsoft Data Access Components 2.8, when used with:
 * Microsoft Windows 2000 Standard Edition

-



This article was previously published under Q309166



SYMPTOMS
Installation of Microsoft Data Access Components (MDAC) 2.6 or later on a computer that is running Windows 2000 may roll back at the very end of the installation process. The Dasetup.log file (located in the Windows directory) shows that verification of Odbcconf.dll fails, and you receive the following error message:

Progress: Loading ODBCConf Library. Entering function: LoadODBCConf Parameters: *phInstance = 0x00000000 pODBCConfLib = 0x0012E9E0 Exiting function: LoadODBCConf Return value: (BOOL) 1 IE Version: IE 5.00 Verifying System Language: The system LCID and the LCID of the setup resource DLL do not match. Entering function: BuildJobList Parameters: pContext = 0x0012E9C8 Entering function: CJob::InitializeJobQueues Parameters: hHive = 0x80000002 szRoot = ???????????????s pContext = 0x%08X

The following message also appears at the end of the Dasetup.log file:

Error: The following error was encountered during setup: *** (null): Unspecified error (Severity: 100, Type: 2, Code: 0x80004005)



CAUSE
Odbcconf.dll is the ODBC driver configuration library, located in the Windows SYSTEM32 directory. You will find that this file is a different version than the Odbcconf.exe file or has a different language ID than your current Windows installation.



RESOLUTION
To correct the problem, rename the Odbcconf.dll file and reinstall MDAC. Make sure that the ODBC configuration manager is not running when you rename this file; otherwise, you will receive an &quot;Access Denied&quot; or &quot;File in use&quot; error message.

