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

Replication Error: 14151, severity: 18, State 1. Expand / Collapse
Author
Message
Posted Wednesday, December 19, 2012 4:45 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, December 15, 2014 11:29 AM
Points: 55, Visits: 297
Hi,

I have like a orphaned publisher trying to push out a transactional request or something. I can't figure this out i get the below error message, but the actual publisher to subscription (push and subscriber is on another server from the publisher) is working just fine. But, in the SQL error log (on the publisher server) I am still getting the below message? Anybody encounter this or know how to find out where this is coming from and how to get rid of this message? Another note is we did swap servers for the subscriber, but like i said it replication is working just fine.

"Replication-Replication Distribution Subsystem: agent(null)failed. The subscription to publication has expired or does not exist."
Error: 14151, severity: 18, State 1.


Any help is much appreciated! Thanks.
Post #1398708
Posted Wednesday, December 19, 2012 11:11 PM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Tuesday, December 2, 2014 6:21 AM
Points: 169, Visits: 286
Must be some old subscriptions as which are generating this , follow discussion in link below it would guide you.

http://social.msdn.microsoft.com/Forums/en/sqlreplication/thread/fc6db830-b88d-4248-b887-21fd18d7aea1


Cheer Satish
Post #1398786
Posted Thursday, December 20, 2012 11:17 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, December 15, 2014 11:29 AM
Points: 55, Visits: 297
Satish thanks a million it looks like exactly the problem we are having! We are going to first try and re-initialize it, because the stopping of the sql service is not a luxury we have since were in a 24x7 environment. So, if the re-initialize doesn't work we will have to schedule some time out to go down your route. Really appreciate the reference though i think your route will work if re-initialize doesn't. Appreciate it.
Post #1399078
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse