October 9, 2007 at 8:02 am
We have legacy dbs / servers running Sql SErver 2000, but are moving new servers to 2005. Our network folks loaded 2005 Management Studio on my desktop, where I already had 2000 Enterprise Manager installed.
Now I can't open Enterprise Manager, I get an error:
The procedure entry point ?ProcessExecute@@YAXPAUHWND__@PBG1@Z could not be located in teh dynamic link library SEMSFC.dll.
If I click ok, I'm then asked if I want to debug using the Visual Studio debugger -- but I'm unfamiliar with that so it doesn't help me.
Our network folks did uninstall / Reinstall Enterprise Manager, but that also didn't help.
We do use DTS packages extensively and have not converted them to SSIS. While I can work with them in 2005, there are somethings about 2000 that worked better.
Any help / hints / thoughts?
October 9, 2007 at 8:30 am
There are quite a few things that you can't do in Enterprise Manager against 2005 servers. You'll need to move to SSMS.
There's a facility for running DTS packages in 2005. Not sure about editing. Someone else will have to chime in there.
October 9, 2007 at 8:36 am
Usually installing 2005 after 2000 does not cause problems, however installing 2000 (or just the tools) after 2005 has been installed is known to create problems "sometimes". Recommend trying to install 2000 SP4 and if that doesn't help then uninstall 2005, uninstall 2000, reboot, install 2000, install 2000 SP4, reboot, install 2005 and see if problem clears up. No promises but I've seen other complaints about this problem and recall that the SP4 seemed to help.
HTH,
James.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply