Page 1 of 1

GetTextExtendPointI could not be located in MSDART.DLL

PostPosted: Thu Jun 01, 2006 2:16 pm
by stephen
Error message occurs when trying to open mpg files.

wmplayer.exe - Entry Point not found
The procedure entry point GetTextExtendPointI could not be located in the dynamic link library MSDART.DLL

I found a usefull tip at
http://www.dbforums.com/archive/index.p ... 90640.html

Need an up to date version of
ole32db.dll.

thanks for the detailled link.

I've also found the ol32db.dll file problem and solve it by copying it from
a working server.

but the article talk about the dllcache... so I'll change the file here
too...

-----
I have two windows 2000 servers
the working server has a ole32.dll
size 957,200 modified 18/01/2005

the server with the msdart errors has a ole32.dll
size 996,112 modified 19/06/2003

I have copied the \winnt\system32\ole32.dll file from the working server
and copied it into the \winnt\system32\dllcache folder on the problem server
I tried to copy it over the ole32 file in \winnt\system32 but
it seems to copy ok but the file has not changed in size or date modified.
if you copy using windows it says cannot replace "Cannot create or replace OLE32: The specified file is being used by windows."

MDAC files are not updated correctly

PostPosted: Fri Jun 02, 2006 5:34 pm
by stephen
Microsoft say in this web page

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B839428

You may receive one of these error messages:-
3709 - The connection cannot be used to perform this operation. It is either closed or invalid in this context.
Error message 2
-2147024769 Automation Error
Error message 3
8007007f Unknown Error
Error message 4
8007007f Cannot open the table
Error message 5
"Method'~' of Object '~' failed" on invoking the Open method of an ADODB.Connection
Error message 6
Error: The procedure entry point GetTextExtentPointI could not be located in the dynamic link library MSDART.DLL.
Error message 7
Error connecting to SQL-2147024769-


This problem occurs because the appropriate Microsoft Data Access Components (MDAC) files were not successfully upgraded.

Microsoft Hot fix

PostPosted: Mon Jun 05, 2006 6:24 pm
by stephen
I contacted Microsoft and obtained the hot fix for MDAC 2.80

However when I tried to apply it it said that I had version 2.81 and the hotfix was not meant for the 2.81 version.

They suggested I talk to a Microsoft support rep the fee would be $300.00

I will have a go at fixing the problem myself at this stage.

Agconet Ver 7.0.0 caused problems with other software

PostPosted: Wed Jun 07, 2006 4:10 pm
by stephen
I set up a new server to try and work around the problem.
All was going fine untill I installed Agconet Version 7.00

It appears this software changed the MDAC version on the PC.

I rang AGCO and they told me to run D:\AV\AV.EXE
which was on the AAgconet Version 7.0.0 CD.

After I ran this I was able to run programs that were giving errors in MSDART and other DLL's

eg GALILEO 4.7 and Case Support Pro 2 now work correctly.

I have one product that will not run correctly called MTD Parts Spotter

Viewer.exe - Common Language Runtime Debugging Services

PostPosted: Wed Jun 07, 2006 4:16 pm
by stephen
MTD Parts in Place
Viewer.exe - Common Language Runtime Debugging Services
Application has generated an exception that could not be handled
Process id=0x1a18 (6680) Thread ud=0x1b44 (6980)
Click OK to terminate the application.
Click Cancel to debug the application.

I rang MTD and they suggest uninstall and re-install the software.

The MTD Parts in Place software is designed for MDAC 2.7 SP1 Refresh
and this seems to be conflicting with the MDAC 2.8 SP1 software installed by Agconet.