Re: The subscription(s) have been marked inactive and must be reinitialized.

Tech-Archive recommends: Fix windows errors by optimizing your registry



basically you are hosed, reset your maximumn distretention to 72 hours and
then you will have to resnapshot. You can do a no sync subscription, do a
validation, figure out what is out of sync and then cobble everything
together.

This is a task I would not wish on my worst enemy, although I will happily
give you Paul Ibison's cell number so you can rope him in on this.

--
Hilary Cotter
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

"ishaan99 via SQLMonster.com" <forum@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:bb02460cc79a4d339c592499a9cfd412@xxxxxxxxxxxxxxxxx
> We have replication set up from our production system to 3 other servers.
> MSrepl_commands table on distribution database was filling up as a result
> someone tried EXEC dbo.sp_MSdistribution_cleanup @min_distretention = 0,
> @max_distretention = 0 which deleted all rows from this table . soon after
> that replication failed completely and the error shows up as
>
> "The subscription(s) have been marked inactive and must be reinitialized.
> NoSync subscriptions will need to be dropped and recreated." followed by
>
> The subscription(s) have been marked inactive and must be reinitialized.
> NoSync subscriptions will need to be dropped and recreated.
> (Source: DISTRIBUTION (Data source); Error number: 21074). Has anyone seen
> thsi error before and if so is there a remedy to this. we had our max
> retention set to 336 hrs but since it was forced to run with 0 did it
> cleanup data from the distribution database that had to be replicated.
> Since its the prodn system any help on this will be greatly appreciated.
>
> TIA
>
> --
> Message posted via http://www.sqlmonster.com


.



Relevant Pages

  • Error 21060 w/Rep. Between Access and SQL Server
    ... can choose options for "Immediate Updating" or "Queued ... establish replication both with and without the option ... >between a SQL Server DB and an Access database. ... >push subscriptions for the following Subscribers: ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge replication / non-convergence
    ... replication (dropped distribution database, dropped subscriptions, dropped ... is related to the replication getting messed up when the metadata clean up ... "Subscriptions never expire" option on; ... publications with 12 subscribers. ...
    (microsoft.public.sqlserver.replication)
  • RE: Disable merge publication
    ... Welcome to Microsoft MSDN Managed Newsgroups Services. ... changes will be replicated to your subscriptions and they will be also ... Controlling Constraints, Identities, and Triggers with NOT FOR REPLICATION ... Microsoft Online Community Support ...
    (microsoft.public.sqlserver.replication)
  • Re: Help in setting up SQL Server 2005 Replication
    ... provides complete DLL replication, but your exposure to data loss is much ... Looking for a SQL Server replication book? ... subscriptions is because it was supposed to reduce cpu/memory usage on the ... latency for every transaction originating on your subscriber. ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication & Patch Installation
    ... I do have pull subscriptions. ... "Hilary Cotter" wrote: ... > Looking for a SQL Server replication book? ... >> servers, ...
    (microsoft.public.sqlserver.replication)