sql server replication: HI, I have configured merge replication with pull subscription on sql server2000 and subscribers running personall sql server 2000. Subscribers connect through VPN. The application written in VB6 was working properly since 4 months with minor replication problems.

A few days ago we rebuilt the publication. All subscribers got their initial snapshots succesfully while connected with UTP cables. From that time on everytime they try to synchronize through VPN they upload their changes but they can't download changes from the Publisher. They receive the message

Failed to enumerate changes in the filtered articles
Coll. Code: x80045063=x80040000 + 2057
{call sp_MSsetupbelongs(?,?,?,?,?,1,?,?,1,?,?,?,?)
Coll. Code:
Incorrect syntax near the keyword 'where'
Coll.Code: x9C=15
Incorrect syntax near the keyword 'and'
Coll.Code: x9C=15

We checked our join filters and everything seems OK

Next a subscriber synchronized with UTP cable (instead of VPN) and it worked! But still everyone trying to synchronize through VPN gets the same error. We increased the timeout of the merge agent but the problem is still there

Do anyone have found real solution for this problem?

Thanks a lot for your help!!

Tony,
there are scant details on this on the MS site:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_err_odbc_72pl.asp.
The main suggestion is to increase the timeout, which you have already done.
There is a recorded error - http://support.microsoft.com/?id=814916 - which
details a fix, and hopefully this is relevant. Also, rerunning the merge
agent often fixes these issues. If none of this helps, then a PSS call might
be required.
HTH,
Paul Ibison

place your merge agent in an infinite loop. Most of the time the failure to
enumerate changes are solved the next time the merge agent runs.

Could you possible post your publication and table schema's here?

Could you also do logging to try to isolate which article is problematic?

http://support.microsoft.com/default.aspx?scid=kb;EN-US;312292
[quoted text, click to view]

Dear Paul and Hilary thank you for your advise. We used the Microsoft Hot Fix of the KB Article Number: 814916 and it fixed our problem

Thanks for the update Tony, I'll update my knowledgebase with this.
Paul

Could you mail that hotfix to me ??


please send it to: jk@bestpriceeu.com

Kind regards
Janus
[quoted text, click to view]