Microsoft KB Archive/914792

= Merge replication results are incorrect or merge replication fails when you try to use merge replication to merge SQL Server 2005 Compact Edition data with SQL Server 2000 data =

Article ID: 914792

Article Last Modified on 12/7/2006

-

APPLIES TO


 * Microsoft SQL Server 2005 Compact Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Standard Edition

-



BUG #: 11321 (SSCE)



SYMPTOMS
When you try to use merge replication to merge Microsoft SQL Server 2005 Compact Edition data with Microsoft SQL Server 2000 data, you may experience one of the following problems:  The operation appears to be successful. However, the results are incorrect when you examine the subscriber table. You experience this problem when the data type of all the columns before the Identity column is the int data type or a data type that is compatible with the int data type. The merge replication fails, and you receive the following error message:

The message received from the server cannot be decoded. Retry the operation. HRESULT 0x80004005 (29511)



This problem occurs when all the following conditions are true:
 * The table has an Identity column.
 * The Identity column is not the first column of the table.
 * Merge replication involves both uploading changes and downloading changes for the table.
 * The table is not empty after the synchronization process.

Note You do not experience this problem when the server that runs the publisher is running SQL Server 2005.



CAUSE
This problem occurs because SQL Server 2005 Compact Edition does not maintain the column order when data is uploaded and downloaded. The upload column order differs from the download order. In SQL Server 2000, you cannot change the column order two times in a single merge replication transaction.



RESOLUTION
To resolve this problem, use one of the following methods:
 * Try to resynchronize the data by uploading changes from the subscriber again.
 * Create the tables with the Identity column as the first column.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Keywords: kbsql2005repl kbtshoot kbprb KB914792

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.