The subscription(s) have been marked inactive.....

  • jmittmann

    Old Hand

    Points: 330

    Hallo,

    from time to time my transactional (push) replications on SQL2000 SP3a servers send me the following error message:

    Error Message : The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated.

    Error Detail : The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions

    will need to be dropped and recreated. (Source: Server Name (Data source); Error number: 21074)

    My subscriptions have been very active for at least 2 years and in the properties "Subscriptions never expire" is marked.

    I know that I can restart replication by setting the status column in distribution..MSsubscriptions to 2 but can anyone tell me why this problem occurs and how I can prevent it in future?

    Thank you for your help

  • magasvs

    SSCertifiable

    Points: 7659

    Some replication parameters require reinitialization of subscriptions. So, if you change something in replication make sure this settings do not require reinitialization.

  • Borik

    Ten Centuries

    Points: 1048

    Umm i just got this error "The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated."

    any Help to get this working again would be appreciated...

    thanks...

  • togi

    SSC Enthusiast

    Points: 117

    Hi All

    I also got same error..I looked to the some forums on net and everybody say that its related with expiration time..its default 72 hours and it can be set longer..

    What is that max value of expiration time?

    Actuallly I want to set my replication as never expired..I mean it should be never expired..How can I set expire time as "unlimited"..

    Thanks ..

  • Borik

    Ten Centuries

    Points: 1048

    Enterprise Manager ->

    Replication Monitor ->

    Publishers ->

    ServerName ->

    Right Click on Publisher ->

    General Tab ->

    at the bottom there is Radio button "Subscription never expires..."

    P.S. Unfortenetly i did't find how to resolve the error, i think u will neet to redo Replication....

    Hope it helps...

    Borik

  • Todd Boothroyd

    SSC Journeyman

    Points: 87

    Hey, not sure all of the steps that I took to resolve my issue, but here's what I recall:

    Under Replication Monitor at the Distributer, expand node.

    Expand Publishers

    Expland node next to server name (Blue-green book icon)

    Right click on any of the publishers and choose Reinitialize all subscriptions. (alternately, you can choose properties and select reinitialize under the Subscriptions tab). This just marks the subscription to be reinitialized.

    Next, on Status tab, I clicked Run Agent Now to trigger the snapshot; this is supposed to, in my setup, push the subscription but that didn't happen.

    Closing the properties window (if open), I selected the publisher in question so the information appeared in the right pane. Selecting the Publish Folder with the red X, I right clicked and chose Start Synchronizing.

    That did it for me; hopefully, I chose the right setting in properties so it doesn't happen again.

    Cheers!

  • ShekharNaidu

    SSCrazy

    Points: 2092

    The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated.

    I am getting this error frequently .. and it requires me to go through all the process of creating subscriptions again and again...

    i would be happy if anybody help in this regard.

    I have "Subscription Expiration perios set to 336 hrs" ... even if it is set to 336 hrs i am getting the above error frequently i.e., bfore this expiration period.

     

    Thank you

    Shekhar

     


    Thanks ,

    Shekhar

  • Andy Warren

    SSC Guru

    Points: 119676

    I dont have a server with replication enabled with me at the moment, but there is a job that checks for expired pubs by looking at the date of the oldest open (undistributed) transaction and marks sub as expired if past x date. Try disabling the job. Though I suspect that may be bandaiding a bigger problem, probably worth digging more.

  • Dinakar Nethi-176633

    SSCarpal Tunnel

    Points: 4689

    If you already have the error, the only solution I would think is to re-setup replication but make sure you check the "never expires" option as Borik mentioned. By default I think its around 336 hours of inactivity. For a production system it is rare to have such period of inactivity.

    ******************
    Dinakar Nethi
    Life is short. Enjoy it.
    ******************

  • Borik

    Ten Centuries

    Points: 1048

    Also u might want to try to increase number of retries for replication jobs...

     

  • ShekharNaidu

    SSCrazy

    Points: 2092

    Thank you for replies...

    I will try those suggestions..

    Shekhar


    Thanks ,

    Shekhar

  • ShekharNaidu

    SSCrazy

    Points: 2092

    Andrew,

    Can you please tell me the job name which is monitoring the subscribers expiration..

    Thank You

    Chandra Shekar


    Thanks ,

    Shekhar

  • Brad Scheepers

    Old Hand

    Points: 356

    Hi guys ...

    When it says the snapshot has been marked as inactive, it's because the snapshot needs to run on it's own schedule in the background (and seems to ignore that it is marked as never expiring).

    So check the schedule of the snapshot agent and let it run something like once a week on a Sunday morning for example. You may still have to reinitialise the publication to get it all sorted out again.

  • Wired-528862

    Mr or Mrs. 500

    Points: 560

    Brad Scheepers (9/18/2008)


    Hi guys ...

    When it says the snapshot has been marked as inactive, it's because the snapshot needs to run on it's own schedule in the background (and seems to ignore that it is marked as never expiring).

    So check the schedule of the snapshot agent and let it run something like once a week on a Sunday morning for example. You may still have to reinitialise the publication to get it all sorted out again.

    Can you expand on this more. I'm new to replication and I'm not sure where to check the Snapshot agent schedule. Thanks.

  • sunrise.freedom

    SSC Journeyman

    Points: 93

    Hi guy,

    just run this query in a new query window in the distribution server 🙂

    USE distribution

    Update [MSsubscriptions]

    Set [status] = 2

Viewing 15 posts - 1 through 15 (of 21 total)

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