Replication-Replication Distribution Subsystem: agent (null) failed.

Discussion in 'microsoft.public.sqlserver.replication' started by Krisnamourt via SQLMonster.com, Nov 22, 2007.

  1. After migrate SQL 2000 replication to SQL 2005, by script and have maked some
    changes, like drop some publications and have added many articles in one,
    this message has appered so often:

    Replication-Replication Distribution Subsystem: agent (null) failed. The
    publication '<name of publication>'does not exist.

    The application log of distributor machine is always with this message like
    this.

    What is the real problem, because some articles don't exist any more and
    there aren't any errors or mistakes of any agents, I mean , the replication
    are ok.

    Unfortely, I didn't see any articles or foruns about the solution and these
    problems impact with Replication alerts.

    I have one machine with three sql instances of distribution functions. All of
    them are administering many publications with many articles.

    Sds!

    Krisnamourt
     
    Krisnamourt via SQLMonster.com, Nov 22, 2007
    #1
    1. Advertisements

  2. Hilary Cotter, Nov 26, 2007
    #2
    1. Advertisements

  3. Thanks Hilary,

    I just dropped these agents and the pull jobs at subscriber and distributor,
    but these message still appear at Distributor.

    I thought these message would be some register from oldest row of
    distribution table, but I couldn't identify any of them.

    At moment, it's so difficult to "redo" all publication , because all of them
    are at production replication, without any "windows time" to do quickly and
    we just have done three weeks ago.

    Any suggest to help me to find out where were all of these row register at
    distribution system tables?

    Sds!

    Krisnamourt

     
    Krisnamourt via SQLMonster.com, Nov 26, 2007
    #3
  4. I'd look to see if I can figure out when these agents are running or
    logging. For example suppose you find they log these messages every 10
    minutes. Then I would run profiler when you next expect it to run and see if
    you can track down the culprit.

    --
    http://www.zetainteractive.com - Shift Happens!

    Looking for a SQL Server replication book?
    http://www.nwsu.com/0974973602.html

    Looking for a FAQ on Indexing Services/SQL FTS
    http://www.indexserverfaq.com
     
    Hilary Cotter, Nov 26, 2007
    #4
  5. Hilary,
    I just followed your advice and see that application "Replication
    Distribution History" send these message.

    How can I delete history informatiom without damage any replication?

    See the sequence:
    if @publication is not null and
    exists (select * from dbo.MSpublications
    where publication = @publication and
    publisher_id = @publisher_id and
    publisher_db = @publisher_db and
    independent_agent = 0)
    -----------------------
    The subscription to publication 'Pub_T400RECL' has expired or does not exist.
    ----------------------
    RAISERROR (21056, 16, -1, @publication)
    ---------------------
    return (1)
    -------------------

     
    Krisnamourt via SQLMonster.com, Nov 26, 2007
    #5
  6. look for an entry in the distribution database where the syspublications
    table has entries for this publication.

    Note the publisher and the publication database. Then go to it and drop the
    publication

    --
    http://www.zetainteractive.com - Shift Happens!

    Looking for a SQL Server replication book?
    http://www.nwsu.com/0974973602.html

    Looking for a FAQ on Indexing Services/SQL FTS
    http://www.indexserverfaq.com
     
    Hilary Cotter, Nov 26, 2007
    #6
  7. I am sorry look for the entries in mspublications, then drop it in that
    database.

    --
    http://www.zetainteractive.com - Shift Happens!

    Looking for a SQL Server replication book?
    http://www.nwsu.com/0974973602.html

    Looking for a FAQ on Indexing Services/SQL FTS
    http://www.indexserverfaq.com
     
    Hilary Cotter, Nov 26, 2007
    #7
  8. Hilary,

    I did what you say to do, but I wasn't finding any register at distributor
    tables that refer to any of these publication that no exists any more.

    are there any kind of multiple register on Monitor replication? I mean, now I
    have many Publication to see in only one SQL 2005 Monitor. When I add some
    new publication, the Monitor connect to your distribution instance. Speaking
    in numbers, It's about 6 distribution connect together in one Monitor.

    What do you think? I can't imagine any other suggest to these problem!

    Sds!

     
    Krisnamourt via SQLMonster.com, Nov 27, 2007
    #8
  9. Can you check each database on the publisher for these entries?

    --
    http://www.zetainteractive.com - Shift Happens!

    Looking for a SQL Server replication book?
    http://www.nwsu.com/0974973602.html

    Looking for a FAQ on Indexing Services/SQL FTS
    http://www.indexserverfaq.com
     
    Hilary Cotter, Nov 27, 2007
    #9
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.