FIX: Error message when you synchronize a merge replication with SQL Server 2005 Compact Edition subscribers: "A column ID occurred more than once in the specification. HRESULT 0x80040E3E (0)"

Consider the following scenario:

• You create a merge replication with the subscribers of Microsoft SQL Server 2005 Compact Edition.
• You synchronize the subscription.
• You add a new article to the publication, and then you do not synchronize the subscription.
• You run a data definition language (DDL) statement on the publisher against the article that you just added. For example, you run a DDL statement that adds a column to the article.
• You re-create the publication snapshot.

When you synchronize the subscription, you receive the following error message:Note This problem also occurs in Microsoft SQL Server Compact 3.5.

This problem occurs because the subscriber receives the DDL statement after the subscriber receives a snapshot that already contains the DDL statement. When a subscriber receives a DDL statement, the subscriber evaluates the DDL statement. During the evaluation, the subscriber checks whether the DDL statement is redundant. However, the subscribers of SQL Server 2005 Compact Edition do not perform this evaluation. This causes synchronization to fail.

To work around this problem, use one of the following methods:

• Synchronize the subscription after you add the new article to the publication and before you run the DDL statement on the publisher.
• After you run the DDL statement on the publisher, delete the publication, and then re-create the publication.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

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 item in Control Panel.

For all supported ARMV4-based versions of Windows CE 4.0

For all supported ARMV4i-based versions of Windows CE 5.0

For all supported x86-based versions of SQL Server 2005 Compact Edition

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about the Incremental Servicing Model, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: