Hi,
We have a product that configures on SQL 2000 and also configures the
replication. We are in the process of doing R&D on SQL 2005.
Following are my machine specifications
OS Type : Windows 2000 Server (SP4)
SQL Server : SQL 2005
When i try to create a publisher and a subscriber, on the subscriber
machine, Replication Job gives an error message 'Agent message code 20084.
The process could not connect to Distributor '[Machine Name]'.'
I have tried using SQL Server accounts and Windows Authentication accounts,
but both are giving same error message.
Any ideas?
Thanks
Ahmed Awais
SSE Title Developments
Can you connect using SSMS from the subscriber to the publisher? Also, has
the servername changed recently ie what does select @.@.servername return on
the distributor?
Paul Ibison
|||Yes i can connect publisher from subscriber using SSMS and server name is not
changed. Query return the same servername which i am using.
"Paul Ibison" wrote:
> Can you connect using SSMS from the subscriber to the publisher? Also, has
> the servername changed recently ie what does select @.@.servername return on
> the distributor?
> Paul Ibison
>
|||OK - on the distribution agent can you enable logging and we'll see if there
is any more info we can get: http://support.microsoft.com/?id=312292.
Also, are you replicating across non-trusted networks, and can you ping the
distributor from the subscriber?
Cheers,
Paul Ibison
Tuesday, February 21, 2012
Replication implementation hurdles.
Labels:
configures,
database,
following,
hurdles,
implementation,
microsoft,
mysql,
oracle,
process,
product,
replication,
server,
sql,
thereplication
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment