| title | MSSQL_ENG021286 | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 06/13/2017 | |
| ms.prod | sql-server-2014 | |
| ms.reviewer | ||
| ms.technology | replication | |
| ms.topic | conceptual | |
| helpviewer_keywords |
|
|
| ms.assetid | b63620b7-1c6d-46f7-90ea-3a8e99af8de4 | |
| author | MashaMSFT | |
| ms.author | mathoma | |
| manager | craigg |
| Product Name | SQL Server |
| Event ID | 21286 |
| Event Source | MSSQLSERVER |
| Component | [!INCLUDEssDEnoversion] |
| Symbolic Name | |
| Message Text | Conflict table '%s' does not exist. |
This error is raised if the conflict table for an article listed in sysmergearticles (Transact-SQL) does not actually exist. The error can occur when you attempt to add a column to or drop a column from a table published for merge replication.
Execute DBCC CHECKDB (Transact-SQL) on the database with the missing conflict table to verify there are no data consistency issues.
If the conflict table is missing on a Subscriber, drop the subscription and recreate it. If the conflict table is missing on a Publisher, drop all subscriptions, drop the publication, and then recreate the publication and all subscriptions. For more information, see Publish Data and Database Objects and Subscribe to Publications.