Hi there,

we are using merge replication with anonymous subscribtion.

window 2000, sql 2000 sp3 - server

wind 2000/XP, msde 2000 sp3 - subscriber

Synchronizing data with Active XControl.

we have around 50 subscriber and in our database we are using identity
range management(defult by server) and static filter also. every
things working fine except some time we donot get data from the
subscriber after synchronization. Subscriber does not display any
error message and it say synchronization done successfully but when we
check data its not there in server but still there in subscriber.

when i connect to subscriber and just re-enter same vaule or just
updata one character in a set and synchronize all the data come to
server. since we have 50 + subscriber it pain for us to check around
10-15 subscriber having this type of error. I am suspecting is there
any kind of bug in replication or what causing this problem. if
Microsoft or any one having information regarding this problme please
let me know. I am thinking to open PSS for this in Microsoft but
before i contact them i wanted to know if any one else also having
similar problme or if there is any way to fix this problem.

Thanks you in advance.

Indra,
I have only seen this before (a) when rows are added
using bulk insert with the default options, in which case
FIRE_TRIGGERS is false and consequently the rows are not
added to MSmerge_contents and (b) when the filter was set
to 1=2 and inserts were made while the merge agent was
running.

I'd be interested in these problem cases you're having to
see if the change has been registered in MSmerge_contents
ie has the trigger fired? In (a) the trigger didn't fire
while in (b) the trigger fired but the generation numbers
got messed up.

In each case, you can run sp_addtabletocontents to
include the rows then resynchronise. Alternatively you
can use sp_mergedummyupdate for a single row.

If you don't have a bulk-insert scenario (and it sounds
as though you don't as in your case a single update will
cause the batch to be added), then by all means call PSS.
If you reach a solution, please post back to tell us,
possibly in a new thread if it's in a while.

Rgds,
Paul Ibison

(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)