Merge agent failure after IP change

I setup merge replication yesterday on Client A and was successful.
Today I changed the gateway and DNS info.; re-ran merge agent and got this
error.
Error messages:
The merge process could not connect to the Publisher 'XXUSSHU18UT:Process'.
Check to ensure that the server is running. (Source: MSSQL_REPL, Error
number: MSSQL_REPL-2147198719)
Get help: http://help/MSSQL_REPL-2147198719
The process could not connect to Publisher 'XXUSSHU18UT'. (Source:
MSSQL_REPL, Error number: MSSQL_REPL20084)
Get help: http://help/MSSQL_REPL20084
Unable to complete login process due to delay in opening server connection
(Source: MSSQLServer, Error number: 0)
Get help: http://help/0
After I changed the IP info. (put back original Gateway IP) the merge agent
ran successful.
What/where do these changes get applied that would alter merge agent from
running?
BTW, I also removed the gateway completely on Cleint A and the merge agent
continued to run successfully again. However I do need the new gateway (the
one that is not working for merge).
thx..
Are you perhaps using an alias on the subscriber? This would explain the IP
address mapping and its relationship to the replication setup.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Is this push or pull?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"bt7403" <bt7403@.discussions.microsoft.com> wrote in message
news:230FE02E-2D00-44EF-9D1D-A6C3A42C6175@.microsoft.com...
>I setup merge replication yesterday on Client A and was successful.
> Today I changed the gateway and DNS info.; re-ran merge agent and got this
> error.
> Error messages:
> The merge process could not connect to the Publisher
> 'XXUSSHU18UT:Process'.
> Check to ensure that the server is running. (Source: MSSQL_REPL, Error
> number: MSSQL_REPL-2147198719)
> Get help: http://help/MSSQL_REPL-2147198719
> The process could not connect to Publisher 'XXUSSHU18UT'. (Source:
> MSSQL_REPL, Error number: MSSQL_REPL20084)
> Get help: http://help/MSSQL_REPL20084
> Unable to complete login process due to delay in opening server connection
> (Source: MSSQLServer, Error number: 0)
> Get help: http://help/0
> After I changed the IP info. (put back original Gateway IP) the merge
> agent
> ran successful.
> What/where do these changes get applied that would alter merge agent from
> running?
> BTW, I also removed the gateway completely on Cleint A and the merge agent
> continued to run successfully again. However I do need the new gateway
> (the
> one that is not working for merge).
>
> thx..
>
|||I am running a PUSH subscription.
Additionally, after troubleshoot, I found the following:
I had a Gateway, primary, secondary DNS IP's setup before I installed SQL
and configured Replication.
After SQL replication configured and working, had to change Gateway and DNS,
then merge agent would not run. I changed Gateway and DNS back to original
and merge worked; I then removed original Gateway IP (only) and merge worked,
which indicates the DNS change was the problem.
I do not have any alias's setup.
How can I maintain IP changes w/o affecting merge agent?
thx..
"Hilary Cotter" wrote:

> Is this push or pull?
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> 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
>
> "bt7403" <bt7403@.discussions.microsoft.com> wrote in message
> news:230FE02E-2D00-44EF-9D1D-A6C3A42C6175@.microsoft.com...
>
>