Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Merge replication results are incorrect or merge replication fails when you try to use merge replication to merge SQL Server 2005 Compact Edition data or SQL Server 2005 Mobile Edition data with SQL Server 2000 data
| Article ID | : | 914792 |
| Last Review | : | March 27, 2008 |
| Revision | : | 3.2 |
BUG #: 11321 (SSCE)
SYMPTOMS
When you try to use merge replication to merge Microsoft SQL Server 2005 Compact Edition data or Microsoft SQL Server 2005 Mobile 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.
Back to the top
CAUSE
This problem occurs because SQL Server 2005 Compact Edition or SQL Server 2005 Mobile 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.
Back to the top
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.
|
Back to the top
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top
APPLIES TO
| • | Microsoft SQL Server 2005 Compact Edition |
| • | Microsoft SQL Server 2005 Mobile Edition |
| • | Microsoft SQL Server 2000 Developer Edition |
| • | Microsoft SQL Server 2000 Enterprise Edition |
| • | Microsoft SQL Server 2000 Standard Edition |
Back to the top
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please
