Installed SQL2005: now can't access SQL2000 (Local) in EM

After installing SQL2005 (with a new instance), I couldn't access my previous
(local) server through Enterprise Mnager, although I can access it through
Query Analyser.
I deleted the connection in Enterprise manager and tried to recreate it
(using either windows security or SQL Autentication): get the message 'Client
unable to establish connection. TCP Provider: No connection could be made
because the target machine actively refused it.'Ashley,
Earlier versions of SQL Server 2005 had a tendancy to trash the SQL Server
2000 tools, perhaps this is your issue. I always put SQL 2005 into a virtual
machine and will keep it there until it RTMs, unless I can install it on a
fresh machine without SQL Server 2000 on.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Ashley Brewerton" wrote:
> After installing SQL2005 (with a new instance), I couldn't access my previous
> (local) server through Enterprise Mnager, although I can access it through
> Query Analyser.
> I deleted the connection in Enterprise manager and tried to recreate it
> (using either windows security or SQL Autentication): get the message 'Client
> unable to establish connection. TCP Provider: No connection could be made
> because the target machine actively refused it.'|||You should re-register SQLDMO.DLL using:
regsvr32 "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\sqldmo.dll"
Razvan|||Thanks Razvan: after restarting the services that worked perfectly.
Ashley
"Razvan Socol" wrote:
> You should re-register SQLDMO.DLL using:
> regsvr32 "C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\sqldmo.dll"
> Razvan
>