Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Merge Replication - could not enumerate changes at the 'Publisher'

373 views
Skip to first unread message

Karthik

unread,
Jul 5, 2006, 5:32:02 AM7/5/06
to
Hi,

I have setup merge replication on SQL 2k with sp4. There are 2 pull
subscriptions (one in LAN and the other over the internet). The one on the
internet is giving the below error everytime we try to sync.

The process could not enumerate changes at the 'Publisher'.
The process could not enumerate changes at the 'Publisher'.
The merge process could not retrieve column information for table
'dbo.ProjectDetails'.
The merge process encountered an unexpected network error. The connection to
Publisher 'ECOSYSTEM' is no longer available.
Percent Complete: 0
The process could not enumerate changes at the 'Publisher'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147200999
Message: The process could not enumerate changes at the 'Publisher'.
Percent Complete: 0
Category:SQLSERVER
Source: ECOSYSTEM
Number: 11
Message: General network error. Check your network documentation.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201016
Message: The process was successfully stopped.
Percent Complete: 0
Category:NULL
Source: Merge Process
Number: -2147199469
Message: The merge process encountered an unexpected network error. The
connection to Publisher 'ECOSYSTEM' is no longer available.
Disconnecting from Publisher 'ECOSYSTEM'

Can someone please help me with this?

Thank you.

Regards,
Karthik

Paul Ibison

unread,
Jul 5, 2006, 6:35:38 AM7/5/06
to
Karthik,
what happens if you just restart the merge agent? The problem here seems to
be that there was a disruption to the network connection, and I would expect
resyncing to sort out the problem.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)


Karthik

unread,
Jul 5, 2006, 7:29:02 AM7/5/06
to
Hi Paul,

Thank you for the response!

I have tried re-starting the merge agent but the same error persists. I have
infact tried to restart all the subscribers and the publisher also. But even
this didn't help.

I have done a ping PUBLISHER -t from the culprit subscriber. Even the ping
responses seem to be fine with hardly any time-outs.

This always fails at one table for which around 1000 records are to be
delivered from the publisher to the subscriber. I have tried increasing query
timeout etc in the agent profile. But even this hasn't helped much.

Thank you.

Regards,
Karthik

Hilary Cotter

unread,
Jul 5, 2006, 8:26:17 AM7/5/06
to
Set QueryTimeout to a larger value and restart your agent. It almost sounds
like you have an unreliable link between your publisher and subscriber.

--
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

"Karthik" <Kar...@discussions.microsoft.com> wrote in message
news:FEE26229-B4FF-458E...@microsoft.com...

Kartik

unread,
Jul 5, 2006, 9:55:02 AM7/5/06
to
That i have already done but still it's giving same error.

Karthik

unread,
Jul 6, 2006, 6:23:01 AM7/6/06
to
Hi Hilary,

I have tried increasing the QueryTimeout to 1200 seconds. But still the
problem persists.

Also the system I am talking about was working fine till last Friday. This
problem has started all of a sudden. We have checked with our server hosting
company as to whether they have been having any issues with connectivity.
They have replied in the negative.

Regards,
Karthik

Hilary Cotter

unread,
Jul 6, 2006, 9:16:00 AM7/6/06
to
could you post the schema for ProjectDetails?

--
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

"Karthik" <Kar...@discussions.microsoft.com> wrote in message

news:8FAB4536-8349-46FA...@microsoft.com...

dzman49

unread,
Jul 6, 2006, 12:45:25 PM7/6/06
to
For what it's worth, I had a "could not enumerate changes..." error
that was due to an inability of the merge agent to access the snapshot
folder. A possibly significant difference between your LAN
subscription (that works) and your anonymous subscription (that doesn't
work) is the rights of the respective users under which the merge
agents are launched.

BTW, are you Karthik from OKC?

Karthik

unread,
Jul 10, 2006, 7:29:01 AM7/10/06
to
Hi,

I republished the entire data after dropping the publication/subscriptions.
After this also I got errors for tables that were huge in size (basically
with image columns).

I deleted data from these tables the replication started working
automatically.

I am NOT Karthik from OKC.

Regards,
Karthik

0 new messages