Error while synchronizing merge replication for first time

I am trying to run the replication merge agent for the first time for a
replication. Several servers already replicate to the same server without
problems. I have replicated all the previous Publishers to my subscriber
with the identical setup with the exception of the user login into the
server. The user login sees the appropriate tables in the subscriber yet the
first synchronization errors with the following:
rror messages:
The process could not connect to Subscriber 'hera'. (Source: MSSQL_REPL,
Error number: MSSQL_REPL20084) Get help: http://help/MSSQL_REPL20084 Named
Pipes Provider: Could not open a connection to SQL Server [53].
(Source: MSSQLServer, Error number: 53)
Get help: http://help/53
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the fact
that under the default settings SQL Server does not allow remote
connections. (Source: MSSQLServer, Error number: 53) Get help:
http://help/53 Login timeout expired (Source: MSSQLServer, Error number: 0)
Get help: http://help/0 The merge process failed to execute a query because
the query timed out.
If this failure continues, increase the query timeout for the process.
When troubleshooting, restart the synchronization with verbose history
logging and specify an output file to which to write. (Source:
MSSQLServer, Error number: 0)
Get help: http://help/0
The subscription to publication 'PUB_1' could not be verified. Ensure that
all Merge Agent command line parameters are specified correctly and that the
subscription is correctly configured. If the Publisher no longer has
information about this subscription, drop and recreate the subscription.
(Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201019) Get help:
http://help/MSSQL_REPL-2147201019
Have any of you seen this error before? Do you know of a possible solution?
Thank you,
Pete Ocasio
Senior Software Developer
It sounds like the publisher login or the distributor login does not have
sufficient rights to pull the subscription.
Verify the subscriber can connect to the publisher - try a ping and map a
drive to the publisher from the subscriber and then verify the distributor
login assigned on the subscriber is in the dbo_role on the publisher and the
publisher login defined on the subscriber is in the pal on the publisher.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Pete Ocasio" <pete.ocasio@.execupay.com> wrote in message
news:O5cWeJ9RIHA.4888@.TK2MSFTNGP02.phx.gbl...
>I am trying to run the replication merge agent for the first time for a
>replication. Several servers already replicate to the same server without
>problems. I have replicated all the previous Publishers to my subscriber
>with the identical setup with the exception of the user login into the
>server. The user login sees the appropriate tables in the subscriber yet
>the first synchronization errors with the following:
> rror messages:
> The process could not connect to Subscriber 'hera'. (Source: MSSQL_REPL,
> Error number: MSSQL_REPL20084) Get help: http://help/MSSQL_REPL20084 Named
> Pipes Provider: Could not open a connection to SQL Server [53].
> (Source: MSSQLServer, Error number: 53)
> Get help: http://help/53
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the fact
> that under the default settings SQL Server does not allow remote
> connections. (Source: MSSQLServer, Error number: 53) Get help:
> http://help/53 Login timeout expired (Source: MSSQLServer, Error number:
> 0) Get help: http://help/0 The merge process failed to execute a query
> because the query timed out.
> If this failure continues, increase the query timeout for the process.
> When troubleshooting, restart the synchronization with verbose history
> logging and specify an output file to which to write. (Source:
> MSSQLServer, Error number: 0)
> Get help: http://help/0
> The subscription to publication 'PUB_1' could not be verified. Ensure that
> all Merge Agent command line parameters are specified correctly and that
> the subscription is correctly configured. If the Publisher no longer has
> information about this subscription, drop and recreate the subscription.
> (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201019) Get help:
> http://help/MSSQL_REPL-2147201019
> Have any of you seen this error before? Do you know of a possible
> solution?
> Thank you,
> Pete Ocasio
> Senior Software Developer
>