September 18, 2005 at 9:25 pm
HI,
I am trying to setup merge replicaton , for the first time it worked fine but when i implemented on real server it gives error that rempote login doesnt exists.
So i disabled the published and subscriber and setup again .
But still it giving me error that remote login doesnt exists.
thanx
from
Killer
September 18, 2005 at 10:05 pm
You must check your server name before create the publication, please check with @@SERVERNAME, the server name must be in the list.
If the server name not in the list, you must add the server name with the "sp_addserver". For complete reference please follow the BOL.
September 19, 2005 at 1:19 am
Hi,
Ichecked everything.I have remote server ( subscriber) and mapped logins.
but still i am getting the same error.
from
Killer
September 19, 2005 at 1:41 am
Could you please to specified the error message?
September 19, 2005 at 4:00 am
sql server could not configure database as distributor for database( i am making distrubutor on my local database only)
error 14114 (null) is not configured as distributor.
i solved the error and recreated the remote server but stil now it is giving me error.
the second error is the remote login not mapped.
but i wanted to know that do i have to make the remote server of the subscriber database or the local database.
and do i have to make the remote login on subscriber also.
hope u understand.
from
Killer
September 19, 2005 at 4:49 am
Dear Raj,
I'm sure that is because the servername, please refer to the BOL in the section sp_addserver
September 19, 2005 at 9:38 am
Dear Deni,
I used to the below to create a linked server or remote server
exec sp_addserver 'ipaddress' or computername
EXEC sp_addremotelogin 'ipaddress or computername', 'sa', 'sa'
GO
EXEC sp_remoteoption 'ipaddress or computername', 'sa', 'sa', trusted, true
GO
EXEC sp_configure 'remote access', 1
RECONFIGURE
I wanted to ask u that do i have to create the remote server on the server which i will give as subscription database in the replication.
secondly the remote user should be present on both the server.
hope u understand.
from
Killer
September 19, 2005 at 7:50 pm
I think the 'local' option in the sp_addserver must be specified, because you configure the replication in the local machine, right?
September 19, 2005 at 9:09 pm
Hi,
Now the error is as follows
Error: 18483 : could not connect to server(server name) because distributor_admin is not defined as remote login at the server.
from
Killer
September 19, 2005 at 9:45 pm
Now you add the user id (distributor_admin) to the remote server as a remote login
September 20, 2005 at 2:42 am
Hi Dear,
I added the distributor_admin as remote login.
But still i am deep in the hell.
the Error is :
error :21007 Cannot add the remote Distributor. Make sure that the local server is configured as a Publisher at the Distributor.
hope i will be out of this hell
from
Killer
September 20, 2005 at 10:06 pm
Have you looked through this KB article?
http://support.microsoft.com/?id=321822
When your deep in hell, the best thing I find is to roll everything back to the point where it's like nothing happened, then start over again.
--------------------
Colt 45 - the original point and click interface
September 20, 2005 at 10:10 pm
Also, have you run SELECT @@SERVERNAME on both servers and verified that the name is not set to null?
--------------------
Colt 45 - the original point and click interface
September 21, 2005 at 2:25 am
Hi,
I had disabled the replication 3 times but still the same error.
i looked in that artical before i posted my question.
from
Killer
September 21, 2005 at 2:31 am
Hi Phill,
If u seen the discussion the u might have read then u might have seen that i am out of that problem.
I means to say that if @@servername is null then i have not faced another error and so on.
But thanx this doesn't helped me
from
Killer
Viewing 15 posts - 1 through 15 (of 34 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy