Post reply

The process could not deliver update(s) at the 'publisher'/'subscriber'

  • October 23, 2008 at 12:17 pm

    #96565

    Hello Everyone, I'm having a big headache with this new replication problem

    I have 4 sql servers 2000 SP3 running on windows 2000 sp4

    3 of them are in 3 differents phisical location, they replicate a databases using a combination of merge and transactional publications.

    But, in one of them I've the next error:

    The process could not deliver update(s) at the 'publisher'.

    (Source: Merge Replication Provider (Agent); Error number: -2147200989)

    ---------------------------------------------------------------------------------------------------------------

    Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 17, current count = 18.

    (Source: SVR_SUBSCRIBER1 (Data source); Error number: 266)

    ---------------------------------------------------------------------------------------------------------------

    The process was successfully stopped.

    (Source: Merge Replication Provider (Agent); Error number: -2147200999)

    ---------------------------------------------------------------------------------------------------------------

    Anyone ever experienced something like this before?.

    Thanks in advance for any suggestion

    Ricardo

  • October 30, 2008 at 5:09 pm

    #892120

    Do you replicate SQL statements or do you use stored procedures? I'm guessing the latter and, if so, have they been written by yourself or are you using the horrible things generated by SQL Server?

  • November 1, 2008 at 2:28 pm

    #892761

    I'm just using sp generated by sql. Have any idea?

  • November 3, 2008 at 9:31 am

    #893087

    Does the error message contain reference to a transaction sequence number and command_id? I'd hope that it does as you can use these with sp_browsereplcmds to identify the actual stored procedure call which is failing. I suspect there may be a SQL error which is being masked by the error you are receiving. I had that behaviour before and I seem to remember the actual error was a data conversion error or arithmetic overflow or some such thing. I was using sp's I had written myself rather than SQL Server generated ones so you shouldn't get that sort of thing with them. But if you can identify the stored procedure which is failing you can then run that one in isolation and see what happens.

  • November 4, 2008 at 10:29 am

    #893759

    Thanks, mdowns!

    Actually, sql server itself solved the problem. I don't know what happened before, during or after de problem. Fortunately, everything’s is fine now, but don’t know when can happen again. Can you suggest any book that specialized in replication or programming replication?

    Ricardo

  • November 5, 2008 at 3:15 am

    #894100

    Ricardo,

    Glad everything is working now. As for a book, I can't recommend one personally. I have managed to survive by using Books OnLine and various SQL Forums (oh, and a lot of blood, sweat and tears). Looking on Amazon the book "Pro SQL Server 2005 Replication" might be good. It only has one review, which is very favourable, but at £54.99 I hope you can buy it on expenses!

    Mike

  • November 5, 2008 at 10:44 am

    #894425

    Thanks, Mike!

    I’ll take a look at that book. I appreciate your interest and help.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply