Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-01-01 : 15:08:29
|
| Dick writes "Hi all,We're running two SQL-servers 7. Replication between them has been running fine for months. Due to new conventions we had to change the W2K-Server name of one of them. (lets say ServerOld to ServerNew) This induced all kinds of problems to the SQL-server. All of them have been solved but one: replication.I dropped all subscriptions and publications. The name of the distribution agent however kept saying ServerOld. Since this property cannot be changed, every new publication I made through the wizard kept pointing to ServerOld and didn't work.I de-installed publishing and distribution, restarted the server and tried to re-install it (Tools, Replication, Configure publishing...). During the wizard, everything went well, all values pointed to ServerNew. However, when I click finish, the following error message appears: ------SQL Server Enterprise Manager could not configure 'ServerNew' as the distributor for ServerNew.Error 18483: Could not connect to server 'ServerOld' because 'distributer_admin' is not defined as a remote login at the server.Remote logins for remote server 'repl_distributor' have been dropped.Server dropped.Server added.Server network name set.-----Does anybody have any idea whether this error has anything to do with the renaming, how I can delete that pointer to ServerOld, and most importantly: How i can get replication back to work?Thanks in advance,Dick Koers." |
|
|
|
|
|
Publishing and distribution cannot be (re)configured