Asked by:
SyncAgent crashing after upgrade to VS2010

Question
-
We have a working implementation of an application built on .NET 3.5, Sync Framework 2.0 with SQL Server 2008, and Sql Compact Server 3.5 SP1. Everything was working fine until we upgraded to Visual Studio 2010. When trying to sync against an existing SQLCE database, the following exception is thrown:
System.NullReferenceException object reference not set to an instance of an object
at System.Data.SqlServerCe.SqlCeChangeTracking.UpgradePublicTracking(String connectionString)
at Microsoft.Synchronization.Data.SqlServerCe.SqlCeClientSyncProvider.PerformUpgradeIfNecessar()
at Microsoft.Synchronization.Data.SqlServerCe.SqlCeClientSyncProvider.BeginTransaction
(SyncSession syncSession)
at Microsoft.Synchronization.SyncAgent.DataSynchronize()
at Microsoft.Synchronization.SyncAgent.Synchronize()
at Medshare.Synchronization.Emotion.Client.EmotionSyncAgent.Sync()We have tried upgrading to Sync Fx 2.1, and SQL Compact 3.5SP2 and 4.0. Nothing resolves the issue. I have also seen a few other posts with the exact same issue, and no resolution.
Any ideas?
Tuesday, May 29, 2012 7:00 PM
All replies
-
have you checked if your project references are pointing to right sync fx assembly versions?Wednesday, May 30, 2012 12:02 AM
-
Yes. I have done ALL of the obvious.
DRM
Wednesday, May 30, 2012 12:12 AM -
Although, I might ask, what is the 'right' Sync Fx version? Or does it matter?
DRM
Wednesday, May 30, 2012 12:13 AM -
Wednesday, May 30, 2012 1:42 AM
-
I uninstalled all versions, installed SQL CE 3.5 SP2, and Sync Framework 1.0, and still no luck. The only solution I have found so far is to regenerate the sql ce database, and then all syncs work fine. However, this is not an option for our users.
Any other ideas?
DRM
Wednesday, May 30, 2012 1:42 PM -
you can try disabling and enabling change tracking yourself. the SQL CE 3.5 SP2 now exposes public APIs for configuring change tracking...Friday, June 1, 2012 1:17 AM
-
Well, that's not fixing the problem. I don't believe we should have to disable change tracking. And we need the change tracking. There has to be a solution to this issue.
DRM
Wednesday, June 6, 2012 6:57 PM