Hi,
I have problems with merge replication over modem connection.
It works fine over LAN but with modem connection I got error:
"The merge process encountered an unexpected network error.".
I have tried to modified timeout, query timeout etc. - nothing helps.
Problems started for few days ago. We have been using merge replication for
the last two years without any problems.
Additional information:
Server: SQL Server 2000, SP3, Win 2K SP4, dual processor, 1 GB Memory
150 Clients: MSDE SP3, Win 2K SP4
Anyone has seen this problem before?
Thanks and Best Regards,
Rafael
All the time. Are you using the slow link profile?
If you still get this using the slow link profile you are likely
encountering network problems, or have an unstable line. Try to drop your
packet size.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"raffe" <raffe@.community.nospam> wrote in message
news:D0096C0B-3846-4948-9835-4E293378E14D@.microsoft.com...
> Hi,
> I have problems with merge replication over modem connection.
> It works fine over LAN but with modem connection I got error:
> "The merge process encountered an unexpected network error.".
> I have tried to modified timeout, query timeout etc. - nothing helps.
> Problems started for few days ago. We have been using merge replication
for
> the last two years without any problems.
> Additional information:
> Server: SQL Server 2000, SP3, Win 2K SP4, dual processor, 1 GB Memory
> 150 Clients: MSDE SP3, Win 2K SP4
> Anyone has seen this problem before?
> Thanks and Best Regards,
> Rafael
|||Thanks for your answer.
I have tested with slow link profile, I have creted my own profile with very
small packet size and nothing helps. I now that it worked fine last week and
there is still a lot of clients without any replicatiopn problems.
Raffe
"Hilary Cotter" wrote:
> All the time. Are you using the slow link profile?
> If you still get this using the slow link profile you are likely
> encountering network problems, or have an unstable line. Try to drop your
> packet size.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
>
> "raffe" <raffe@.community.nospam> wrote in message
> news:D0096C0B-3846-4948-9835-4E293378E14D@.microsoft.com...
> for
>
>
|||can you start logging to try to find out exactly why it is timing out like
this?
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"raffe" <raffe@.community.nospam> wrote in message
news:ACCC9978-A042-40B3-8A96-3168A77CF4ED@.microsoft.com...[vbcol=seagreen]
> Thanks for your answer.
> I have tested with slow link profile, I have creted my own profile with
> very
> small packet size and nothing helps. I now that it worked fine last week
> and
> there is still a lot of clients without any replicatiopn problems.
> Raffe
> "Hilary Cotter" wrote:
|||How can I enable logging for merge agents?
"Hilary Cotter" wrote:
> can you start logging to try to find out exactly why it is timing out like
> this?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
> "raffe" <raffe@.community.nospam> wrote in message
> news:ACCC9978-A042-40B3-8A96-3168A77CF4ED@.microsoft.com...
>
>
|||Hi Raffe,
I think Hilary means the Agent Logs described in the following knowledge
base article
HOW TO: Enable Replication Agents for Logging to Output Files in SQL Server
http://support.microsoft.com/kb/312292
However, I would like to set your expectation that replication issues tend
to be very complex and hard to troubleshoot in newsgroups. If you need
instance and insight assistance, I recommend that you open a Support
incident with Microsoft Product Support Services (PSS) so that a dedicated
Support Professional can work with you in a more timely and efficient
manner. If you need any help in this regard, please let me know.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
Showing posts with label modem. Show all posts
Showing posts with label modem. Show all posts
Wednesday, March 28, 2012
Merge replication, modem connection problems
Friday, March 9, 2012
Merge replication fails with odd message
Hi Guys,
I've got a merge replication set up between boxes. They're on separate sites both behind an ADSL Nat modem router. The publisher connects to the subscriber via a port forward / Nat translation at the router. This replication set up has been running for some months now. This morning I got this failure message from the merge agent on the publisher.
"the specified remote server name may not be the network name of the remote server or the remote server is unreachable due to network problems. The step failed"
Currently the Enterprise Mgr at the publisher can see the subscriber as can query analyzer running on the publisher.
The host name of the subscriber is the same name used in the server registration at the publisher. The registration uses a Client Network Utility alias to resolve the name.
If I run a ping command at the publisher using the subscribers name I get replies (the resolution of that name is done via a hosts file entry)
Both machines are Win2k Server boxes running SQL Server 2000 Standard.
Any ideas why the agent can't see the subscriber despite the fact its usual communications channel is working just fine?I've still no idea why I was getting this behaviour but I've reinitialised the subscriptions now and the problem's 'gone'.
I've got a merge replication set up between boxes. They're on separate sites both behind an ADSL Nat modem router. The publisher connects to the subscriber via a port forward / Nat translation at the router. This replication set up has been running for some months now. This morning I got this failure message from the merge agent on the publisher.
"the specified remote server name may not be the network name of the remote server or the remote server is unreachable due to network problems. The step failed"
Currently the Enterprise Mgr at the publisher can see the subscriber as can query analyzer running on the publisher.
The host name of the subscriber is the same name used in the server registration at the publisher. The registration uses a Client Network Utility alias to resolve the name.
If I run a ping command at the publisher using the subscribers name I get replies (the resolution of that name is done via a hosts file entry)
Both machines are Win2k Server boxes running SQL Server 2000 Standard.
Any ideas why the agent can't see the subscriber despite the fact its usual communications channel is working just fine?I've still no idea why I was getting this behaviour but I've reinitialised the subscriptions now and the problem's 'gone'.
Subscribe to:
Posts (Atom)