Greetings!
Do any of you know whether or not it's possible to install Enterprise Manager onto a box with SQL Server 2005 installed I've come across a couple of problems when trying to admin some SQL 2000 servers, so I need EM somewhere. Also, it's incompatable with SQL Server 7.0, of course, and I've got two of them to admin as well.
Thanks!
DotNetFun wrote:
Yes, it's OK, I've done it. But it's not recommended for a production machine. Uninstalling either may cause either to not function properly.
Thanks for your reply. I went ahead and tried to install the SQL 2000 client tools on my laptop (which has the SQL 2005 installation). It was the only option I had. Anyway, it installed fine, but gave me the following error when I started EM: mmc.exe -
Entry Point Not Found
---------------------------
The procedure entry point ProcessExecute@@YAXPAUHWND__@@PBG1@Z could not be located in the dynamic link library SEMSFC.dll.
---------------------------
I get a couple of those and then a seeminly unending supply of:
---------------------------
SQL Server Enterprise Manager
---------------------------
Connection to application object failed. Ensure that no program modules have been deleted.
---------------------------
So, it looks like it's not going to work for me. Bummer. I'll just have to Remote Desktop to another machine when I need to. Thanks, though!
Installing SQL Server 2000 (tools and/or servers) after SQL Server 2005 is installed is not a good idea and not officially supported. I won't go into all of the gory details - but the main issue has to do with COM registration, which it looks like you hit. Since we didn't test this configuration I don't have a definitive answer for what you need to do other than strip everything down and start from a clean state. You can try re-registering a bunch of DLLs but I wouldn't recommend this.
We did explore installing a shim with SQL Server 2005 that would prevent SQL Server 2000 from installing but we couldn't come up with a solution that would meet every case. I realize none of these "answers" bode well for you. Again, you can try re registering the DLLs using "regsvr32" but you're on your own to figure out exactly what needs to be re-registered.
Dan
I have the same problem in a little different scenario.
What am I doing wrong
Please help,
Gita
Hi;
I've been facing the same problem since last week, this morning I got it done. Here what I experienced.
1- I was running SQL Server 2000 client components for Enterprise Manager
2- I installed SQL Server 2005 Management Studio
3- I could not open DTS in Management Studio, so I installed SQL Server 2000 DTS Graphics Components b/c I have to view DTS in both the server so that I can convert them into 2005 ETL
4- After that, my Enterprise Manager was got corrupted and I could not launch EM b/c of the same Error which is mentioned the above post, SEMSFC.dll
5- I uninstalled SQL Server 2000 components and re-installed them, the problem was not solved
6- I unistalled DTS 2000 Graphics components b/c that was the point which caused the problem, the problem was not sovled
7- I re-installed SQL Server 2000 client components, the problem was not solved
8- I gave up and re-installed DTS Components so that I would have at-least one place from where I can view DTS i.e. from SQL Server 2005 management studio, then it was not working.
9- I un-installed DTS Components and I gave up, I also rebooted my machine so many time during these tasks.
10- This morning, I installed DTS Components, It went fine and I was able to view DTS into SQL Server 2005 management studio
11- My system admin suggested to install SQL Server 2000 Service Pack 4, that was a great Idea, I installed Service pack 4 and the problem is solved now.
Conclusion:
Now, I am running SQL Server 2000 Enterprise Manager, SQL Server 2005 Management Studio with DTS view components. The main point is to check the service pack.
I hope it might help.
Thanks
Muhammad Essa Mughal
Toronto, Canada
Fantastic, Muhammad!! Yup, it worked like a charm. I simply installed SP4 and it worked right away; I didn't have to do any series of uninstalls/reinstalls/reboots. Thanks a ton! This will save me a lot of hastle.
Brian
Unfortunately I installed the sql2000 client only tools and then got this error dialog infinitely. Added and removed it and mmc is messed up too. I added it again and then installed sp4 and it Enterprise manager will still not run. I didn't need it until I tried to edit a package with a odbc connection to an as400 using the Rumba driver. It says the driver is not capable when I try to open the connection or edit the query. The packages run on the sql 2000 server. I just can't edit them now. I can open MS Query and create a query to those odbc connections. I am really interested in figuring out what the problem here is.
Steve
Hi;
I've been facing the same problem since last week, this morning I got it done. Here what I experienced.
...
11- My system admin suggested to install SQL Server 2000 Service Pack 4, that was a great Idea, I installed Service pack 4 and the problem is solved now.
Muhammad Essa Mughal
Toronto, Canada
The workaround works great!
If you are interested, you can also repair your MMC by installing the SQL Server 2000 Service Pack 3.
I am running into the same problem, and have try downloading and installing SQL 2000 SP4, but the problem still persists.
SQL 2000 SP4 has multiple files, can you tell me what you have downloaded and installed
I applied SP4 to my own computer only and not to the data base server because the problem is happening after I installed SQL Server Management Studio Express and added the SQL 2005 DTS.msi on my own computer. Do you need to install SP4 to the data base server also
Entry Point Not Found
---------------------------
The procedure entry point ProcessExecute@@YAXPAUHWND__@@PBG1@Z could not be located in the dynamic link library SEMSFC.dll.
---------------------------
I get a couple of those and then a seeminly unending supply of:
---------------------------
SQL Server Enterprise Manager
---------------------------
Connection to application object failed. Ensure that no program modules have been deleted.
---------------------------
---------------------------------------------------------------
Had the same problem today - encountered it after installing the Microsoft SQL Server 2000 DTS Designer Components , SQL2K service pack 4 fixed it for me.
Thanks a lot Muhammad!
Taslim Ngom
Atlanta, GA
Shouldn't running 2005 backward compatibility "repair" fix something like this
I uninstalled my 2000 client tools on my desktop.
I installed the SQL 2005 "eval"
I installed the 2000 DTS Designer Components (April 2006 build)
I ran the 2005 backward compatibility "repair." I modified the xml configuration file so that the 2000 DTS designer components would work. Without doing so, they wouldn't work. The 2005 install works. The 2000 DTS designer components work fine too.
However, now I go into My Computer, Management and I cannot get into anything under services. It crashes the MMC. It throws the same error as the one this thread is built around.
So I'm uninstalling SQL 2005 eval. I'm going to reinstall the 2000 client tools. I need to get into my other services.
I can't run "2000 SP4" to "fix this" because I don't have 2000 on this box.
Any ideas