Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: Merge Agent for a filtered publication might fail
Article ID: 814916 - View products that this article applies to.
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
Message: Failed to enumerate changes in the filtered articles.
Source: Failed Command
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)
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 informationTo 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:
(http://support.microsoft.com/kb/290211/ )How to obtain the latest SQL Server 2000 service pack
Hotfix informationThe 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.
Note Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.
Date Time Version Size File name ------------------------------------------------------------------------ 08-Feb-2003 05:43 786,432 bytes Distmdl.ldf 08-Feb-2003 05:43 2,359,296 bytes Distmdl.mdf 30-Jan-2003 01:55 180 bytes Drop_repl_hotfix.sql 01-Feb-2003 00:32 2000.80.763.0 1,557,052 bytes Dtsui.dll 30-Jan-2003 05:18 746,470 bytes Instdist.sql 30-Jan-2003 01:55 1,402 bytes Inst_repl_hotfix.sql 08-Feb-2003 06:40 2000.80.765.0 90,692 bytes Msgprox.dll 08-Feb-2003 03:53 1,065,895 bytes Replmerg.sql 08-Feb-2003 06:40 2000.80.765.0 221,768 bytes Replprov.dll 08-Feb-2003 06:40 2000.80.765.0 307,784 bytes Replrec.dll 30-Jan-2003 05:18 1,084,318 bytes Replsys.sql 08-Feb-2003 06:40 2000.80.765.0 176,696 bytes Sqlmap70.dll 08-Feb-2003 06:40 2000.80.765.0 57,920 bytes Sqlrepss.dll 08-Feb-2003 06:41 2000.80.765.0 7,528,529 bytes Sqlservr.exe 08-Feb-2003 06:40 2000.80.765.0 45,644 bytes Sqlvdi.dll 08-Feb-2003 06:40 2000.80.765.0 82,492 bytes Ssnetlib.dll
Apply this fix to SQL CE subscribersFor SQL Server CE subscribers, you do not have to perform any additional steps if Microsoft Internet Information Services (IIS) and SQL Server are running on the same computer.
If IIS is running on a different computer, follow these steps on the computer that is running IIS to correctly apply this fix:
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:
(http://support.microsoft.com/kb/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.
Article ID: 814916 - Last Review: November 2, 2007 - Revision: 7.3