SQL Azure Data Sync stuck in Processing State since 5 Sep 2014

Hi,
I've a sync group stuck in "processing" state since 5 Sep 2014, have tried to restart the client PC, restarted the sync service and also tried to regenerate the sync agent key, but still in vain. Would anyone please help me to figure it out what's
the problem? As I have many sync groups running without any problem for more than a year and encountered this problem recently (in this 3 months). 
Here's the sync group details:
Sync Group Name
    ew_sync_a054
Status
    Processing
LAST SYNC
    9/5/2014 5:57:35 PM
Sync Group ID
    94f34eaa-cf1c-4af0-950e-7aa565ccc781_East Asia
Location
    East Asia
Subscription Name
    Solo Customer Batch 2
Subscription ID
    cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Conflict Resolution
    Client Wins
Thanks for your help.
Best regards,
Michael Yung

Hi Bowen,
I've checked the local agent has been offline at 2014/09/05 18:00:00 UTC+8, as the shop close every night and they will shut down the computer, but they've turned on the computer in next day morning, and they keep turning that off at night, turn
back on at next morning.
I've checked the agent was online during that "stuck" period when the computer was turned on, as I could click the "PING SYNC SERVICE" and it reported it could reach the sync server, and I could also view from the portal that the agent
was online, just the sync group stuck in the "processing" status.
Best regards,
Michael Yung

Similar Messages

  • SQL Azure Data Sync stuck in Processing State since 14 Sep 2014

    Hi,
    I've a sync group stuck in "processing" state since 14 Sep 2014, have tried to restart the client PC, restarted the sync service and also tried to regenerate the sync agent key, but still in vain. Would anyone please help me to figure it out what's
    the problem? This problem happened across my sync group very frequent recently (they're located in different physical locations), but still no workaround or the root cause :(
    Here's the sync group details:
    Sync group name:  ew_sync_a069
    Status
    Processing
    LAST SYNC
    9/14/2014 11:11:22 PM
    Sync Group ID
    4a604aad-e318-469d-adde-9ed4e1d52ead_East Asia
    Location
    East Asia
    Subscription Name
    Solo Customer Batch 3
    Subscription ID
    a68811f9-f82a-4e7c-b93c-d1bee226f84b
    Conflict Resolution
    Client Wins
    Thanks
    for your help.
    Best regards,
    Michael Yung

    As the client need the sync to be fixed ASAP, cannot wait for the answer / help, I've removed the sync agent, compare the data (what data need to download from Azure to client, what data need to upload from client to Azure) and recreate back the sync group.
    Hi Micheal,
    Is this the workaround in your scenario? Since the Azure SQL Data Sync failed, the Microsoft support engineer will help to solve the problem from backend based on your subscription ID and Sync Group ID. Sometime delay might be expected. Your patience is
    greatly appreciated. Thank you for your understanding and support.
    Regards,
    Charlie Liao
    TechNet Community Support

  • SQL Azure Data Sync stuck in Processing State since 16 Aug 2014

    Hi,
    I've a sync group stuck in "processing" state since 16 Aug 2014, have tried to restart the client PC, restarted the sync service and also tried to regenerate the sync agent key, but still in vain. Would anyone please help me to figure it out what's
    the problem? As I have many sync groups running without any problem for more than a year and encountered this problem recently (in this 3 months). 
    Here's the sync group details:
    Sync Group Name
    ew_sync_a037
    LAST SYNC
    8/16/2014 9:17:37 PM
    Sync Group ID
    15a3a3c5-f867-4ba4-b7af-92fb5c8d36a6_East Asia
    Location
    East Asia
    Subscription Name
    Pay-As-You-Go
    Subscription ID
    f979186d-23f7-45e3-8d5e-c14c89c56a7f
    Conflict Resolution
    Client Wins
    Thanks for your help.
    Best regards,
    Michael Yung

    Hi Michael,
    Thanks for you posting the subscription ID and Sync Group ID. The Microsoft support engineer will help to solve the problem from backend. Sometime delay might be expected. Your patience is greatly appreciated. Thank you for your understanding and support.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Data Sync stuck in processing

    Can you please delete my data sync? I tried to cancel the data sync, so I could delete it but it has been stuck in processing for almost 24 hours now. The subscription id is 2b362515-3f77-44fc-9803-08334705d01a and the sync group is called DevSyncGroup.

    Hi CpAtMtb,
    Thanks for your information about  subscription ID.
    The Microsoft support engineer will help to solve the problem from backend. Sometime delay might be expected. Your patience is greatly appreciated. Thank you for your understanding and support.
    Besides, any of the following can result in a sync group being stuck in the processing state.
    • The client agent is offline.
     Be sure that the client agent is online then try again.
    • The client agent is uninstalled or missing.
     If the client agent is uninstalled or otherwise missing:
        1. Remove agent XML file from the SQL Data Sync (Preview) installation folder if the file exists.
        2. Install the agent on same/another on-premise computer, submit the agent key from the portal generated for the agent that’s showing offline.
    • The SQL Data Sync (Preview) service is stopped.
        1. In the Start menu, search on Services.
        2. Click Services in the Programs section of the search results.
        3. Find the SQL Data Sync (Preview) service.
        4. If the service status is Stopped right-click the service name and select Start from the dropdown menu.
    Reference :  http://msdn.microsoft.com/en-us/library/azure/hh667321.aspx#ProcessingError
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • Sync stuck on processing state

    On 10/02/2014 20:34 ET there's an error in the sync group (This is production)
    Sync failed with the exception "Error in RelationalProviderProxy.ExecuteAndRetryServiceOperation, Method: Void <BeginSession>b__0(), CurrentTimeout: 60 Exception Details: System.ServiceModel.Security.MessageSecurityExceptionThe security timestamp
    is invalid because its creation time ('2014-10-03T01:04:31.703Z') is in the future. Current time is '2014-10-03T00:59:31.509Z' and allowed clock skew is '00:05:00'.Server stack trace:    at System.ServiceModel.Security.SecurityTimestamp.ValidateFreshness(TimeSpan
    timeToLive, TimeSpan allowedClockSkew)   at System.ServiceModel.Security.SecurityTimestamp.ValidateRangeAndFreshness(TimeSpan timeToLive, TimeSpan allowedClockSkew)   at System.ServiceModel.Security.ReceiveSecurityHeader.ReadTimestamp(XmlDictionaryReader
    reader)   at System.ServiceModel.Security.ReceiveSecurityHeader.ExecuteFullPass(XmlDictionaryReader reader)   at System.ServiceModel.Security.StrictModeSecurityHeaderElementInferenceEngine.ExecuteProcessingPasses(ReceiveSecurityHeader securityHeader,
    XmlDictionaryReader reader)   at System.ServiceModel.Security.ReceiveSecurityHeader.Process(TimeSpan timeout, ChannelBinding channelBinding, ExtendedProtectionPolicy extendedProtectionPolicy)   at System.ServiceModel.Security.TransportSecurityProtocol.VerifyIncomingMessageCore(Message&
    message, TimeSpan timeout)   at System.ServiceModel.Security.TransportSecurityProtocol.VerifyIncomingMessage(Message& message, TimeSpan timeout)   at System.ServiceModel.Security.SecurityProtocol.VerifyIncomingMessage(Message& message, TimeSpan
    timeout, SecurityProtocolCorrelationState[] correlationStates)   at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.ProcessReply(Message reply, SecurityProtocolCorrelationState correlationState, TimeSpan timeout)   at
    System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)   at System.ServiceModel.Channels.ServiceChannel.Call(String
    action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage
    message)Exception rethrown at [0]:    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)  
    at Microsoft.SqlAzureDataSync.ClientServerCommon.ISyncServiceContract.BeginSession(String scopeName, SyncTaskRequestInfo syncInfo, DssConflictResolutionPolicy conflictPolicy, String objectSchema)   at Microsoft.SqlAzureDataSync.AgentHostLib.RelationalProviderProxy.<BeginSession>b__0()
      at Microsoft.SqlAzureDataSync.AgentHostLib.SyncServiceProxy`1.ExecuteAndRetryServiceOperation(Action operation)Inner exception: The security timestamp is invalid because its creation time ('2014-10-03T01:04:31.703Z') is in the future. Current time is
    '2014-10-03T00:59:31.509Z' and allowed clock skew is '00:05:00'."    For more information, provide tracing ID ‘a4808300-c03c-4d5d-a658-0b220bab58c6’ to customer support.
    And after that the Sync got stuck in the processing state, i try to stop it and resend it again but is still trying to stop it. I already fix the time settings in the server and restart the service of sync and nothing. Here are the info related to the Sync
    Group. 
    SYNC GROUP ID
    045ac6f9-d27a-47ba-8194-7aadf8fc90de_East US
    LOCATION
    East US
    SUBSCRIPTION NAME
    Pay-As-You-Go
    SUBSCRIPTION ID
    399ba2d3-f357-4c7b-a52e-972bcb3cc2d7
    CONFLICT RESOLUTION
    Client Wins

    Hi,
    We've just reset the sync group status at our service backend. Could you please check whether your sync back to work now? Let us know if any more question.
    Regards,
    Bowen

  • SQL Azure Data Sync 'Refresh Schema' Not Working

    I am trying to setup SQL Azure sync from my core database to a reporting database (both SQL Azure).  I successfully setup sync with my secondary (and smaller schema) database.  When I try to define the Sync rules and hit Refresh Schema it never
    finishes.  I've been trying to do this off/on for the last ~3 months so I don't think it is an intermittent issue.
    SyncGroup - 9ea034c4-8fc6-43e8-a12f-a1e3d1479e25_EastUS
    When I look at my web console I see:
    Failed to load resource: the server responded with a status of 500 (Internal Server Error): https://manage.windowsazure.com/DataSync/RefreshCloudDbSchema
    Similar (same issue?) from Sept 20, 2013
    http://www.networksteve.com/forum/topic.php/SQL_Azure_Data_Sync_%27Refresh_Schema%27_Not_Working/?TopicId=41473&Posts=0
    Thanks, Aaron

    Per https://msdn.microsoft.com/en-us/library/azure/jj590380.aspx?f=255&MSPPError=-2147217396 I had (2) columns that had over 50 characters in length preventing the page from loading.
    Once they were removed the schema was able to refresh.

  • Azure Data Sync Log Take Too Much Time to Load

    Hi,
    I've found that the Azure Sync Log inside the Portal take too much time to load if my sync group was created long time ago. i.e. for those new sync group with only a few logs, it will take around 5 seconds for loading. However, I've many sync group created
    more than 1 year, and it will take me up to 10 minutes for viewing the first page of the logs.
    It seems the Portal will download ALL the logs to my browser even I just want to view the most recent logs (maybe I just want to view the last 10 records, but it will download the whole 5000 pages?)
    It will be great if the Portal only fetch the data of the page I am currently viewing, instead of fetching all the logs.
    Is there any ways to speed up the log loading time?
    Michael Yung

    Hello,
    I suggest you post a feedback on
    Azure SQL Data Sync feedback forum.
    All of the feedback you share in the forum will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • Error when running scheduled refresh from SQL Azure data

    I have a PowerPivot that connects to a SQL Azure database table.  I added the username and password in the PowerPivot connection.  It refreshed fine manually straight from PowerPivot.  However, when I upload the excel file to Power BI
    and I schedule a refresh, it fails with the following error message:
    Sorry, something went wrong. Please try again. Correlation ID: d43f07fc-cc0c-461c-b25e-68e866a2a911
    I went through this FAQ (http://office.microsoft.com/en-us/office365-sharepoint-online-enterprise-help/scheduled-refresh-faq-HA104180763.aspx#_Toc388441416)
    and the steps have me also saving the password in the connection string.  However the connection string (under tab Data->Connections) is grayed-out and I am unable to enter the password.
    Thanks for your help...

    Hi,
    When you refresh in Excel client, do you get a prompt for the password?
    What worked for me in the past, is the following process:
    1. Within PowerPivot, get the data but don't save the password there.
    2. Once you get the data go back to Excel, switch to Data ribbon >> Connections, and select the connection(s) that were created in PowerPivot and select to save the password.
    3. Refresh the data (it will prompt for the password), save the file.
    4. Just to be sure, open the file again, refresh and see that it is not prompting for a password.
    GALROY

  • Sync stuck in Processing

    Hello!
    My Sync group is stuck in Processing status, and I'm unable to make changes or sync data anymore. This is in a production environment, so it's disruptive to our reporting processes.
    Here's the error:
    Sync completed with warnings in 259403.73 seconds. Upload:   0 changes applied/0 failed  Download: 0 changes applied/789 failedData Sync will stop synchronizing changes for this sync group member in 39 days if the failures are not resolved.    
    For more information, provide tracing ID ‘167f5e6b-ac06-4d04-9b21-94c6180d45ba’ to customer support.

    Sorry for the late delay...
    ece4bf55-7077-420b-8c83-1cbf2f8c44d7_East US - both databases that are part of the sync group are still showing as Processing on the Properties screen. The sync itself fails with this error:
    Sync failed with the exception "An unexpected error occurred when applying batch file C:\Resources\directory\07eb40e27bc6414382cf30de457d7c69.NTierSyncServiceWorkerRole.BatchDir\DSS_34e7aaa4-2ff4-4e4d-9424-622dc5764287\sync_28e4cfaa696c4fd5b9010bb8ce7343d0c4a5a2354a324b178199442cc1969fd7\c5bb69f0-df20-43c7-b5a6-00f80d6883c9.batch.
    See the inner exception for more details.Inner exception: Failed to execute the command 'UpdateCommand' for table 'dbo.[name removed]; the transaction was rolled back. Ensure that the command syntax is correct.Inner exception: SqlException Error Code: -2146232060
    - SqlError Number:10054, Message: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) Inner exception: An existing connection was forcibly
    closed by the remote host"    For more information, provide tracing ID ‘34e7aaa4-2ff4-4e4d-9424-622dc5764287’ to customer support.
    I've turned off automatic sync now to see if that makes any difference.

  • Azure Cloud Service Stuck in "Stopping" state for a long time (12 hours)

    Does anyone have suggestions what to do with the issue I have. I tried to stop my Cloud Service the service is now basically stuck in "Stopping" State and been there over 12 hours. In my Cloud service there is 16 Virtual Machines I am using in
    testing.
    I tried to start Cloud Service but it also failed with error "Could not start the virtual machine deployment.".
    Is there something I could do or some way to get Microsoft Support (without paying extra)? I have "Visual Studio Premium with MSDN" so i have no other support but billing from Microsoft :(

    Managed to find the solution. I stopped and deallocated all the Virtual Machines. After that the Cloud Service status changed to stopped state. After that it was possible to start the Cloud Service again.

  • Cloud service stuck in "Deleting..." state since July 2014

    One of my cloud services has been stuck at the "Deleting..." state in the Azure portal (and also shown as such in VS2013 server explorer) since ~July 2014
    I can't interact with the role to do anything with it - and have no idea why it won't go away.
    Can anyone suggest what I should do about this? Thanks for any help.

    Please refer this thread
    https://social.msdn.microsoft.com/Forums/azure/en-US/e71fa367-b478-44ce-8e41-ec5a8eec7b83/azure-cloud-service-stuck-at-deleting?forum=windowsazuredevelopment
    Bhushan | Blog |
    LinkedIn | Twitter

  • G1 Sync stuck at Backing up, since July 2

    I have upgraded to 3.0 and synced many times. But since July 2nd. I have been unable to sync my phone.
    I either get unable to find phone via an error message or Backing Up is stuck in an endless loop for hours.
    I've rebooted both PC and iPhone
    If I cancel the sync via iTunes or the iPhone, "Canceling Sync" is stuck in an endless loop.
    I am able to pull pictures and Last Fm can scrobble.

    I beliebe I have solved my own problem
    I saw a suggestion in another post that said to try a different USB port, and that did the trick.
    I guess iTunes does not like to sync over USB when that cable is plugged into a hub.

  • SQL Data Sync Agent can not start - Debug error in windows 7 x86

    Log file as per below
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:Main,
    message:Microsoft SQL Data Sync Windows service is starting as a Windows Service.
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:OnStart,
    message:Microsoft SQL Data Sync Windows service starting.
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:OnStart,
    message:Starting a service worker thread.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:OnStart,
    message:Started a service worker thread.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:OnStart,
    message:Microsoft SQL Data Sync Windows service started successfully.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartUxWcfService,
    message: Namedpipe bd54233d-16ce-46d3-8858-5e564732b21c, BaseAddress net.pipe://localhost/bd54233d-16ce-46d3-8858-5e564732b21c
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartUxWcfService,
    message: Opened WCF Host
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartServiceThread,
    message: GetEntryAssembly().Location: C:\Program Files (x86)\Microsoft SQL Data Sync\bin\LocalAgentHost.exe, GetExecutingAssembly().Location: C:\Program Files (x86)\Microsoft SQL Data Sync\bin\LocalAgentHost.exe, Process.GetCurrentProcess().StartInfo.WorkingDirectory:
    LocalAgentHost 1/3/2013 11:55:37 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:AgentConfigDataManager.DownloadAndCacheServiceUrisFromLocator,
    message:Scale unit found
    AgentCore 1/3/2013 11:55:40 AM  id:AgentCore_InstanceStarted, rId:, sId:65915150-1284-4a17-9c13-d58e2830fcd9, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0
    ThreadId:40. Dispatcher started. Waiting
    ThreadId:43. GetRequest started.
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:46. GetRequest started.
    ThreadId:41. GetRequest started.
    ThreadId:48. GetRequest started.
    ThreadId:45. GetRequest started.
    ThreadId:42. GetRequest started.
    ThreadId:47. GetRequest started.
    ThreadId:44. GetRequest started.
    ThreadId:49. GetRequest started.
    ThreadId:50. GetRequest started.
    ThreadId:51. GetRequest started.
    ThreadId:52. GetRequest started.
    ThreadId:53. GetRequest started.
    ThreadId:54. GetRequest started.
    ThreadId:55. GetRequest started.
    ThreadId:56. GetRequest started.
    ThreadId:57. GetRequest started.
    ThreadId:58. GetRequest started.
    ThreadId:59. GetRequest started.
    ThreadId:60. GetRequest started.
    ThreadId:61. GetRequest started.
    ThreadId:62. GetRequest started.
    ThreadId:63. GetRequest started.
    ThreadId:64. GetRequest started.
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest

    Hi,
    I believe that your issue is resolved by now. Please try this step is the issue still persists.
    its security issues and re-install the data sync with domainname\Myaccount user and give the user as adminitsrator privileges and change the time of your system.
    http://social.technet.microsoft.com/wiki/contents/articles/2655.sql-azure-data-sync-troubleshooting-guide.aspx
    Girish Prajwal

  • Data Sync logs not showing in Azure Portal

    The Data sync Logs are no longer showing in the Azure Portal.  this started about a month ago.  Please help.   I opened a support ticket with Azure Support and they suggest the Logs Storage may have become full.
    LAST SYNC
    12/30/2014 7:28:22 AM
    SYNC GROUP ID
    ac33f15d-40c7-4e11-9f8c-c840c8cd1732_East US
    LOCATION
    East US
    SUBSCRIPTION NAME
    GEX-Azure-1
    SUBSCRIPTION ID
    653e04dd-c69f-4b16-8fd3-5efa954a6132
    CONFLICT RESOLUTION
    Hub Wins
    James Glenn

    Hi James,
    If there is on-premise database in the sync group,  you can use the following methods to check the log.
    • Check the Event Log entries on the box where you installed the SQL Data Sync Agent.
    Event Viewer->Applications and Services Logs->SQL Azure Data Sync Preview or Event Viewer->Applications and Services Logs->Data Sync Service
    • Turning logging in verbose mode. Open LocalAgentHost.exe.config in notepad. This file should be present in your installation directory.
    a) Uncomment the section that is currently commented < !-- < switches> < add name="SyncAgentTracer" value="4" /> < /switches> < trace autoflush="true" indentsize="4"> < listeners> <
    add name="myListener" type="Microsoft.SqlAzureDataSync.ClientLogging.DSSClientTraceListener, Microsoft.SqlAzureDataSync.ClientLogging, Version=2.0.0.0" initializeData="DSSAgentOutput.log" /> < remove name="Default"
    /> < /listeners> < /trace> -->
    b) Stop and restart SQL Azure Data Sync Preview Windows Service. Now you would find the detailed logs in files named DSSAgentOutput*.log
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • SQL Azure Synch

    I have created a synch between two azure databases and the hub database has a size of  20 GB .How long it will take the synch process to complete? Could any one help me on this 

    Hi,
    I am sure you have the answer by now, if not please have a check on a similar thread.
    http://social.msdn.microsoft.com/Forums/windowsazure/en-US/cab00a4f-603f-43f2-9a22-e0406db19a77/many-problems-with-sql-azure-data-sync
    Regards,
    Mekh.

Maybe you are looking for