Can't Remove Remote Svr which was computer's previous name 
Author Message
 Can't Remove Remote Svr which was computer's previous name

Having a problem installing Publishing on our SQL server 6.5.  Prior to
installing Publishing, the machine was formerly named SERVER1 (example
names), then changed to SERVER2.  In the enterprise manager, SERVER1 was
unregistered and SERVER2 (the new name) was registered.  The machine works
fine as far as can be seen.

Now, when trying to install publishing, An error pops up saying that
SERVER1 cannot be found to install publishing on it.  If I look under
remote servers, SERVER1 and SERVER2 are both listed.  If I choose SERVER1,
I get the same error message.  I then try to "Drop" it, and it disappears
from the list.  Going back to Remote Servers shows it in the list again.

Unless I can get rid of any reference to this SERVER1, I feel my life will
complicated.  It feels like an ex-significant-other.  Drop it and it
doesn't go away.  I haven't looked to the registry yet because I think it
may be held in some stupid binary DAT file.  Reinstalling is an absolute
last resort.

Ideas and possible solutions are much appreciated.



Thu, 25 May 2000 03:00:00 GMT
 Can't Remove Remote Svr which was computer's previous name

Remove both SERVER1 and SERVER2 from the table and using sp_addserver enter
(sp_addserver SERVER2, Local).

Quote:

>Having a problem installing Publishing on our SQL server 6.5.  Prior to
>installing Publishing, the machine was formerly named SERVER1 (example
>names), then changed to SERVER2.  In the enterprise manager, SERVER1 was
>unregistered and SERVER2 (the new name) was registered.  The machine works
>fine as far as can be seen.

>Now, when trying to install publishing, An error pops up saying that
>SERVER1 cannot be found to install publishing on it.  If I look under
>remote servers, SERVER1 and SERVER2 are both listed.  If I choose SERVER1,
>I get the same error message.  I then try to "Drop" it, and it disappears
>from the list.  Going back to Remote Servers shows it in the list again.

>Unless I can get rid of any reference to this SERVER1, I feel my life will
>complicated.  It feels like an ex-significant-other.  Drop it and it
>doesn't go away.  I haven't looked to the registry yet because I think it
>may be held in some stupid binary DAT file.  Reinstalling is an absolute
>last resort.

>Ideas and possible solutions are much appreciated.



Thu, 25 May 2000 03:00:00 GMT
 Can't Remove Remote Svr which was computer's previous name

I can't remove SERVER1 from the list using the Drop command. Actually, I
can't drop SERVER2 either. Is there another way I am missing?  Obviously, I
can't drop them if I unregister SERVER2.

BTW, the error message is "Unable to connect to site 'SERVER1' because
SERVER1 is not defined as a remote server at the site.'

Thanks for your efforts,

Dave Aoun



Quote:
> Remove both SERVER1 and SERVER2 from the table and using sp_addserver
enter
> (sp_addserver SERVER2, Local).
> >Now, when trying to install publishing, An error pops up saying that
> >SERVER1 cannot be found to install publishing on it.  If I look under
> >remote servers, SERVER1 and SERVER2 are both listed.  If I choose
SERVER1,
> >I get the same error message.  I then try to "Drop" it, and it
disappears
> >from the list.  Going back to Remote Servers shows it in the list again.



Fri, 26 May 2000 03:00:00 GMT
 Can't Remove Remote Svr which was computer's previous name

Anachostic,

I think this thread is getting quite confusing. Can you post me the output
from

select srvid,srvstatus,srvname,srvnetname from master..sysservers

What was the output from exec sp_dropserver "server1" ?

The local server must have a srvid of 0 is neither has or the wrong one has
then it can get a little messy.  The other problem with replication as well
is that the status of the server (subscriber/publisher/distributer) is also
held by the srvstatus field.

if you post the output up here with a listing next to each about what you
want it to do I will write the script to do it in the system tables for
you.

--
I hope this was of use.

Steve Robinson



Quote:
> I can't remove SERVER1 from the list using the Drop command. Actually, I
> can't drop SERVER2 either. Is there another way I am missing?  Obviously,
I
> can't drop them if I unregister SERVER2.

> BTW, the error message is "Unable to connect to site 'SERVER1' because
> SERVER1 is not defined as a remote server at the site.'

> Thanks for your efforts,

> Dave Aoun



> > Remove both SERVER1 and SERVER2 from the table and using sp_addserver
> enter
> > (sp_addserver SERVER2, Local).

> > >Now, when trying to install publishing, An error pops up saying that
> > >SERVER1 cannot be found to install publishing on it.  If I look under
> > >remote servers, SERVER1 and SERVER2 are both listed.  If I choose
> SERVER1,
> > >I get the same error message.  I then try to "Drop" it, and it
> disappears
> > >from the list.  Going back to Remote Servers shows it in the list
again.



Fri, 26 May 2000 03:00:00 GMT
 Can't Remove Remote Svr which was computer's previous name

They have now been removed by using 'delete from sysservers' on the master
db.  The error message still comes up.  Other interesting things are
happening now with Publishing, but I can't get past this one error message.
 Where else could it store that name?!

da

Quote:
> I can't remove SERVER1 from the list using the Drop command. Actually, I
> can't drop SERVER2 either. Is there another way I am missing?  Obviously,
I
> can't drop them if I unregister SERVER2.

> BTW, the error message is "Unable to connect to site 'SERVER1' because
> SERVER1 is not defined as a remote server at the site.'
> > Remove both SERVER1 and SERVER2 from the table and using sp_addserver
> enter
> > (sp_addserver SERVER2, Local).

> > >Now, when trying to install publishing, An error pops up saying that
> > >SERVER1 cannot be found to install publishing on it.  If I look under
> > >remote servers, SERVER1 and SERVER2 are both listed.  If I choose
> SERVER1,
> > >I get the same error message.  I then try to "Drop" it, and it
> disappears
> > >from the list.  Going back to Remote Servers shows it in the list

again.


Fri, 26 May 2000 03:00:00 GMT
 Can't Remove Remote Svr which was computer's previous name

I apologize for my over-concise-ness.  I tend to cram as much info in the
least amount of space sometimes.

Quote:
> select srvid,srvstatus,srvname,srvnetname from master..sysservers

srvid  srvstatus srvname                        srvnetname                

------ --------- ------------------------------
--------------------------------
1      9         RADIUSNT                       RADIUSNT                  

(this is the local server, with the new name)

Quote:
> What was the output from exec sp_dropserver "server1" ?

The server 'radius' does not exist.  Use sp_helpserver to show available
servers.
(Radius is the machine's prior name)  sp_helpserver shows:
name                           network_name                 status      id

------------------------------ ---------------------------- -----------
----
RADIUSNT                       RADIUSNT                     rpc,dist    1  

RADIUS    
(And a light is starting to come on, but I have no idea where to go)

Quote:
> The local server must have a srvid of 0 is neither has or the wrong one
has
> then it can get a little messy.  The other problem with replication as
well
> is that the status of the server (subscriber/publisher/distributer) is
also
> held by the srvstatus field.

The svrid is 1.  I think I can fix that one by removing and readding it.

Quote:
> if you post the output up here with a listing next to each about what you
> want it to do I will write the script to do it in the system tables for
> you.

You are very kind.  I have the SQL training books, but they do not cover
topics like this.  Do you have any recommendations for good SQL server
books?

Dave Aoun



Fri, 26 May 2000 03:00:00 GMT
 Can't Remove Remote Svr which was computer's previous name

Anachostic,

There are two ways you can do this - I would do the latter but I leave the
choice to you.
1.
exec sp_dropserver "RADIUSNT"
/* This will give you a clean table then */

exec sp_addserver "RADIUSNT",Local

*/

/* Then to reset the server options */
sp_serveroption 'RADIUSNT', 'dist', 'true'
go

The other way to do this is update the sysserver table.  
2.
use master
go
exec sp_configure "allow updates",1
reconfigure with override
update sysservers set srvid = 0 ans status = 8 where srvname = "RADIUSNT"
/*The reason why i drop srvstatus by 1 is because this denotes a remote
server - whic this is not. */
exec sp_configure "allow updates",0
reconfigure with override
go

The reason why i choose this method is because when I have lots of server
(110 in my case) dropping every one just so I can get the srvid = 0 is a
bit of a pain.


well
I hope everything is now ok - good luck

--
Steve Robinson MCP (SQL /NT)




Quote:
> I apologize for my over-concise-ness.  I tend to cram as much info in the
> least amount of space sometimes.

> > select srvid,srvstatus,srvname,srvnetname from master..sysservers
> srvid  srvstatus srvname                        srvnetname              

> ------ --------- ------------------------------
> --------------------------------
> 1      9         RADIUSNT                       RADIUSNT                

> (this is the local server, with the new name)

> > What was the output from exec sp_dropserver "server1" ?
> The server 'radius' does not exist.  Use sp_helpserver to show available
> servers.
> (Radius is the machine's prior name)  sp_helpserver shows:
> name                           network_name                 status    
id

> ------------------------------ ---------------------------- -----------
> ----
> RADIUSNT                       RADIUSNT                     rpc,dist    1


> RADIUS    
> (And a light is starting to come on, but I have no idea where to go)

> > The local server must have a srvid of 0 is neither has or the wrong one
> has
> > then it can get a little messy.  The other problem with replication as
> well
> > is that the status of the server (subscriber/publisher/distributer) is
> also
> > held by the srvstatus field.

> The svrid is 1.  I think I can fix that one by removing and readding it.

> > if you post the output up here with a listing next to each about what
you
> > want it to do I will write the script to do it in the system tables for
> > you.

> You are very kind.  I have the SQL training books, but they do not cover
> topics like this.  Do you have any recommendations for good SQL server
> books?

> Dave Aoun



Fri, 26 May 2000 03:00:00 GMT
 Can't Remove Remote Svr which was computer's previous name

The only part I found out that I was missing was stopping and restarting
the server.  After dropping and readding the correct server name,
restarting the service changed the server name.  

I have seen other posting by you and I'd like to thank you on behalf of
myself and others for sharing your expertise with SQL Server.

da

Quote:
> The reason why i choose this method is because when I have lots of server
> (110 in my case) dropping every one just so I can get the srvid = 0 is a
> bit of a pain.


be
> well
> I hope everything is now ok - good luck



Sat, 27 May 2000 03:00:00 GMT
 
 [ 8 post ] 

 Relevant Pages 

1. Jan's Name (Was: Re: I am being interviewed by OReilly)

2. Jan's Name (Was: Re: I am being interviewed by OReilly)

3. if you will promise Allahdad's swamp against cans, it will angrily depart the unit

4. Please ignore my previous 'urgent' posting

5. A change on computer's name prevents SQLSserver starts

6. Removing the -------- under the field name, in xp_sendmail's, att ach-result, header

7. after i change computer name, SQL 7.0 won't work

8. Changed computer name. MSSQL won't start

9. Trying to push a dynamic merge subscription using subscriber's computer name

10. SQL7 - Cannot remove filegroup with dash in it's name

11. SQL Won't Start After Changing Computer Name

12. Remote query: Can't select from database named 16k_data


 
Powered by phpBB® Forum Software