Microsoft KB Archive/255986

= PRB: Improper Installation of MDAC May Return Error Message "Method '~' of Object '~' Failed" at Run Time with ADO Application =

Article ID: 255986

Article Last Modified on 5/17/2007

-

APPLIES TO


 * Microsoft Data Access Components 2.1
 * Microsoft Data Access Components 2.1 Service Pack 2
 * Microsoft Data Access Components 2.1 Service Pack 1
 * Microsoft Data Access Components 2.1 Service Pack 2
 * Microsoft Data Access Components 2.5
 * Microsoft Data Access Components 2.6
 * Microsoft Data Access Components 2.7
 * Microsoft Data Access Components 2.8
 * Microsoft Visual Basic 5.0 Professional Edition
 * Microsoft Visual Basic 6.0 Professional Edition
 * Microsoft Visual Basic 5.0 Enterprise Edition
 * Microsoft Visual Basic 6.0 Enterprise Edition

-



This article was previously published under Q255986



SYMPTOMS
When you attempt to run simple ActiveX Data Objects (ADO) code in an application, the following error can occur:

"Method '~' of Object '~' Failed"



CAUSE
The most common cause for this error is mismatched DLL files with Microsoft Data Access Components (MDAC).



RESOLUTION
To work around this problem:  Make sure to install the appropriate Mdac_type.exe file that matches the same version you developed with your application. You can find the file at:

http://msdn2.microsoft.com/en-us/data/aa937695.aspx

 If you are using a Microsoft Windows 9x computer, install the latest DCOM version from:

http://www.microsoft.com/com/resources/downloads.asp

 If you are deploying this application, be sure to use the Package and Deployment Wizard and distribute the correct Mdac_typ.exe file version. Also make sure that the computer is restarted after MDAC installation unless you are explicitly implementing a silent install.

 If you are still having problems, obtain the Component Checker to remove MDAC and install it again. The Component Checker can be obtained at:

http://msdn2.microsoft.com/en-us/data/aa937695.aspx





MORE INFORMATION
Although this error has not been consistently reproduced, the items in the "Resolution" section appear to be effective in correcting the problem.

The preceding error is only one of the ways that mismatched DLLs may manifest themselves. A different error may occur. The component checker mentioned in the Resolution section will help determine if there are mismatched DLLs.

