Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Replication Failure - subscription marked inactive

Status
Not open for further replies.

Technokrat

Programmer
Jul 20, 2001
92
US
I have a replication setup that has been working successfully for months, but two weeks ago, the following error occurred.

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

I have clicked the option to re-initialize the replication, but this doesn't work. I've even gone as far as deleting the publication and re-adding it from scratch. This still produces the same error message. It seems like there is a log, or status being held someplace from the old publication that is intercepted by the newly created publication.

Thank you in advance for the feedback.

Best Regards,
Steve
 
Hi Techokrat

I publish several time question about replication problems but no body never answer that. I am trying to findout articles through online but none. I am bumping my head since last 3-days but now crying...I can not help you but may be you can help me. I am trying to setup for replication every thing is ok but at the end when jobs run there are some error which shows about F_Keys and P_Keys probles and also some like following

When IDENTITY columns are transferred to the Subscriber, the IDENTITY property will not be transferred. (For example, a column defined as INT IDENTITY at the Publisher will be defined as INT at the Subscriber.)

If you want the IDENTITY property transferred to the subscription table, you must do the following:

» Create the subscription table manually using the IDENTITY property and the NOT FOR REPLICATION option.

» Set the name conflict article property so that SQL Server does not drop an existing destination table when applying the snapshot. This property is found on the Snapshot tab of article properties.

The following published tables contain IDENTITY columns:

[dbo].[jobs]

one error is as

Could not drop object 'publishers' because it is referenced by a FOREIGN KEY constraint.

i have live and big data base i dn't know how can i handle this problem...if you can help me pls, i will be appreciated for that

Thanks
Naveed
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top