Thank you for your time today to discuss this further Sharath.
The errors we were seeing in the logs on the main SDM Server, when any record is attempted to be edited was similar to this:
| sqlsrvr.c 2612 Execution failed. MISC_DB_ERROR: Clause ({ ? = call dbo.usp_lock_acquire;1( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? ) }) Input (<string>Animator|<string>411019|<int>15724|<string>domsrvr|<uuid>(NULL)|<string>superuser|<string>ANI|<string>cr:899558|<int>1411998253|<int>63 | 0) |
animator_nxd.c 1839 AHD04199:An unexpected error occurred. Contact your administrator. [Microsoft OLE DB Provider for SQL Server] [ SQL Code=3621 SQL State=01000] The statement has been terminated.; [Microsoft OLE DB Provider for SQL Server] [ SQL Code=548 SQL State=42000] The insert failed. It conflicted with an identity range check constraint in database 'mdb', replicated table 'dbo.usp_record_lock', column 'id'. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent. in animator ANI:411019 (cr:899558) for atev:1463347 in method examine_lock_list
Initially we thought it was the procedure itself that was giving grief. But later we saw that the table usp_record_lock was in the replicated list.
Upon identifying this, we determined that TEC617157, which has the updated procedures for SQL Server Merge Replication would help.
Sharath would be testing this and getting back to me, I'll update the thread later on.
_R