FIX: The application enters into an infinite loop when you run an application that uses Microsoft Synchronization Services for ADO.NET to synchronize a SQL Server Compact 3.5 database

Consider the following scenario:

• You create an application that uses Microsoft Synchronization Services for ADO.NET to synchronize a server database of SQL Server and a client database of Microsoft SQL Server Compact 3.5.
• In the application, you use the SqlCeClientSyncProvider client synchronization provider for SQL Server Compact 3.5.
• In the application, you resolve a client-side conflict by specifying the ApplyAction.RetryWithForceWrite option.

When the SqlCeClientSyncProvider client synchronization provider tries to resolve a detected conflict, the application may enter into an infinite loop without applying any row on the client database.

Note This problem also occurs in SQL Server Compact 3.5 Service Pack 1 (SP1).

This problem occurs because the SqlCeClientSyncProvider provider incorrectly detects a conflict that does not exist. The false conflict is caused by a bug in the SQL Server Compact engine. The bug causes the return of incorrect results for a query that is used by the SqlCeClientSyncProvider provider to detect conflicts. This query runs every time that the SqlCeClientSyncProvider provider tries to force a row to be applied on the client database. However, because the ApplyAction.RetryWithForceWrite option is enabled, the application enters into an infinite loop.

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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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.

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: