Sunday, February 19, 2012

Help: GetTextExtentPointIX could not be located?

I experienced the exact same problem. I was running Win2K & Sql Server sp3a.
Everything was fine. I upgraded
to Win Server 2003. I got warned about running Sql Server 2000 sp2 or lower.
I continued. Upgraded Win Server
2003 with all current critical patches. I run Sql Server 2003. Try to open u
p DTS designer and get GetTextExtentPointI
could not be located in msdart.dll. Try to open a table and I get "Unknown e
rror: 8007007F".
msdart.dll ver is 2.80.1022.0Same problem for me on 3 servers that I upgraded from Windows 2000 Server to
Windows 2003 Server. The SQL Enterprise Manager's DTS Package Designer wil
l complain about not finding GetTextExtentPointI in MSDART.DLL. I also can'
t create a .UDL file anymor
e and get the same error message.
My msdart.dll version is 2.80.1022.0.|||Hello,
Thanks for your post. What is the version of SQL Server (Service pack) on
your side? Based on my experience, MSDART.DLL is a MDAC component. Please
try to run MDAC component checker which is downloaded from
MDAC Utility: Component Checker
http://www.microsoft.com/downloads/...8DF6-4A21-4B43-
BF53-14332EF092C9&displaylang=en
Check to see if there are some different dlls were overwritten by 3rd party
software.
Also, in order to concentrate fully on your issue, it is best that you can
post it as a separate thread. On that way each issue can receive full
attention and will also make the thread more clear and consistent for
others reference. Please feel free to open a new post for this issue and we
will be very glad to work with you. Thanks for your understanding.
Thanks again for posting in community.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||I've figured out a fix to this problem.
On a machine running Windows 2003 Server that was upgraded from Windows 2000
Server, look for OLEDB32.DLL in "c:\Program Files\Common Files\System\Ole
DB".
Check the version of OLEDB32.DLL. If it is the correct version for Windows
2003 Server, it should be (at least) version 2.80.1022.0 according to the
MDAC 2.8 manifest.
On my servers that were upgraded from Windows 2000 Server to Windows 2003
Server, that OLEDB32.DLL file was version 2.71.9042.0. The wrong version.
I copied the OLEDB32.DLL that was version 2.8.1022.0 to c:\Program
Files\Common Files\System\Ole DB on the upgraded machines, and it seems to
have solved the "The procedure entry point GetTextExtentPointI could not be
located in the DLL MSDART.dll" problem.
The correct OLEDB32.DLL can be found from the MDAC 2.8 redistributable, or
from a cleanly installed Windows 2003 Server.
""Yuan Shao"" <v-yshao@.online.microsoft.com> wrote in message
news:3AZnnvp%23DHA.2848@.cpmsftngxa06.phx.gbl...
> Hello,
> Thanks for your post. What is the version of SQL Server (Service pack) on
> your side? Based on my experience, MSDART.DLL is a MDAC component. Please
> try to run MDAC component checker which is downloaded from
> MDAC Utility: Component Checker
>
http://www.microsoft.com/downloads/...8DF6-4A21-4B43-
> BF53-14332EF092C9&displaylang=en
> Check to see if there are some different dlls were overwritten by 3rd
party
> software.
> Also, in order to concentrate fully on your issue, it is best that you can
> post it as a separate thread. On that way each issue can receive full
> attention and will also make the thread more clear and consistent for
> others reference. Please feel free to open a new post for this issue and
we
> will be very glad to work with you. Thanks for your understanding.
> Thanks again for posting in community.
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>|||
quote:
Originally posted by Scot Kelly
I've figured out a fix to this problem.
On a machine running Windows 2003 Server that was upgraded from Windows 2000
Server, look for OLEDB32.DLL in "c:\Program Files\Common Files\System\Ole
DB".
Check the version of OLEDB32.DLL. If it is the correct version for Windows
2003 Server, it should be (at least) version 2.80.1022.0 according to the
MDAC 2.8 manifest.
On my servers that were upgraded from Windows 2000 Server to Windows 2003
Server, that OLEDB32.DLL file was version 2.71.9042.0. The wrong version.
I copied the OLEDB32.DLL that was version 2.8.1022.0 to c:\Program
Files\Common Files\System\Ole DB on the upgraded machines, and it seems to
have solved the "The procedure entry point GetTextExtentPointI could not be
located in the DLL MSDART.dll" problem.
The correct OLEDB32.DLL can be found from the MDAC 2.8 redistributable, or
from a cleanly installed Windows 2003 Server.
""Yuan Shao"" <v-yshao@.online.microsoft.com> wrote in message
news:3AZnnvp%23DHA.2848@.cpmsftngxa06.phx.gbl...
> Hello,
> Thanks for your post. What is the version of SQL Server (Service pack) on
> your side? Based on my experience, MSDART.DLL is a MDAC component. Please
> try to run MDAC component checker which is downloaded from
> MDAC Utility: Component Checker
>
http://www.microsoft.com/downloads/...8DF6-4A21-4B43-
> BF53-14332EF092C9&displaylang=en
> Check to see if there are some different dlls were overwritten by 3rd
party
> software.
> Also, in order to concentrate fully on your issue, it is best that you can
> post it as a separate thread. On that way each issue can receive full
> attention and will also make the thread more clear and consistent for
> others reference. Please feel free to open a new post for this issue and
we
> will be very glad to work with you. Thanks for your understanding.
> Thanks again for posting in community.
> Regards,
> Michael Shao
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>

|||Hi,
I download and installed MDAC_TYP.EXE and mdac28sdk.msi. However, I still ha
ve older version of oledb32.dll. Is there a quick to get the latest version?
Thanks.
Chris

No comments:

Post a Comment