My clientside application is having
problems loading up an MDAC DLL.
The client application is running COM+ components which are installed on a server. (The export is setup as an application proxy). The server is Win2K Pro SP2, SQL Server 2000 SP2. It’s got MDAC 2.6.2 as a result of the SQL Server service pack.
My client machine is a Win2K Pro SP2 machine with COM+ rollup 18.1. It’s got MDAC 2.5 SP2 installed as part of the Win2K service pack.
When I run Component Checker, it reports everything is installed correctly for MDAC 2.5 SP2 (2.52.6019.2).
When I run my client app, I get an ‘Error 48 – Error in loading DLL’. I used the SysInternal’s FileMon utility to discover that the application couldn’t find the msador15.dll. It was looking in the wrong location – it was looking for it in the application path, and the Winnt\System32\ path as well.
The Component Checker and the registry show that the msador15.dll is registered in the correct location (under \Program Files\Common Files\System\ADO), and the file is there and the correct version. These are clean installations and I’ve also tried unregistering and
registering the DLL with no success.
I’ve found that if I install a later version of MDAC (2.6 or later) on the client machine, everything works properly. I don’t know if it’s
because it’s resetting a value, or it’s a version incompatibility. I can’t install MDAC 2.5.2 again because Windows detects its already
installs and gives a fatal setup error.
Does anyone have any ideas? Is this an incompatibility issue with MDAC 2.5 and 2.6?
Thanks for your help.
Albert.