5 martie 2012 11:30
Do you know how hard it is to report a problem with data sync? The Microsoft support wizard deemed my problem was critical since it affects my delivery programme and I was directed by the wizard to report via online telephone call to US azure helpdesk (rather than email). This online call service was then reported as not available and I was asked to complete a customer satisfaction survey while trying to report a fault! Following my international phone call to Azure Customer Support in US, I was then redirected to this data sync forum since the data synch programme is still in beta. My helpdesk call has been closed and my 'critical' problem remains unanswered.
Perhaps the data synch error log should direct to this forum in the first place until the capability is fielded?
Server id: zsn3wfc2q1
Region: West Europe
Time / Date: 05/03/2012 (thats the 5th of March in UK Calendar). Repeated between approx 1000 hrs to 1100 hrs.
Tracing Id: 72dc0a69-942f-49e3-8a6d-e97eb1da0110’
Sync failed with the exception "GetStatus failed with exception:
Sync worker failed, checked by GetStatus method. Failure details:
An unexpected error occurred when applying batch file C:\Resources\directory\ceda43982be34e059edcb35ef8fad8df.NTierSyncServiceWorkerRole.LS1\DSS_syncjobr0aozbk4eue2mziyuynb0sy5\6d449307-63cc-47ba-b246-a889397c771a.batch. See the inner exception for more details.
Inner exception: Failed to convert parameter value from a DateTime to a Int32.
Inner exception: Invalid cast from 'DateTime' to 'Int32'.
For more information, provide tracing id ‘72dc0a69-942f-49e3-8a6d-e97eb1da0110’ to customer support.
5 martie 2012 15:18
Well the message is different but the synchronisation problem remains unclear.
Sync failed with the exception "We have encountered an issue in syncing your data."
For more information, provide tracing id ‘c6cb30da-f9cd-4c5f-a559-23d964ecc722’ to customer support.
6 martie 2012 00:00
Sorry to hear you're experiencing an issue and having problems reporting it. We should be able to help you out here though.
We're taking a look at the errors more closely using the tracing ids you supplied. In the meantime can you also clarify your configuration and supply more a little more information?
- Are you syncing between two SQL Azure databases or between SQL Server and SQL Azure?
- For your Sync Group there is an ID field in the top right of the UI when the Sync Group is highlighted in the portal - what is it?
- Was the sync working and then started to fail or did it never succeed?
- Can you check the database schemas on all members - any chance that there is a mismatch of column types for any of the DateTime columns?
6 martie 2012 22:02
The reason for sync failure with tracing id 'c6cb30da-f9cd-4c5f-a559-23d964ecc722' is
Cannot enumerate changes at the RelationalSyncProvider for table 'dbo.CoreStaff'
Invalid object name 'dbo.CoreStaff'
Error Code: -2146232060 - SqlError Number:208.
Must have happened when the sync ran after the table were dropped.
- Editat de Anurag_Sharma 6 martie 2012 22:03