A production SQL server was accidentally moved (I found out about it
after the fact)from it's existing physical box (Windows Server 2003, SQL
Server 2000) to a virtual server.

I'm able to remote into the server & use enterprise manager from the
server, but cannot connect via Enterprise Manager that I had on my own
desktop.

I can get to it from SQL 2005, but cannot modify any DTS jobs since this
is a functioning server & changing it in SQL 2005 would make it so I
could not open the job on the server & change the DTS if needed. Also,
batches of stored procedures could be changed in bulk on SQL 2000, but I
can't pull but 1 stored procedure to edit at a time on SQL 2005.

The server appears to work fine, I can get to the server from Query
Analyzer on my local box (after I change the servername to be
servername.mydomain.com instead of servername).

In the wizard in Enterprise Manager, I see 2 instances of this server
showing up in the list there, both return the same error:

Specified SQL Server Not Found (connection.open(Connect())

If I try to add both of the servers to the Register SQL Server Wizard at
once, it hangs Enterprise Manager & crashes MMC.

Naturally, since the folks who moved it can see it via a Ping request,
remote desktop and from within SQL 2005, it is "my fault" that this SQL
2000 Enterprise Manager isn't working right.

Any ideas/suggestions appreciated.

BC

Hi BC

That's one interesting problem that you have. At first, I would have thought
that there might be a firewall issue or something that is blocking the
traffic between your system and the virtual server. But you've mentioned that
you can connect to it using SQL Server 2005 (I am assuming the SSMS), and
Query Analyzer. I guess there are more questions, when you said that the SQL
has been moved to a virtual server environment, does it being moved using
imaging? Is the server name and IP address stays the same?

Not sure if you have tried this, but just trying to throw some ideas to see
if it might work in your case:
-. Have you tried to add the server registration within the Enterprise
Manager using IP address, instead of server name?
-. Can you check that the server is still running on port 1433? If yes have
you tried to hard coded it when registering the server in the Enterprise
Manager? So to register it, use the following: <server name>,1433 or <ip
address>,1433.

Thank you
Lucas

"Blasting Cap" wrote:

I've tried the two suggestions, and here's what happens in both cases:

Using IP address - it gives me the message: "SQL Server does not exist
or access denied (ConnectionOpen(Connect()).

Using name + 1433, it gives the same thing.

Finally, using ip + 1433, it connected. I do not know why though.

Thank you for the help. Any ideas why it works with IP and not with
name any more?

BC

Lucas Kartawidjaja wrote:

There could be several reasons as to why it works using IP address but not
server name. You've mentioned that when you tried to connect using Query
Analyzer, you need a fully qualified domain name, such as server.domain.com.
By any chance the new virtual box resides on different domain as your system?

I guess, try running nslookup servername on the command prompt, and see if
it gives the same IP address as your SQL Server? Or try to ping the
servername?

Another one is that if the IP address of your virtual server is different
than the physical server but the name is the same, then there might be some
cache that need to be clear out. You can use ipconfig /flushdns for that.
Just a few suggestions. But try to do ping and nslookup first and see if the
servername points to the correct IP address.

"Blasting Cap" wrote: