Microsoft KB Archive/889521

= FIX: Synchronization of a merge publication that uses the &quot;Subscriber Always Wins Conflict Resolver&quot; conflict resolver is unsuccessful in SQL Server 2000 Windows CE Edition 2.0 =

Article ID: 889521

Article Last Modified on 2/14/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Windows CE Edition 2.0

-



Bug #: 10738 (SQL Server CE)



Article contents
 Summary Symptoms Resolution 

Hotfix information

 

Prerequisites

 

Restart information

 

Hotfix file information

</li> Workaround</li> Status</li> More Information</li></ul>

<div class="summary_section">

SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package
 * The prerequisites for installing the hotfix package
 * Whether you must restart your computer after you install the hotfix package
 * Whether the hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes
 * The files that are contained in the hotfix package

back to the top

<div class="symptoms_section">

SYMPTOMS
In Microsoft SQL Server 2000 Windows CE Edition 2.0, when you use the Synchronize method against merge publication that uses the Microsoft SQL Server Subscriber Always Wins Conflict Resolver conflict resolver, the synchronization is unsuccessful. When this problem occurs, you receive error messages that are similar to the following:

DESCRIPTION = 'Run'

NUMBER = 80004005

NATIVE_ERROR = 28557, SSCE_M_UNUSABLEDATABASE

SOURCE = 'Microsoft SQL Server 2000 Windows CE Edition'

ParamCount = 6

Param #0 = 0,

Param #1 = 0,

Param #2 = 0,

Param #3 = 'Provider=Microsoft.SQLSERVER.OLEDB.CE.2.0;Data Source= '

Param #4 = ''

Param #5 = ''

DESCRIPTION = 'The row update or insert cannot be reapplied due to an integrity violation. [,,,,,]'

NUMBER = 80040E2F

NATIVE_ERROR = 28549, SSCE_M_FAILEDRETRIES

SOURCE = 'Microsoft SQL Server 2000 Windows CE Edition'

ParamCount = 6

Param #0 = 0,

Param #1 = 0,

Param #2 = 0,

Param #3 = ''

Param #4 = ''

Param #5 = ''

Note This error may be common when there are problems with the join filter logic that is used in the SQL Server publication definition. In order to experience this problem, you must use the Microsoft SQL Server Subscriber Always Wins Conflict Resolver conflict resolver for at least one article in the publication.

back to the top

<div class="resolution_section">

Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

back to the top

Prerequisites
No prerequisites are required.

back to the top

Restart information
You do not have to restart your computer after you apply this hotfix.

back to the top

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

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

SA1100
<pre class="fixed_text">  Date         Time   Version     Size     File name     Platform 01-Feb-2005 00:04  2.0.7331.0  264,774  Ssceca20.dll  ARM

ARMV4
<pre class="fixed_text">  Date         Time   Version     Size     File name     Platform 01-Feb-2005 00:25  2.0.7331.0  264,192  Ssceca20.dll  ARM Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files. back to the top

<div class="workaround_section">

WORKAROUND
To work around this problem, use the default conflict resolver. When the default conflict resolver is selected, the publisher always wins.

back to the top

<div class="status_section">

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

back to the top

<div class="moreinformation_section">

MORE INFORMATION
For more information about how merge replication works, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/aa256294(SQL.80).aspx

For more information about replication with SQL Server CE, visit the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/aa237145(SQL.80).aspx

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:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about the terminology that Microsoft uses when it corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

back to the top

Additional query words: SQLCE fails

Keywords: kbbug kbfix kbqfe KB889521

-

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

© Microsoft Corporation. All rights reserved.