This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 363726 (SHILOH_BUGS)
The Merge Agent for a filtered publication can fail, and you receive the following error message:
Failed to enumerate changes in the filtered articles. Category: NULL Source: Merge Replication Provider Number: -2147200925 Message: Failed to enumerate changes in the filtered articles. Category: COMMAND Source: Failed Command Number: 0 Message: create table #belong_agent_-2147483646 (tablenick int NOT NULL, rowguid uniqueidentifier NOT NULL,generation int NULL, lineage varbinary(255) NULL, col v varbinary(2048) NULL) Category: SQLSERVER Source: ServerName Number: 170 Message: Line 1: Incorrect syntax near '-'.
In certain scenarios, SQL Server creates the temporary table name with a dash sign in the table name; however, the dash sign in the table name causes the creation of the temporary table to fail.
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Check Merge Replication Sync to make sure that no errors occurred.
Note The fix must be applied on both the publisher and the subscriber. The hotfix is also available in the security hotfix rollup that is described in the following article in the Microsoft Knowledge Base:
821277 MS03-031: Security patch for SQL Server 2000 Service Pack 3
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.