Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

The subscription(s) have been marked inactive..... Expand / Collapse
Author
Message
Posted Tuesday, January 11, 2005 5:03 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, February 15, 2007 2:32 AM
Points: 38, Visits: 1

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




Post #154744
Posted Tuesday, January 11, 2005 11:43 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, June 19, 2014 6:51 AM
Points: 1,264, Visits: 723
Some replication parameters require reinitialization of subscriptions. So, if you change something in replication make sure this settings do not require reinitialization.
Post #154873
Posted Monday, February 14, 2005 8:51 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, August 30, 2007 9:12 PM
Points: 28, Visits: 1
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...
Post #161473
Posted Tuesday, March 1, 2005 2:44 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, December 14, 2006 2:17 AM
Points: 3, Visits: 1

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 ..

Post #164609
Posted Tuesday, March 1, 2005 7:34 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, August 30, 2007 9:12 PM
Points: 28, Visits: 1
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
Post #164673
Posted Monday, September 26, 2005 2:07 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, September 26, 2005 1:47 PM
Points: 1, Visits: 1

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!

Post #223727
Posted Friday, June 23, 2006 5:44 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, November 8, 2010 10:45 PM
Points: 122, Visits: 70

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

Post #289654
Posted Friday, June 23, 2006 7:33 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Today @ 10:42 AM
Points: 6,779, Visits: 1,854
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.

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #289696
Posted Friday, June 23, 2006 3:08 PM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, December 5, 2013 12:21 PM
Points: 265, Visits: 164
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.
******************
Post #289869
Posted Friday, June 23, 2006 3:24 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, August 30, 2007 9:12 PM
Points: 28, Visits: 1

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

 

Post #289873
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse