Post reply

The process could not execute sp_repldone/sp_replcounters

  • November 24, 2021 at 7:21 am

    #3956383

    Hi All,

    From the replication log agent , we get this error message "the process could not execute sp_repldone/sp_replcounters"

    and status of log agent -> between retries .

    We run below command :

    EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0,    @time = 0, @reset = 1

    but it doesn't work

    and sp_replrestart also takes a while so we cancel it ..

    Any feedback is much appreciated for the solution

    thank you

  • November 25, 2021 at 8:10 am

    #3956763

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • November 26, 2021 at 8:33 pm

    #3957322

    I would review the logs.  See why it can't execute that stored procedure and possibly find a maintenance window where you can run sp_replrestart for a long period of time as I expect it will complete at some point, it just has a lot of work to do and starting then stopping it is causing problems.

    But step 1 would be to review ALL logs to determine why it is failing.  Chances are one (or more) of the logs will point you in the right direction.  when I say all logs, I mean all of the SQL logs on the source and the destination, as well as the windows logs on both the source and destination.

    Generally, when errors come up, reviewing logs is my first step.  And checking all of the logs is important.  It may be that the replication log is only logging the little bit that you shared ("the process could not execute sp_repldone/sp_replcounters"), but it could be that the SQL error log on the destination server is logging a "login failed" type message.  Or Windows may have a log entry about a NIC failure at the same time replication is failing.

    So, I would start by reviewing the logs and looking at what they say at the time that replication is failing and see if you can find any commonality in them.  There will be a lot of fluff for sure, but finding that one log that points you to the solution is rewarding!

    The above is all just my opinion on what you should do. 
    As with all advice you find on a random internet forum - you shouldn't blindly follow it.  Always test on a test server to see if there is negative side effects before making changes to live!
    I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

  • December 22, 2021 at 9:30 am

    This was removed by the editor as SPAM

Viewing 4 posts - 1 through 3 (of 3 total)

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