Unexpected Data Loss(Mege Replication)

Yes I know this will be hard to track...
I just post it in case somebody else expirence the same problem...
This rows are insert at the subscriber and never apear on the publisher
so i suppose i will not find them in msmerge_contents in the publisher.
(they also desapear from subscriber after a while)
Also i have a strange behavior - lets say that I insert 500 rows in this
table
1,2,3...500. The conection speed is slow so some times i see that the row 3
is comming to
publisher before the row 2 ...

? "Hilary Cotter" <hilary.cotter.TakeThisOut@gmail.com> ?????? ??? ??????
news:f462bab1-9ce5-49b7-83cb-2dd4e6aefb13@m34g2000hsb.googlegroups.com...
This will be hard to diagnose and trouble shoot. I take it you are not
doing any filtering.

If so make sure the missing rows aren't being filtered out. If not you
will have to run profiler and filter on the replication agent name.

Then see if the rows make it to the subscriber. If not, check
msmerge_contents to see if they were marked for replication on the
publisher.
On Jan 24, 8:58 am, "Grigoris Tsolakidis"
<gcholakidis.TakeThisOut@spam_remove.hotmail.com> wrote:
> I have a replication with SQL Server 2000 with Service Pack 4
> Recently i make a freqently update to a table (lets say to update 50000
> Row)
> 2,3 times a day.
> After that i notice strange data loss in this table - for example I loose
> 1
> row from 1000 Inserted.
> And this rows are not in the conflict table...
 >> Stay informed about: Unexpected Data Loss(Mege Replication)