Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Replication issues

Author  Topic 

sprashant
Starting Member

3 Posts

Posted - 2005-01-27 : 10:52:03
Hi,

we are having some replication issues from past few days.
The updates to a particular table does not get replicated. Inserts work fine.
All these were working fine till 3 days back. We are getting this error only from past three days.
There has been no change in the schema.
The data gets written in the DB but does not get replicated.
The updates for other tables are all working.

Few observations
When I run the sp_distcounters I don't get any rows.
Also the log reader agent displays an error.
We are running sql server 2000 on windows 2000 server on both the machines.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2005-01-27 : 16:11:17
You haven't posted the error, so it's hard to help you out. When the DML statement happens at the subscriber, is it done via stored procedures or UPDATE statements?

Tara
Go to Top of Page

sprashant
Starting Member

3 Posts

Posted - 2005-01-27 : 22:14:57
Hi Tara,
the updates made either at the subscriber or the publishers does not get replicated at all.
Either we use the DML statement to update the column or just do it thru enterprise manager it does nto matter.
As of the error it is as below.
The row was updated at '<<servername>>.<<DBName>>' but could not be updated at '<<servername>>.<<DBName>>'. Unable to synchronize the row because due to an unspecified error.
the server names are the subscriber server name and the publisher server name.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2005-01-28 : 11:32:06
I would drop replication and recreate it.

When I mentioned DML statements, I was referring to the replication configuration and not how you are making the update.

Tara
Go to Top of Page

sprashant
Starting Member

3 Posts

Posted - 2005-01-31 : 15:58:23
Hi Tara,

The isse has been addressed..The error was in a trigger.

Yes I did the replication again in totality since there were some other issues also which all got solved once we did the replication from scratch.
Thanks for the help.
Prashant
Go to Top of Page
   

- Advertisement -