SQL Server 2000 and 2005 co-existence problems

[thomas_vicker]

Hi,

I need to maintain both SQL Server 2000 and 2005 on my PC for support
purposes. I am using the developer additions. After I install
everything (with no install errors) I can use SQL 2005 Mgt Studio fine
until I bring up SQL 2000 Query Analyzer or Enterprise Mgr. After that,
I cannot bring up SQL 2005 Mgt Studio. It get this message:

Package 'Microsoft SQL Management Studio package' failed to load

I click OK, the message comes up again, I click OK again and then Mgt
Studio disappears.

My default instance is under SQL 2000 and I created a named instance
under SQL 2005 on my PC both with Local System Account.

My order of installs was:

1) SQL Server 2000 (Server tools)
2) SQL Server 2000 SP4
3) SQL Server 2005 (DB Engine, Integration Services, and Workstation
components)

I also have .NET 2005 Professional installed.

The frustrating thing is I can find no log information anywhere --
event log, under my Documents and Settings, or in the SQL Server 2005
directories where it was installed.

My guess is that when I used Query Analyzer it changed a setting
somewhere or prevented me from using Mgt Studio somehow, but I just
can't figure out what it did. I'd like to avoid a complete re-install
where it may just happen again.

Any help would be appreciated. Thanks much.

Tom Vicker

[jim_geissman]

I wonder if it would help to install SQL 2005 SP1.

Jim

[Erland Sommarskog]

th***********@s tandardandpoors .com (th***********@ standardandpoor s.com)
writes:

I need to maintain both SQL Server 2000 and 2005 on my PC for support
purposes. I am using the developer additions. After I install
everything (with no install errors) I can use SQL 2005 Mgt Studio fine
until I bring up SQL 2000 Query Analyzer or Enterprise Mgr. After that,
I cannot bring up SQL 2005 Mgt Studio. It get this message:

Package 'Microsoft SQL Management Studio package' failed to load

Very strange. I have both the SQL 2000 and SQL 2005 tools on my machine,
and they co-exist very well.

I also find it difficult that QA or EM would wreak something havoc for
Mgmt Studio, as QA and EM are native code, and Mgmt Studio is a .Net
application.

I think Jim's suggestion of installing SP1 SQL 2005 is a good idea.
Not because that SP1 may have a fix as such to the problem, but there
is a good chance that it will repair whatever that is broken.
--
Erland Sommarskog, SQL Server MVP, es****@sommarsk og.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx