dbTalk Databases Forums  

Msg 18483 (could not connect because not defined as a login) but a little different

microsoft.public.sqlserver.replication microsoft.public.sqlserver.replication


Discuss Msg 18483 (could not connect because not defined as a login) but a little different in the microsoft.public.sqlserver.replication forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Aikon
 
Posts: n/a

Default Msg 18483 (could not connect because not defined as a login) but a little different - 05-19-2006 , 07:44 AM






We have a two-server configuration where the distributor and subscriber
reside on the same physical server, and the publisher resides on
another. Recently, two of our jobs responsible for recreating UDA
replication have been receiving the following error:

Msg 18483, Sev 14: Could not connect to server '<distributor/subscriber
server name>' because '(null)' is not defined as a remote login at the
server. [SQLSTATE 42000]

This is a little different than the much-discussed 'distributor_admin'
not being defined, for which the solution is to make sure that SQL
Server i using the correct server name (such as SELECT@@Servername).

Any help would be appreciated =D

-Scott


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.