| Event Id | 21286 |
| Source | MSSQLServer |
| Description | Conflict table %s does not exist. |
| Event Information | CAUSE: This error occurs when you try to add or drop a column to a merge article, but the conflict table specified in sysmergearticles for the modified article does not actually exist in the database. A variation of this problem occurs when the conflict table has a special character. RESOLUTION: 1. Execute DBCC CHECKDB on the database with the missing conflict table to verify there are no data consistency issues. 2. 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. |
| Reference Links | Microsoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 21286 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.