0

We are synchronizing SQL Server CE with SQL Server 2008 R2.

There are two different publications we need to synchronize, and we call them each in sequence.

This is a (greatly abbreviated) sample of what we are doing.

System.Data.SqlServerCe.SqlCeReplication repPub1;
repPub1.Synchronize();

System.Data.SqlServerCe.SqlCeReplication repPub2;
repPub2.Synchronize();

99% of the time, the first publication runs, then the second.

However, 1% of the time, the first publication finishes, according to the replication monitor, but not as far as C# is concerned, so we sit and wait indefinitely on the repPub1.Synchronize(); step, and the second publication never starts. The only thing we can do is have the user terminate and start over when they get tired of waiting.

Has anyone seen this before? Anyone know how to make this more fail safe?

Suggestion?

Thanks

marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
Brad
  • 1,357
  • 5
  • 33
  • 65
  • First questions I usually ask are: What CU level on the server and web server (must be in sync) and what SQL CE build. Desktop or Windows Mobile? – ErikEJ Feb 27 '14 at 08:13
  • SQL 2008 R2 CU7 for the server and SQL CE 3.5 (latest version that supports merge replication) The mobile database is running on Windows Mobile. Thanks – Brad Mar 13 '14 at 14:37
  • Sorry about that. SQL CE is 3.5.5386 – Brad Mar 13 '14 at 19:54
  • Then I suggest you upgrade the replication components on both client and server to the latest version: http://erikej.blogspot.dk/2010/08/sql-server-compact-35-sp2-downloadable.html – ErikEJ Mar 14 '14 at 08:22
  • We upgraded to CE 3.5 SP2 and everything seems to be working properly. Thanks. – Brad May 21 '14 at 01:14

1 Answers1

0

Upgraded to CE 3.5 SP2 on both the SQL Server and in our mobile application and that seemed to fix the problem.

Brad
  • 1,357
  • 5
  • 33
  • 65