Results 1 to 5 of 5
  1. #1
    Join Date
    May 2003
    Posts
    23

    Unanswered: Log Reader Agent won't start

    We restored a database with replicated tables. Now, the Log Reader Agent will not run. This displays:
    "The process could not execute 'sp_repldone/sp_replcounters' on 'ourservername'."
    In Error Details for the agent:
    "The process could not set the last distributed transaction."
    And, from the logs:
    "ForwardLogBlockReadAheadAsync: Operating system error 998(Invalid access to memory location.) encountered."

    Does anyone know how we get the Distribution database and the Log Reader running again?
    It is only affecting Transactional replication (not snapshot or merge).

  2. #2
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    The only way that I know is to reinitialize the subscriptions. This essentially pushes a new copy of the articles in the stalled publications to the subscribers, which is time consuming but it gets things back to a "known good state" so that replication can continue.

    -PatP

  3. #3
    Join Date
    May 2003
    Posts
    23
    We tried reinitializing. It didn't work.
    We are going to drop all of the Transactional publication subscriptions and see if we can clear it up that way. Otherwise, we may have to script, disable, and re-configure replication.

  4. #4
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Try checking the distribution agent history. See if there is something in there that tells you what the problem is.

    -PatP

  5. #5
    Join Date
    Jul 2003
    Location
    Minnesota Horse Country
    Posts
    4
    This is a stretch, but look for an orphaned log reader process on the publisher and kill it.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •