Help: GetTextExtentPointIX could not be located?

Hi All,
While trying to create a new dts package in SQL Server
2000 the following error message appeared:
mmc.exe - Entry Point Not Found
The procedure entry point GetTextExtentPointIX could not
be located in the dynamic link library MSDART.dll.
I reinstalled MS Servicepack 3a for SQL Server, but this
didn't solve the problem.
I tried to use system restore, but without any luck
either.
I installed Visual Studio .NET Whidbey the day before
yesterday, could this have caused the problem, and if so,
how could I resolve this error?
Thank you in advance,
bENI had a similar problem earlier and had to uninstall Whidbey and then
re-install SQL Server. Not sure if any workaround is present.
I would recommend that you install Whidbey on a seperate machine.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"bEN" <benvkm@.nospam4.net> wrote in message
news:091b01c3b025$1036a100$a401280a@.phx.gbl...
> Hi All,
> While trying to create a new dts package in SQL Server
> 2000 the following error message appeared:
> mmc.exe - Entry Point Not Found
> The procedure entry point GetTextExtentPointIX could not
> be located in the dynamic link library MSDART.dll.
> I reinstalled MS Servicepack 3a for SQL Server, but this
> didn't solve the problem.
> I tried to use system restore, but without any luck
> either.
> I installed Visual Studio .NET Whidbey the day before
> yesterday, could this have caused the problem, and if so,
> how could I resolve this error?
> Thank you in advance,
> bEN
>|||Hello,
Thanks for your post. According to the error message, it usually indicates
a problem with the MSDART.dll file. I would like you to try installing MDAC
2.7 SP1a. After rebooting, then apply SQL2K SP3a and rebooted again. Does
it solve your problem?
For additional information regarding MDAC 2.7sp1, please refer to the
following articles:
Microsoft Data Access Components (MDAC) 2.7 Service Pack 1 Refresh
http://www.microsoft.com/downloads/details.aspx?FamilyID=9ad000f2-cae7-493d-
b0f3-ae36c570ade8&DisplayLang=en
Also, please test the suggestions in the following articles to see if it
helps.
http://dbforums.com/archives/t128594.html
http://dbforums.com/showthread.php?threadid=319606
This document contains references to a third party World Wide Web site.
Microsoft is providing this information as a convenience to you. Microsoft
does not control these sites and has not tested any software or information
found on these sites; therefore, Microsoft cannot make any representations
regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any
software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from
the Internet.
Please feel free to post in the group if this solves your problem or if you
would like further assistance.
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 All,
Thank you for the possible solutions.
Saldy enough, the problem isn't solved yet.
I installed 2.7 SP1a. Rebooted, didn't work
I installed 2.8. Rebooted, didn't work.
I also tried the suggestions in the following articles
>http://dbforums.com/archives/t128594.html
>http://dbforums.com/showthread.php?threadid=319606
Didn't work either.
I unistalleded sql server, didn't work.
I installed the 2.7 SP1a, rebooted, tried, than installed
the 2.8 and it didn't help.
I installed Visual Studio .NET 2003 again, didn't solve
the problem.
I deleted the whole C:\Program Files\Common
Files\Microsoft Shared\MSDesigners98 directory on my hard
drive, and reinstalled SQL Server 2000 with SP3a, didn't
solve the problem.
But now something that I just noticed. MS office 2003 is
also installed on that machine, when I loged in with a
fresh create user account (thinking a different profile
could help) and started outlook, the same error came up,
when it tried to create a new outlook profile?
Guess I could reinstall ms office 2003 now, but don't
know if that would help...
Hope you guys might could give me some more advice?
Thank you in advance,
bEN
>--Original Message--
>Hello,
>Thanks for your post. According to the error message, it
usually indicates
>a problem with the MSDART.dll file. I would like you to
try installing MDAC
>2.7 SP1a. After rebooting, then apply SQL2K SP3a and
rebooted again. Does
>it solve your problem?
>For additional information regarding MDAC 2.7sp1, please
refer to the
>following articles:
>Microsoft Data Access Components (MDAC) 2.7 Service Pack
1 Refresh
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=9ad000f2-cae7-493d-
>b0f3-ae36c570ade8&DisplayLang=en
>Also, please test the suggestions in the following
articles to see if it
>helps.
>http://dbforums.com/archives/t128594.html
>http://dbforums.com/showthread.php?threadid=319606
>This document contains references to a third party World
Wide Web site.
>Microsoft is providing this information as a convenience
to you. Microsoft
>does not control these sites and has not tested any
software or information
>found on these sites; therefore, Microsoft cannot make
any representations
>regarding the quality, safety, or suitability of any
software or
>information found there. There are inherent dangers in
the use of any
>software found on the Internet, and Microsoft cautions
you to make sure
>that you completely understand the risk before
retrieving any software from
>the Internet.
>Please feel free to post in the group if this solves
your problem or if you
>would like further assistance.
>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 Ben,
Thanks for your response. You wrote "the same error came up, when it tried
to create a new outlook profile?" Do you mean the error message is exactly
the same as the one occurring on the SQL Server? If not, please provide the
detailed error message. Based on your description, the error is mostly
caused by the version mess of the MSDART.dll file.
Please provide the following information so that I can perform further
research.
1. What is the Operation System on your side?
2. When you searched for the MSDART.dll file on your computer, how many
files did you find and what were their versions?
Before searching for the MSDART.dll file, please go to tools --> folder
options --> view tab and turn on "show hidden files and folders". UNCHECK
"hide extensions for know file types" and "hide protected operating system
files".
3. I would like you to check the MDAC version on your machine using
component checker.
It also helps us to find files that mismatch the current version of MDAC.
Please download the latest version of component checker from this URL:
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-
BF53-14332EF092C9&displaylang=en
Can you find the MSDART.dll file in the mismatched files list? If so, I
would like you to provide all the related information. It is best to
provide a screen shot.
Try to obtain the screen shot of the information.
1. Press the "Pr Scrn" button on the keyboard.
2. Run the Paint tools (Start?All programs?Accessories?Paint).
3. Press Ctrl+V to copy the screen shot from the memory.
4. Save as a JPEG file.
Also, such issues tend to be complex and take up extensive research time.
I'd like to set your expectations appropriately, knowing that it may take a
while for us to help you narrow down the problem. In addition, we may
eventually suggest that you reinstall the operation system. If this is
critical, I'd recommend contacting PSS and opening a Support incident
troubleshoot this further. If you need any help in this regard, please let
me know.
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 experienced the exact same problem. I was running Win2K & Sql Server sp3a. Everything was fine. I upgrade
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 up DTS designer and get GetTextExtentPointI
could not be located in msdart.dll. Try to open a table and I get "Unknown error: 8007007F"
msdart.dll ver is 2.80.1022.0|||Same 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 will complain about not finding GetTextExtentPointI in MSDART.DLL. I also can't create a .UDL file anymore 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/details.aspx?FamilyId=8F0A8DF6-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/details.aspx?FamilyId=8F0A8DF6-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.
>