Replication nightmare... - SQL Server Forums

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.

All Forums

SQL Server 2000 Forums

Import/Export (DTS) and Replication (2000)

Replication nightmare...

Author

Topic

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2001-12-17 : 09:07:48

Brooks writes "I posted to the forums a while ago: http://www.sqlteam.com/Forums/topic.asp?TOPIC_ID=10933

In short, I've got a production server that refuses to configure replication, mostly with the 18483 (not 18484, as I mistakenly said in that post) error: distributor_admin is not a remote login.

So last night, around 2am, I did the huge project of detaching all of my databases, uninstalling SQL server, reinstalling SQL server + SP1 (still scared of SP2; this is a production server), and re-attaching my databases. I intentionally did not restore Master or MSDB (I scripted my various jobs and maintenance plans).

So this morning I think it's got to be fixed and go to set up replication... and run into the same problem! Argh!

I've played around with the properties of the remote server, checking the "map all remote logins to..." and setting it to SA. I'm not sure if that's better or worse; replication setup still fails, but this time with the message "Error 18456: Login failed for user 'sa'".

What could be going on here? It's a fresh install, for all practical purposes. I've tried only selecting Pubs to replicate, in case it doesn't like the DB's I reattached. No go.

Help!
-Brooks"

ryanston
Microsoft SQL Server Product Team

89 Posts

Posted - 2001-12-18 : 17:42:32

Hello,

I would recommend that you verify the following:

1. Verify that SELECT @@SERVERNAME returns the correct server name. If not run sp_dropserver <your_server>, 'droplogins' and sp_addserver <your_server>, 'local'. Cycle the server and try again.
2. Verify that you have no aliases configured in the SQL client network utility. If you have these configured, remove them (if possible) and try configuring replication again.
3. Verify that you haven't registered your SQL Servers using IP addresses. Use NetBIOS names if possible.

If none of these works, can you post the output of sp_helpserver for us?

Thanks!
--R

quote:

Brooks writes "I posted to the forums a while ago: http://www.sqlteam.com/Forums/topic.asp?TOPIC_ID=10933

In short, I've got a production server that refuses to configure replication, mostly with the 18483 (not 18484, as I mistakenly said in that post) error: distributor_admin is not a remote login.

So last night, around 2am, I did the huge project of detaching all of my databases, uninstalling SQL server, reinstalling SQL server + SP1 (still scared of SP2; this is a production server), and re-attaching my databases. I intentionally did not restore Master or MSDB (I scripted my various jobs and maintenance plans).

So this morning I think it's got to be fixed and go to set up replication... and run into the same problem! Argh!

I've played around with the properties of the remote server, checking the "map all remote logins to..." and setting it to SA. I'm not sure if that's better or worse; replication setup still fails, but this time with the message "Error 18456: Login failed for user 'sa'".

What could be going on here? It's a fresh install, for all practical purposes. I've tried only selecting Pubs to replicate, in case it doesn't like the DB's I reattached. No go.

Help!
-Brooks"

aiken
Aged Yak Warrior

525 Posts

Posted - 2001-12-22 : 02:28:55

Definitely verified the items you suggest.

Here's the output from sp_helpserver when replication is "installed" (upon getting that error). If I uninstall replication, the results are the same except, of course, "repl_distributor" doesn't exist.


name			network_name			status						id	coallation_name		connect_timeout		query_timeout
repl_distributor	SA111                       	rpc,dist,rpc out,system,use remote collation	2   	NULL			0			0
sa111			sa111                       	rpc,sub,rpc out,use remote collation		1   	NULL			0			0

Thanks for any and all insight!
-b

aiken
Aged Yak Warrior

525 Posts

Posted - 2002-01-03 : 11:43:51

I'm still pulling my hair out over this one.... if anyone has any ideas, please post!

Thanks!
-b

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources