SQLServer2005_DTS.msi install corrupts SQL 2000 Client

  • From my desktop, I've been using SQL 2005 and SQL 2000 clients in unison with no problem.  Today, I installed SQLServer2005_DTS.msi and it disabled my SQL 2000 client.  Error Msg:

    The procedure entry point ?ProcessExecute@YAXPAUHWND_@@PBG1@Z could not be located in the dynamic link library SEMSFC.dll

    SQL 2005 runs fine (and I can now edit and execute my 2000 DTS pkg's)

    SQL 2000 is hosed !!!  Is there a quick remedy to get SQL 2000 Client working again in this scenario?

     

    BT
  • Re-Installing the SQL 2000 client tools, is probably the easiest fix.

  • Problem resolved.  Exact sequence of events:

    -- Installed 2000 SP4 only & bounced my desktop (problem persisted)

    -- re-Installed SQL 2000 STD edition w/ explicit INSTANCE name & bounced my desktop (problem persisted)

    -- Installed 2004 SP4 (PROBLEM RESOLVED!!!)

    I now have access to SQL 2000, SQL 2005 (both w/ access to Edit & Execute DTS pkg's)

    BT
  • I'm confused by something; you said you were successfully running 2000 and 2005 clients simultaneously, but when you reinstalled 2000, you gave it an explicit instancename. So, you reinstalled the full SQL Server 2000?

  • It's been a while but I will tell you that if you plan on installing SQL 2005 Management Studio on the same desktop w/ SQL Server 2000 Enterprise Manager, BE SURE TO GIVE YOUR "SQL 2005" a NAMED INSTANCE. If you proceed installing SQL 2005, w/ the default instance, you'll corrupt the kernal for SQL 2000. (SQL 2005 will operate fine but SQL 2000 will not start up correctly if at all) At least this was our shops experience. Once we started supplying NAMED INSTANCES for SQL 2005 desktop installations, we found that both products operated fine.

    BT
  • Hi,

    Can you tell me what is sql server 2004 sp4.

    I think its typing error.

    Pls clarify

  • Yes - typo. I meant to type SQL 2000 SP4

    BT

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply