Prev: Push via FTP
Next: The query processor could not produce...
From: Damer on 29 Mar 2010 12:22
I run into the same issue, and even when this is really old I decided to post my solution hoping it helps future readers:
I was able to fix the error by re-running sp_addmergepullsubscription_agent from the Create Subscription Script. Note passwords are null and need to be reset when generating the script from an existing subscription or from the Local Publication.




Ton wrote:

Merge agent problem
16-Oct-07

One of my subscriptions recently stopped replicating. When I went to view
the subcription agent it pops up with this message: "The specified pull
subscription is not configured with a synchronization agent job. (.Net
SqlClient Data Provider)." Previously the sub was working and if I execute
the job it replicates. Short of deleting and recreating the subscription
(which I'm loath to do as the database is over 21 gigs in size and the
subscription creation takes 8-11 hours) does anyone have any suggestions?

Previous Posts In This Thread:

On Tuesday, October 16, 2007 10:37 AM
Ton wrote:

Merge agent problem
One of my subscriptions recently stopped replicating. When I went to view
the subcription agent it pops up with this message: "The specified pull
subscription is not configured with a synchronization agent job. (.Net
SqlClient Data Provider)." Previously the sub was working and if I execute
the job it replicates. Short of deleting and recreating the subscription
(which I'm loath to do as the database is over 21 gigs in size and the
subscription creation takes 8-11 hours) does anyone have any suggestions?

On Thursday, October 18, 2007 7:40 PM
Chri wrote:

It sounds like you really need an alternative to using the snapshot agent to
It sounds like you really need an alternative to using the snapshot agent to
re-init. Look at the 'nosync' option - you can use a backup and restore as
your snapshot.

1) drop subscr
2) add subscr w/ nosync option
3) backup pub
4) restore at subscr from backup
5) fire up merge agent

should be limited to 1 maybe 2 hours...

best of luck

ChrisB MCDBA
www.MSSQLConsulting.com

"Tony" wrote:


Submitted via EggHeadCafe - Software Developer Portal of Choice
Featured Product / Service Review: TekPub
http://www.eggheadcafe.com/tutorials/aspnet/ae6e21fa-3443-4134-9d2e-39384482c80e/featured-product--servic.aspx
 | 
Pages: 1
Prev: Push via FTP
Next: The query processor could not produce...