merge replication error

  • Hi all

    One of my merge replication, sometimes shows the following error which will automatically solve after some days.

     

    error:

    Failed to enumerate changes in the filtered articles.

    Error details:

     

    Failed to enumerate changes in the filtered articles.

    (Source: Merge Replication Provider (Agent); Error number: -2147200925)

    ---------------------------------------------------------------------------------------------------------------

    Line 1: Incorrect syntax near '-'.

    (Source: ABBLCCIS (Data source); Error number: 170)

    ---------------------------------------------------------------------------------------------------------------

    All help appreciated.

    Thanks

     

     

     

  • Hello,

    What is the result from Select @@Version on the publisher, distributor, and subscribers?

    jeff

     

  • Hello,

    Collect the verbose log and check if you get any information from within in.

    As this is a pretty generic error.

    1. Is it at the time of initial synchronization

    2. Does this error occur every time

    3. You can as well take a SQL profiler and check as to which SP is causing issues

    - Krishna

  • Actually I would check the build number before doing any of those steps.

    Select @@Version

    I think this problem happens with SP3 if the build 818 hotfix isn't applied.

     

     

     

     

     

  • Select @@Version

    Result from publisher database server

    Microsoft SQL Server  2000 - 8.00.760 (Intel X86)   Dec 17 2002 14:22:05  

    Copyright (c) 1988-2003 Microsoft Corporation  Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

    Result from Subscriber

    Microsoft SQL Server  2000 - 8.00.760 (Intel X86)   Dec 17 2002 14:22:05  

    Copyright (c) 1988-2003 Microsoft Corporation  Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

     

  • Helo!

    I have not got any proper solution.

     

  • Hello,

    I'm pretty sure that this is a known bug in SQL2000 with SP3.  It was corrected in build 818, which is available via a hotfix or security update.

    Based on your report of the select @@version back in March, you are running build 760 (unpatched SP3)

    Are you still using SP3 unpatched (760) ?

     

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply