| Event Id | 20038 |
| Source | MSSQLServer |
| Description | The article filter could not be added to the article %s in the publication %s. |
| Event Information | CAUSE: This error occurs when you add or change a merge replication filter. If any other error was reported during the execution of sp_addmergefilter or sp_changemergefilter, error 20038 will follow the more specific error. This error is also reported if sp_addmergefilter or sp_changemergefilter failed to perform one of the following actions: Update sysmergepublications or sysmergearticles. Insert into or update sysmergesubsetfilters. Mark all subscriptions for the specified publication for reinitialization. Create a view for a vertical partition. RESOLUTION: If other errors occur at the same time as this error, troubleshoot them. 1. Check the syntax of the filter clause specified. If you are running on a case-sensitive server, make sure that the filter clause uses the proper case for identifiers. Ensure that the article name specified as the join article exists. 2. If you change the join article name, join filter clause, or join unique key, ensure that @force_invalidate_snapshot = 1. 3. Ensure that the filter name specified does not already exist. 4. Run SQL Profiler against the relevant SQL Server instance to capture "Errors and Warnings" events. Sometimes this will capture errors that are otherwise not seen. Verify the intergrity of the published database. 5. Check to see if any object can be created in the database, and if data can be inserted into any existing object in the database. It is possible that the problem is actually with the database as a whole, rather than specific to replication. |
| Reference Links | Microsoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 20038 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.