Showing posts with label deactivated. Show all posts
Showing posts with label deactivated. Show all posts

Thursday, March 8, 2012

Deactivated?

Merge replication.
Push New Subscription.
Immediately after I click "finish" in the wizard (push new subscription),
the subscription status shows deactivated. The merge agent runs and
completes then shows status has failed. error = "the subscription to the
publication pub_name is invalid. The remote-server is not defined as a
subscription server. 14010"
Your problem is that the remote server is not enabled as a subscriber. I'm
not trying to be flippant, but this might take a little back and forth to
fix.
First off - all publications/subscriptions are marked as deactivated until
the snapshot agent runs. So this status is not problematic in your case.
To enable your subscription server as a subscriber, go to tools,
Replication, Configure Distributor, Publishers, and Subscribers, click on
the subscriber tab, locate your subscriber or register it.
You might also want to review this pdf -
http://www.nwsu.com/lowres_replication_ch02.pdf
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:%23cKdOIoAFHA.904@.TK2MSFTNGP12.phx.gbl...
> Merge replication.
> Push New Subscription.
> Immediately after I click "finish" in the wizard (push new subscription),
> the subscription status shows deactivated. The merge agent runs and
> completes then shows status has failed. error = "the subscription to the
> publication pub_name is invalid. The remote-server is not defined as a
> subscription server. 14010"
>

Deactivate Subscription status

Hi,
I have a transaction replication b/w two servers. In the publisher's subscription list status,it displays deactivated.
The Replication is stopped because of this, i am not able to change the status.
What to do ? Please let me know.
Kumaran,
Subscriptions can be deactivated or can expire if they are not synchronized within a specified period of time. If this shouldn't have happened then you might want to increase the subscription expiration property of the publication and the maximum transact
ion retention property of the distribution database for the future. For now, you'll need to reinitialize.
HTH,
Paul Ibison