Problem removing remote server (6.5) from master..sysservers

Problem removing remote server (6.5) from master..sysservers

Post by Scott Smit » Sat, 27 Feb 1999 04:00:00



We are trying to get rid of an annoying little message that has just started
happening this morning.  The message is "Unable to connect to site 'HRNT2'
because 'HRNT3' is not defined as a remote server at the site".  It occurs
when we try to access HRNT3 through the SQL Enterprise Manager, and also if
you use the Servers|Remote Servers menu item.

Background:  We have 2 SQL servers in operation - HRNT3 AND HRNT4, both of
them are NT4 Servers.  This morning I was trying to set up a link on HRNT3
for doing remote procedure calls.  My original thought was to use the sa
account for this link, and started to implement it through Servers|Remote
Servers.  I then thought better of it and used the "Drop Login" button to
get rid of it (the one at the bottom of the dialog, not the one at the top
right, below the Modify button).  Now we are getting the aforementioned
error message.

HRNT2 is an NT server on our network, but all it does is Exchange 5.5.
Several months ago HRNT2 had SQL and Exchange on it, but we got the separate
box for Exchange and moved it off, keeping the name HRNT2.  We then renamed
the original box to HRNT4 and kept SQL on it.

I used sp_helpserver to show a list of servers that HRNT3 is seeing, and
HRNT2 is listed there.  We tried to drop it from the list through the
Servers|Remote Servers menu, but it wouldn't stay dropped.  (This time we
used the Drop button, not the Drop Login button)

We haven't tried sp_dropserver yet.  Would that be the way to get rid of
that entry, or is there some other way?

My other question would be is there some other place that feeds that system
table where these databases are stored, and would refresh it if an entry was
deleted?

Scott Smith
Human Resource Information Systems
Michigan State University

 
 
 

Problem removing remote server (6.5) from master..sysservers

Post by Steve Robinso » Tue, 02 Mar 1999 04:00:00


Scott,

The entry for this is in master..sysservers and the way to remove it is

exec sp_dropserver "server name"

if you need to add a new one then

exec sp_addserver "server name"

This will set it up as a remote server unless you use the local keyword.

The only issue with this is if you have replication set up.  The server ID
is used in replication so dropping and adding servers may change these
number and give you loads of problems.

Steve Robinson
SQLServer MVP



>We are trying to get rid of an annoying little message that has just
started
>happening this morning.  The message is "Unable to connect to site 'HRNT2'
>because 'HRNT3' is not defined as a remote server at the site".  It occurs
>when we try to access HRNT3 through the SQL Enterprise Manager, and also if
>you use the Servers|Remote Servers menu item.

>Background:  We have 2 SQL servers in operation - HRNT3 AND HRNT4, both of
>them are NT4 Servers.  This morning I was trying to set up a link on HRNT3
>for doing remote procedure calls.  My original thought was to use the sa
>account for this link, and started to implement it through Servers|Remote
>Servers.  I then thought better of it and used the "Drop Login" button to
>get rid of it (the one at the bottom of the dialog, not the one at the top
>right, below the Modify button).  Now we are getting the aforementioned
>error message.

>HRNT2 is an NT server on our network, but all it does is Exchange 5.5.
>Several months ago HRNT2 had SQL and Exchange on it, but we got the
separate
>box for Exchange and moved it off, keeping the name HRNT2.  We then renamed
>the original box to HRNT4 and kept SQL on it.

>I used sp_helpserver to show a list of servers that HRNT3 is seeing, and
>HRNT2 is listed there.  We tried to drop it from the list through the
>Servers|Remote Servers menu, but it wouldn't stay dropped.  (This time we
>used the Drop button, not the Drop Login button)

>We haven't tried sp_dropserver yet.  Would that be the way to get rid of
>that entry, or is there some other way?

>My other question would be is there some other place that feeds that system
>table where these databases are stored, and would refresh it if an entry
was
>deleted?

>Scott Smith
>Human Resource Information Systems
>Michigan State University



 
 
 

Problem removing remote server (6.5) from master..sysservers

Post by Scott Smit » Wed, 03 Mar 1999 04:00:00


We did try that and got the original error message:  "Unable to connect to
site 'HRNT2'
because 'HRNT3' is not defined as a remote server at the site".

>Scott,

>The entry for this is in master..sysservers and the way to remove it is

>exec sp_dropserver "server name"

>if you need to add a new one then

>exec sp_addserver "server name"

>This will set it up as a remote server unless you use the local keyword.

>The only issue with this is if you have replication set up.  The server ID
>is used in replication so dropping and adding servers may change these
>number and give you loads of problems.

>Steve Robinson
>SQLServer MVP



 
 
 

Problem removing remote server (6.5) from master..sysservers

Post by Robert L. Klub » Thu, 04 Mar 1999 04:00:00


Scott,

I too have received that error message.  Our systems are installed from a
clone server, so the local server is always set up the same.

The question is how do we drop the remote server form the list (which is not
possible through the query or drop down menus)  Where is the setting stored?
How do we change the server ID structure?

Robert

System Specs: SQL 6.5 + SP5a, NT4 + SP 3 + OP


>We are trying to get rid of an annoying little message that has just
started
>happening this morning.  The message is "Unable to connect to site 'HRNT2'
>because 'HRNT3' is not defined as a remote server at the site".  It occurs
>when we try to access HRNT3 through the SQL Enterprise Manager, and also if
>you use the Servers|Remote Servers menu item.

>Background:  We have 2 SQL servers in operation - HRNT3 AND HRNT4, both of
>them are NT4 Servers.  This morning I was trying to set up a link on HRNT3
>for doing remote procedure calls.  My original thought was to use the sa
>account for this link, and started to implement it through Servers|Remote
>Servers.  I then thought better of it and used the "Drop Login" button to
>get rid of it (the one at the bottom of the dialog, not the one at the top
>right, below the Modify button).  Now we are getting the aforementioned
>error message.

>HRNT2 is an NT server on our network, but all it does is Exchange 5.5.
>Several months ago HRNT2 had SQL and Exchange on it, but we got the
separate
>box for Exchange and moved it off, keeping the name HRNT2.  We then renamed
>the original box to HRNT4 and kept SQL on it.

>I used sp_helpserver to show a list of servers that HRNT3 is seeing, and
>HRNT2 is listed there.  We tried to drop it from the list through the
>Servers|Remote Servers menu, but it wouldn't stay dropped.  (This time we
>used the Drop button, not the Drop Login button)

>We haven't tried sp_dropserver yet.  Would that be the way to get rid of
>that entry, or is there some other way?

>My other question would be is there some other place that feeds that system
>table where these databases are stored, and would refresh it if an entry
was
>deleted?

>Scott Smith
>Human Resource Information Systems
>Michigan State University


 
 
 

1. Problem removing remote server (6.5) from master..sysservers

We are trying to get rid of an annoying little message that has just started
happening this morning.  The message is "Unable to connect to site 'HRNT2'
because 'HRNT3' is not defined as a remote server at the site".  It occurs
when we try to access HRNT3 through the SQL Enterprise Manager, and also if
you use the Servers|Remote Servers menu item.

Background:  We have 2 SQL servers in operation - HRNT3 AND HRNT4, both of
them are NT4 Servers.  This morning I was trying to set up a link on HRNT3
for doing remote procedure calls.  My original thought was to use the sa
account for this link, and started to implement it through Servers|Remote
Servers.  I then thought better of it and used the "Drop Login" button to
get rid of it (the one at the bottom of the dialog, not the one at the top
right, below the Modify button).  Now we are getting the aforementioned
error message.

HRNT2 is an NT server on our network, but all it does is Exchange 5.5.
Several months ago HRNT2 had SQL and Exchange on it, but we got the separate
box for Exchange and moved it off, keeping the name HRNT2.  We then renamed
the original box to HRNT4 and kept SQL on it.

I used sp_helpserver to show a list of servers that HRNT3 is seeing, and
HRNT2 is listed there.  We tried to drop it from the list through the
Servers|Remote Servers menu, but it wouldn't stay dropped.  (This time we
used the Drop button, not the Drop Login button)

We haven't tried sp_dropserver yet.  Would that be the way to get rid of
that entry, or is there some other way?

My other question would be is there some other place that feeds that system
table where these databases are stored, and would refresh it if an entry was
deleted?

Scott Smith
Human Resource Information Systems
Michigan State University

2. No Source Error Rows file when error in ActiveX Transformation

3. Problems 'Removing' SQL Server 6.5

4. Replicating into message queues

5. sql 6.5 and Remote server sql 7.0 problem

6. Live online chat with MSFT experts

7. Permissions on master..sysservers

8. tuning tool on the web

9. Incorrect Backupserver entry in sysservers system table in master database

10. Multi-master Replication: Add/Remove Master Sites

11. Remote login from SQL Server 4.21a (Alpha) to SQL Server 6.5 (Intel)

12. SQL 6.5 Remote Server to SQL 7 Linked Server

13. 7.0 server use Remote Stored Proc to 6.5 server