Subscription marked inactive in SQL 2008

[OceanDeep via SQLMonster.com]

We are using SQL 2008 std with push transactional publishation to a SQL 2005
subscriber. The publisher and distributor are on the same server.

Out of nowhere, I received the following message.

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

The subscription setting in the publisher is 'never expire'. The retention
settings in the distributor are as follows:

Transaction retention: At least 0 hours and but not more than 72 hours.
History retention: store replication performance History at least 48 hours.

Since we upgrade to SQL 2005 and SQL 2008, I haven't encountered this error
for over 2 years as the default is set to 'never expire' I think. So what
happened to my subscription? why all of a sudden, this error comes up. What
is the solution for it?


Any help on this is very much appreciated.

od

[Ben Thul]

How do you monitor your replication? Do you know that your subscriber
wasn't more that 72 hours behind the publisher? If it got outside of
that threshold, that would make the subscription expire, regardless of
settings. Other than that, I can't think of another reason why that
would happen.
--
Ben

Post by OceanDeep via SQLMonster.com
We are using SQL 2008 std with push transactional publishation to a SQL 2005
subscriber.  The publisher and distributor are on the same server.
Out of nowhere, I received the following message.
The subscription(s) have been marked inactive and must be reinitialized.
NoSync subscriptions will need to be dropped and recreated.
The subscription setting in the publisher is 'never expire'.   The retention
Transaction retention: At least 0 hours and but not more than 72 hours.
History retention:  store replication performance History at least 48 hours.
Since we upgrade to SQL 2005 and SQL 2008, I haven't encountered this error
for over 2 years as the default is set to 'never expire' I think.  So what
happened to my subscription?  why all of a sudden, this error comes up.  What
is the solution for it?
Any help on this is very much appreciated.
od
--
Message posted viahttp://www.sqlmonster.com

[Nick Fairway]

We are having a similar issue on SQL2005. Two of 8 subscriptions have this error. These subscriptions have been working for months and then suddenly 2 will not work. Even tried dropping all subscriptions and adding them in again - the same 2 always error out immediately before we even initialise with "The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated."

Did anyone find the solution?

Post by OceanDeep via SQLMonster.com
We are using SQL 2008 std with push transactional publishation to a SQL 2005
subscriber. The publisher and distributor are on the same server.
Out of nowhere, I received the following message.
The subscription(s) have been marked inactive and must be reinitialized.
NoSync subscriptions will need to be dropped and recreated.
The subscription setting in the publisher is 'never expire'. The retention
Transaction retention: At least 0 hours and but not more than 72 hours.
History retention: store replication performance History at least 48 hours.
Since we upgrade to SQL 2005 and SQL 2008, I have not encountered this error
for over 2 years as the default is set to 'never expire' I think. So what
happened to my subscription? why all of a sudden, this error comes up. What
is the solution for it?
Any help on this is very much appreciated.
od
--
Message posted via http://www.sqlmonster.com

Post by Ben Thul
How do you monitor your replication? Do you know that your subscriber
was not more that 72 hours behind the publisher? If it got outside of
that threshold, that would make the subscription expire, regardless of
settings. Other than that, I cannot think of another reason why that
would happen.
--
Ben
005
ntion
ours.
or
hat
=A0What