November 1, 2007 at 9:36 am
I installed the DTS Components for 2005 and now my Enterprise Manager doesn't work.
I'm working in an environment where we have both SQL 2000 and 2005 and have found that for certain things (security, scripting, DTS etc) it is easier to keep both sets of tools available. This was working great until I installed the DTS Editor Components for 2005. Now when I try to open Enterprise Manager I get the following errors:
The procedure entry point ?ProcessExecute@@YAXPAUHWND__@@PBG1@Z could not be located in the dynamic link library SEMSFC.dll
Then
Connection to application object failed. Ensure that no program modules have been deleted.
We have had this problem on 2 different machines now. Please tell me I'm not the only one with this problem and there is a fix out there somewhere?
Thanks
Kenneth Fisher
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
November 1, 2007 at 2:26 pm
I had this issue with our sandbox, but I opted for a clean install of 2005.
Not sure if you had a look at this link already - might help...
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=174076&SiteID=17
November 1, 2007 at 3:09 pm
Unfortunatly this is for our development machines and with a mixed environment (mid upgrade) we need them to have both sets of tools (and to be honest there are just things that 2000 does better).
However that article you posted works GREAT. It suggested applying SP4 to the SQL 2000 install. I can now use both the 2000 and 2005 tools. Along with both sets of DTS designers.
Thanks again.
Kenneth Fisher
Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]
April 18, 2008 at 6:52 am
I installed SQL Server 2000 SP3 and it worked straight away!
Use the 'sql2ksp3.exe' file in the pack from Microsoft at
(P.S. I just installed this on my client. It didn't need to go on the sever)
A long struggle ended! 🙂
April 22, 2008 at 8:35 pm
If by no means SQL 2000 SP4 and SP3 are not fixing this error then you need to do a clean install:
- install SQL 2000 client
- install SQL 2005 server
- install sqlserver2005_dts.msi
Then
- uninstall all of the above (I sequentially uninstalled 2000, 2005 and the dts addins)
- reinstall SQL 2000 and try EM - it should now work
- you then can reinstall SQL 2005 server but NOT sqlserver2005_dts.msi
- reapply SPs for 2005 and 2000
You might have to do few reboots in the process (I did 1 after uninstalling everything).
Hope it helps
T
March 6, 2009 at 1:08 pm
I followed the same steps to get 2000 and 2005 working on same PC with DTS Designer components. It worked on my old laptop but not on my desktop. Both have same Win xp with SP2.
If I install SQL 2005 sp3, will this problem be resolved ?
Can anyone help ?
Thanks
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply