How is the network relationship set up? If this is a non-
trusted relationship, you'll need to register an alias in
the client network utility on the subscriber, and place
an entry in the hosts file there also.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Paul,
Thank you for your reply.
This is a non-trusted relationship.I registered a client network utility
with the alias pointing to my publisher/ distributor and added an entry in
the host file also.
But still I 'm getting this same message in the job history:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
What is wrong am I doing?
Sam
"Paul Ibison" wrote:
> How is the network relationship set up? If this is a non-
> trusted relationship, you'll need to register an alias in
> the client network utility on the subscriber, and place
> an entry in the hosts file there also.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Also I tried to push the subscription instead of pullin git from subscriber.
But in push subscription , the merge agent throws this error:
The remote server is not defined as a subscription server.
How do I set up the remote server as subscription server?
The merge agent does transfers lot of data and objects from publisher to
subscriber , it is sometime at the end of the process , it fails.
Please advice..
Sam
"Paul Ibison" wrote:
> How is the network relationship set up? If this is a non-
> trusted relationship, you'll need to register an alias in
> the client network utility on the subscriber, and place
> an entry in the hosts file there also.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Sam,
have you set up FTP for the initialization? Have a look at this article:
http://support.microsoft.com/?id=321822
Also, check that the correct port has been opened up on the firewall (port
1433 for default instance of SQL Server, by default).
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment