Error trying to import after upgrade to Win2003

[meckeard]

Hi All,

I have SQL Server 2000 and started getting an error when trying to import/export (DTS) after I upgraded to Windows 2003 Enterprise Edition:

the procedure entry point GetTextEntentPointI could not be located in the dynamic link library MSDART.DLL

I can't find any info on the MS website or google.

Any ideas?

Thanks,
Mark

 

[mrdenny]

What happens when you run the DTS package manually from your workstation?

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[meckeard]

Here is what happens when I right-click on a database --> All Tasks --> Import Data:

1) I get the above error twice
2) I get a third error: The specified procedure could not be found
3) The DTS wizard appears, I click the "Next" button
4) The data source defaults to .txt/.csv option, not SQL Server like it usually does
5) When I select my server from the dropdown, it waits about 5 seconds then generates an application error:

the instruction at "0x418c2768" referenced memory "0x00000000". The memory could not be read.

Also, I cannot right-click and open a table.

Thanks for the help.

Mark

 

[mrdenny]

Sounds like you need to reinstall Enterprise Manager. Have you tried this operation on more than one computer's console?

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[meckeard]

No. It's my only server.

I will try a reinstall tonight.

Thanks,
Mark

 

[mrdenny]

If you have Enterprise Manager installed on another machine (workstation or server, all you need is Enterprise Manager) you can confirm if EM is hosed. If the procedure works on another machine with Enterprise Manager then the EM on the server needs to be reinstalled.

When reinstalling on the server be sure to only reinstall the Client Tools, and not install another instance of SQL Server.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[meckeard]

I have another PC with EM, I will check it shortly.

I did uninstall SQL Server entirely. After I reinstalled, the first thing I noticed was my sql server registration list. It was still intact.

Anyhow, even after the reinstall, I still get the error.

I will check EM on another PC.

Thanks,
Mark

 

[meckeard]

EM can connect on my laptop to the server. It runs SQL 2k and Win XP Pro.

Does this mean that the problem exists with EM on my server?

Thanks,
Mark

 

[meckeard]

OK, one more post.

I made another registration from my server to SQL Server on my laptop (I forgot it was installed there -- I haven't used it lately). And I still had the same problems with any of the databases on the laptop from my server.

Thanks,
Mark

 

[mrdenny]

Yeah, this means that there is a problem with the EM on the server. Try finding the dll you mentioned above on the laptop and on the server. Try replacing the DLL on the server with the one from the laptop. Be sure to backup the one on the server before overwriting it. It may have been replaced by the wrong version or something during the upgrade process.

This may kill the server depending on where the dll is located, and what else it does. So be VERY carefull.

 

[meckeard]

I reinstalled both the server and EM to no avail.

I applied SP3, all hotfixes and upgraded to MDAC 2.8. Nothing.

The only thing were mentioning is the warning I get when installed SQL Server on Win2k3. It states that SQL Server SP2 is not certified for this version of windows. But I only have 1 MSDN install disk, so I opt to continue. I then install SP3.

Any additional ideas are welcome.

Thanks,
Mark

 

[mrdenny]

I would recommend that you start checking out the DLLs on the Server and the laptop, and make sure that they are the same. Something may have gotten corrupt, and the installer didn't reconnise that it was corrupt, so it didn't over write it.

Denny

--Anything is possible. All it takes is a little research. (Me)