Membru care solicită informaţii
I just encountered this error yesterday without any changes done on our end:
Sync failed with the exception "We have encountered an issue in syncing your data."
For more information, provide tracing id ‘705b5681-129e-4af7-ab81-95e0de09fa5b’ to customer support.
Apparently, there are inconsistencies on the column definitions for NTEXT types that just cropped up. When we tried to remove the columns/tables that caused the problems, ASPNET_* Tables, we get this error instead:
The sync group is not in a valid state for re-provisioning. The sync group cannot be re-provisioned if members are currently provisioning, re-provisioning, de-provisioning, canceling sync, synchronizing, or have local agents that do not support re-provisioning.
Tracing Id: ec92063a-0fdb-4381-9d82-2d453c5f9e16
Sync Group ID: 43bfa1e2-cef9-47c6-9b48-573a759faba3
Server Location: North Central US
Date Time Error Encountered: around 6/30/2012 9:30AM GMT+8
- Editat de eugene_paden 30 iunie 2012 01:37
afaik, a scheduled sync can overlap if the interval specified is not long enough to allow the synchronization to complete first. the schedule is an interval of time between firing sync requests, not an interval of time from the last time the sync completed.
for example, if you scheduled a sync every 5mins, and a sync takes more than 5 mins, that would fire another sync request even if there's an ongoing sync....
- Editat de yaphets 2 iulie 2012 09:16
For the first error, it is because the destination database is outdated with respect to the source database.
It’s outdated because the source database has deleted some records and cleaned up its tombstones but not synced to destination database, there are deletions that the source database no longer knows about. Therefore, the source provider cannot send changes that represent these deletions to the destination provider. Currently the tombstone retention period is 45 days.
You need to deprovision the sync group and provision again in this case.
The second error is caused by the first error, when the destination database is outdated, the corresponding sync group member will be in an unhealthy state which you can’t reprovision/sync/etc…
You can only deprovision the sync group member in such an unhealthy state.
is the 24-hour retention period documented somewhere else? when was this introduced?
imho, that's something people should know about and i personally think that's too short.
current documentation only mentions the 45-day out-of-date status. (http://msdn.microsoft.com/en-us/library/windowsazure/6c1a99b9-41ce-4d4c-9c77-2564ee63615e#bkmk_databaseoutofdatestatus)