SQL Server Performance

Subscriptions marked as inactive

Discussion in 'SQL Server 2008 Replication' started by kdefilip, Jan 18, 2010.

  1. kdefilip Member

    I have two sql2005 servers, both at same sp level. At first glance, the publisher looks to be up with no issues. When I view the replication monitor, I see the following error:
    The subscription(s) have been marked inactive andmust be reinitialized. NoSync subscriptions will need to be dropped andrecreated.
    When I drill down in the monitor, I see many of the above error. When I click on the "start" button back at the main monitor window, I get the following:
    TITLE: View Synchronization Status
    ------------------------------

    The agent could not be started.

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server+Management+Studio&ProdVer=9.00.4035.00&EvtSrc=Microsoft.SqlServer.Management.UI.ReplUtilitiesErrorSR&EvtID=CantStartAgent&LinkId=20476

    ------------------------------
    ADDITIONAL INFORMATION:

    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

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

    SQLServerAgent Error: Request to run job SCMMA-NTV-FX1-ECLP_Reporting_FX1-SCMMARPT-NTV-1 (from User distributor_admin) refused because the job is already running from a request by Start Sequence 0.
    Changed database context to 'FX1'. (Microsoft SQL Server, Error: 22022)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.4035&EvtSrc=MSSQLServer&EvtID=22022&LinkId=20476

    ------------------------------
    BUTTONS:

    OK
    ------------------------------
    The Subscriber is showing similar errors? The publisher is set to "never expire but they can be deactivated until they are reinitilized".
    When I look at the log reader agent status, it is continually sending commands like "xx transactions with xx commands were delivered"
    Anybody have any idea what is going on here?
    Thanks.
  2. preethi Member

    I remember reading somewhere that it could be because of snapshot agent not runing for sometime. Can you execute snapshot agent and see.
    In our environments, we created without snapshot agent 9The data was synced manually). The only issue is you can't reinitialize it but it was fine for us.
  3. preethi Member

    Got some additional info from this site: http://www.sqlservercentral.com/Forums/Topic154744-7-1.aspx. Not sure whether it is the reason. (The last post there says it happens only if there is no transaction happened for 48 hours. But In your post you have mentioned that transactions get replicated.) However, its worth the reading.
  4. satya Moderator

    Check the history frm msdistribution_agents & msdistribution_history

Share This Page