Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I have transactional replication with updatable subscribers set up in SQL Server 2008. It has 3 subscribers and 1 publisher. I had to setup replication again due to some errors related to the database and the application which uses the database. However, now I run into issues when I try updating a section in my application. It does not go through the with update and gives the following error:

Execption Message: Updateable Subscriptions: Rows do not match between Publisher and Subscriber. Run the Distribution Agent to refresh rows at the Subscriber. Updateable Subscriptions: Rolling back transaction. The transaction ended in the trigger. The batch has been aborted. Exception Triggered by Method: OnError

The update statement obviously doesn't go through. However, when I try it the second time it works. Replication is working. Everything seems to be replication.

Can anyone explain why this error would occur and how I can resolve this issue. I would really appreciate the help!...

share|improve this question
1  
    
Yes I have they didn't really help. As this situation started occurring recently and this was working fine previously. –  user24250 Jul 15 '13 at 21:24
add comment

1 Answer

Maybe it is because of the replication latency, i.e. when you first run, the pub and sub tables are not sync'ed and during your next run, the tables are sync'ed and the 2nd run succeeded.

share|improve this answer
    
That wasn't happening before.....so why would it start all of a sudden. And if that is the case, should I increase the timeout....? –  user24250 Jul 15 '13 at 21:03
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.