Merge Replication Misses Table

I have set up merge replication between two databases and I consistently
fail to get any records updated in one of the tables.
Basically I have a one way push subscription from server A to Server B.
Every table gets replicated except for one which never copies any records. I
can't see anything about this particular table that looks different to any
of the others
Does any one have any ideas?
Regards
Ian
Does anything show up in the conflict viewer for this table?
Hilary Cotter
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
"Ian Cox" <Ian1971@.newsgroup.nospam> wrote in message
news:%236IBthweFHA.1504@.TK2MSFTNGP15.phx.gbl...
> I have set up merge replication between two databases and I consistently
> fail to get any records updated in one of the tables.
> Basically I have a one way push subscription from server A to Server B.
> Every table gets replicated except for one which never copies any records.
I
> can't see anything about this particular table that looks different to any
> of the others
> Does any one have any ideas?
> Regards
> Ian
>
|||No. Nothing in the conflict viewer
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:usCxAlweFHA.3184@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> Does anything show up in the conflict viewer for this table?
> --
> Hilary Cotter
> 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
> "Ian Cox" <Ian1971@.newsgroup.nospam> wrote in message
> news:%236IBthweFHA.1504@.TK2MSFTNGP15.phx.gbl...
records.[vbcol=seagreen]
> I
any
>
|||Hello,
You may refer to the following articles to troubleshoot the issue:
315521 INF: How to Troubleshoot SQL Server Merge Replication Problems
http://support.microsoft.com/?id=315521
Review SQL Server error logs to check if there is any related error.
Default folder is C:\Program Files\Microsoft SQL Server\MSSQL\LOG
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I've gone through the article you suggested and checked the logs but nothing
seems to apply to my situation.
There are no conflicts and nothing to indicate a problem in the logs
I have taken the step to completely rebuild the publication and see if that
helps.
It seems to be ok now, but I will keep an eye on the situation to make sure
the data is being replicated ok by validating the data at the subscriber as
indicated in the article you mentioned.
Thanks
Ian
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:P2pVIQ8eFHA.3404@.TK2MSFTNGXA01.phx.gbl...
> Hello,
> You may refer to the following articles to troubleshoot the issue:
> 315521 INF: How to Troubleshoot SQL Server Merge Replication Problems
> http://support.microsoft.com/?id=315521
> Review SQL Server error logs to check if there is any related error.
> Default folder is C:\Program Files\Microsoft SQL Server\MSSQL\LOG
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
|||I still have the same problem. I have rechecked the knowledge base article
and gone through all the steps.
I enabled validation and logging. As expected it now fails the validation
check. The log doesn't reveal anything.
I am stumped on this one.
Any ideas?
"Ian Cox" <Ian1971@.newsgroup.nospam> wrote in message
news:OGdnSq%23eFHA.1448@.TK2MSFTNGP09.phx.gbl...
> I've gone through the article you suggested and checked the logs but
nothing
> seems to apply to my situation.
> There are no conflicts and nothing to indicate a problem in the logs
> I have taken the step to completely rebuild the publication and see if
that
> helps.
> It seems to be ok now, but I will keep an eye on the situation to make
sure
> the data is being replicated ok by validating the data at the subscriber
as
> indicated in the article you mentioned.
> Thanks
> Ian
> "Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
> news:P2pVIQ8eFHA.3404@.TK2MSFTNGXA01.phx.gbl...
> rights.
>
|||Hello,
You may need to perform the following steps to narroe down the issue:
1. Perform the following command before you insert a new record via trigger
on the publication database
use <publication dabatbase>
select * from msmerge_contents
2. Insert a new record on the problem table
3. Run above command again to see if a new line appears
If new line appears in msmerge_contents when inserting a new record, please
refer to the following article to enable merge replication
agent, and then send log file to me
312292 HOW TO: Enable Replication Agents for Logging to Output Files in SQL
Server
<http://support.microsoft.com/default...b;EN-US;312292>
If a new line does not appear, please check if the triggers are added
properly by merge replication setup process:
Right-click the problem table->All tasks->Manage triggers and make sure
insert/delete/update triggers are listed properly.
If the above triggers do not exist, please run following command to make
sure the article has the same features as other articles:
select * from sysmergearticles
I look forward to hearing from you.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thanks for the info Sophie.
A record does appear in msmerge_contents.
I have already enabled agent logging as indicated in that article.
The logs don't seem to reveal much though
I basically see something like this (server names and DB names changed)
...
[7/1/2005 2:00:25 AM]SubscriptionServer.MyDB: {call sp_MSgetversion }
Percent Complete: 60
Processing article 'Language'
Percent Complete: 80
Processing article 'Supplier'
Percent Complete: 80
Downloaded 5 data changes (5 inserts, 0 updates, 0 deletes, 0 conflicts).
<Note the 5 inserts were all related to the Supplier table - the Language
table should be showing 98 inserts on top of that>
Percent Complete: 80
Validating article 'Territory'
Connecting to Subscriber 'SubscriptionServer.MyDB'
...
Percent Complete: 0
Article 'Language' failed data validation (rowcount only).Article 'Language'
failed data validation (rowcount only).
...
It seems like it doesn't spot any differences between the Language table at
the publisher and subsriber when replicating. When there clearly are changes
Any other ideas?
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:OcLUDShfFHA.3480@.TK2MSFTNGXA01.phx.gbl...
> Hello,
> You may need to perform the following steps to narroe down the issue:
> 1. Perform the following command before you insert a new record via
trigger
> on the publication database
> use <publication dabatbase>
> select * from msmerge_contents
> 2. Insert a new record on the problem table
> 3. Run above command again to see if a new line appears
> If new line appears in msmerge_contents when inserting a new record,
please
> refer to the following article to enable merge replication
> agent, and then send log file to me
> 312292 HOW TO: Enable Replication Agents for Logging to Output Files in
SQL
> Server
> <http://support.microsoft.com/default...b;EN-US;312292>
> If a new line does not appear, please check if the triggers are added
> properly by merge replication setup process:
> Right-click the problem table->All tasks->Manage triggers and make sure
> insert/delete/update triggers are listed properly.
> If the above triggers do not exist, please run following command to make
> sure the article has the same features as other articles:
> select * from sysmergearticles
> I look forward to hearing from you.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||Hello,
I find the following articles address similar issue:
309400 FIX: Merge Replication Non-Convergence Fixes in SQL Server 2000 SP2
http://support.microsoft.com/?id=309400
304222 FIX: Merge Replication Non-Convergence Occurs with Local Subscribers
http://support.microsoft.com/?id=304222
Please install the latest hotfix to resolve the issue:
Microsoft SQL Server 2000 Service Pack 4
http://www.microsoft.com/downloads/d...C8D-C20E-4446-
99A9-B7F0213F8BC5&displaylang=en#filelist
Or you can perform the workaround to narrow down the issue.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Sophie,
Thanks for those articles. They do sounds like the symptoms I am
experiencing, but the cases described are not quite the same. We are already
on SP3 so 390400 doesn't seem to apply and the table in question has less
than 32 columns so 304222 doesn't seem to apply.
I am going to find out if we can install SP4 to see if that makes any
difference
Regards
Ian
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:w4I7MOGgFHA.1184@.TK2MSFTNGXA01.phx.gbl...
> Hello,
> I find the following articles address similar issue:
> 309400 FIX: Merge Replication Non-Convergence Fixes in SQL Server 2000 SP2
> http://support.microsoft.com/?id=309400
> 304222 FIX: Merge Replication Non-Convergence Occurs with Local
Subscribers
> http://support.microsoft.com/?id=304222
> Please install the latest hotfix to resolve the issue:
> Microsoft SQL Server 2000 Service Pack 4
>
http://www.microsoft.com/downloads/d...C8D-C20E-4446-
> 99A9-B7F0213F8BC5&displaylang=en#filelist
> Or you can perform the workaround to narrow down the issue.
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
>