January 25, 2007 at 2:31 pm
We got the following error when remote login into our production server:
The procedure entry point DefWindowProcI could not be located in the dynamic link library MSDART.dll.
I did some research and found the MDAC Utility: Component Checker from the following MS site
http://www.microsoft.com/downloads/...8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en and check to see if there are some different dlls.
There are a lots of files are identified as the mismatch Fields. For example, MSADCO.DLL. It's expeted version should be: 2.82.1830.0.
Does anyone know it's the correct way to fix the problem and where is the correct version located at so I can replaced the file.
Thanks a lot,
Roxanne
January 25, 2007 at 3:10 pm
Have you tried reinstalling the latest version of MDAC?
January 25, 2007 at 3:27 pm
No. I see it's already the latest version: 2.82.1830.0. How do I reinstall it if I have to?
January 25, 2007 at 4:47 pm
A quick search for MDAC on microsoft.com will get you this:
January 25, 2007 at 6:20 pm
Yes, I did this before but it says it's not the correct version or something like that. Our OS is 2003 sp1. This is one is good for
I will give a another try again and let you know.
Thanks again,
Roxanne
January 26, 2007 at 3:39 pm
Hi,
I donwloaded MDAC 2.8 from the link you referred and installed it without problem this time. After the installation, I run the CompChecker agian. However, I still see all those files stayed not matched and the error is still showing up. And a scheduleing job which had been running without problem doesn't run anymore. Basically this program\.batch file is to run DTS to extract data and send the file to a ftp site. But if I manually click on this file, it's working correctly.
Is there anything else I need to do?
Thanks,
Roxie
January 26, 2007 at 5:20 pm
January 26, 2007 at 6:12 pm
Thank you. Will read it and let you know how it goes.
January 29, 2007 at 6:53 am
MDAC 2.8 SP2 for Windows Server 2003 is only available within the Windows Server 2003 SP1 distribution. I have seen where MSDART.dll may sometimes exist in both Windows\System32 & several places under "program files\common files\System\...". Since this file is also a OS protected file, it will exist in the System32\dllcache (hidden) folder. Check all places. If this does not correct the problem, uninstall Win Server 2003 SP1, reinstall SQL 2000 SP4, then reinstall Win Server 2003 SP1.
hope this helps...
February 7, 2007 at 6:16 pm
Hi,
Sorry for the late reply. I unchecked protected file and searched again. I only found MSDART.dll in two places:
C:\WINDOWS\system32
C:\WINDOWS\ServicePackFiles\i386
And they both have the same version.
The reason I want to resolve the problem is that the schedule job doesn't work. However, after I corrected the problem of the scheduling job Run from "C:\WINDOWS\system32\cmd.exe /c SRbatch.bat" to "C:\SR Daily Extract\Batch Files\SRbatch.bat". The scheduling job works but I still see the same error everytime I login into this db box. So the error is not related to the scheduling job.
Since this is the production db (it doesn't happen to our development db), I'm little serious about uninstallation and reinstallaion at this point. But I'm glad this opton is available for later when it's necessary. I also read about another update. It's also related to my issue. I will give a try when I'm ready.
Thanks lot to both of you,
Roxanne
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply