Unable to synchronize the row because the row was updated by a different process outside of replication.

Unable to synchronize the row because the row was updated by a different process outside of replication.

• sigme

  Where in this topology are you getting the errors
  

• bostontech2

  Hi Greg,

  Thanks for your reply, I am trying to solve this problem since couple of weeks but no luck.

  I am having SQL Server 2000 Enterprise Edition 8.00.2039(SP4).

  Topology

  1. Central Head Office SQL Server which act as Publisher and Distribution database is kept on same machine.

  2. There are 4 SQL Servers which are subscribers and connected to Head Office.

  3. There are 10 Range Offices SQL Server acts as Publishers and Distribution databases kept on respective machines. Range SQL Server are subscribers for Head Office also.

  4. There are 32 Circle Offices SQL Servers acts as Subscribers, they are only connected to Range Office. And Range Office is connected to HO.

  Thanks

  
  
  

• LYx

  Hi Coniah, in what order was your topology set up

  Was P1 set up first, with S1 and P2 as subscribers, then P2 configured to be a republisher with S2 as a subscriber to P2

  
  

• TGF

  Ok, for a republisher scenario to work, you have to create it as a top-down approach. Meaning:

  P1

  / \

  S1 P2

  \

  S2

  So you create publisher P1, with subscribers S1 and P2 with P2 having global/server property set (this enables P2 to be a republisher).

  Then create your publication on P2 with subscriber S2.

  If you create it out of order, you run the risk of nonconvergence, or errors such as the one you're seeing, caused by having two totally different publications with different article nicknames in the triggers/procs. One set ends up overwriting the other.

  
  

• I. Silvestri

  I am also getting the same error. I am also running SQL 2000. I suspect it is the topography I am using. I have a total of 4 SQL servers involved, two at each location. At location 1, one server is the publisher (P1) while the other is the subscriber (S1). At location 2, it is the same setup (P2, S2). To link the two sites, the publisher at location 2 (P2) is also a subscriber to the publisher at location 1 (P1). For our tests, only Publisher P1 modifies the data, although this may change in the real world. If there is no synchronization between P1 and P2, all updates occur without any problems. If there is no synchronization between P2 and S2, all updates occur without any conflicts. If there is synchronization between P2 and S2, and P1 and P2, then I get the 'Unable to synchronize the row because the row was updated by a different process outside of replication.' error. I believe this is because there are two publishers.
  
  Any assistance would be greatly appreciated. Thank you.
  
  

• 10010101

  Hi

  I am getting this error at Head Office (HO) SQL Server and number of conflicts are in high number. There is no error reported at Rang or Circle level SQL Servers.

  Thanks

  
  
  

• Buzzy teh Cicada

  Hi Milind, what version of SQL Server do you have at the publisher/distributor Also, can you describer your topology Is this a central subscriber scenario
  

• uncle_peter

  I thought I had tried it before, but I think the mistake I made was in setting the priority to zero. Apparently that's not a good thing. Thank you very much.
  
  

• Mathava Gnanananthan

  It looks like the metadata is messed up somewhere, If reinitialization is not an option, I suggest calling support to have an engineer figure out the problem.
  

• DIW

  Yes, P2 subscribed to P1, then the subscription was deleted. Then S2 subscribed to P2 and P2 subscribed to P1. I used the first P2 to P1 subscription to push the database and schemas across the networks. I had to delete the subscription since a subscriber can't become a publisher but a publisher can become a subscriber. I then added the location to subscription and re-established the location 1, 2 subscription.
  

• Alfo

  Milind,

  Since you say you are seeing this error on the Head Office, is there a chance that a row which was updated by a subscriber, is being synchronized by the merge agent and at the same time, there are updates to this particular row at the Head Office by someone else

  And if this is true, are all such rows (which are reported) having the same issue, that is, being merged but being updated by some (user) at the same time

  
  
  
• Unable to synchronize the row because the row was updated by a different process outside of replication.