Azure Sync Group stuck in processing
I have a "Amygdalum DEMO" sync group on the "af8ulpf55q" server, it is stuck in processing and I need it reset. It has been stuck for 5 days and I cannot update the schema to add new sync data.
STATUS
Warning
LAST SYNC
3/15/2015 8:22:51 PM
SYNC GROUP ID
cf026340-56c7-44d7-b14b-9c4f3641eb82_West US
LOCATION
West US
SUBSCRIPTION NAME
Pay-As-You-Go
SUBSCRIPTION ID855c7c63-4e63-4c8d-8228-4001ff2eda12
CONFLICT RESOLUTION
Client Wins
Hi,
After investigation I found the sync stuck is caused by your local agent offline. We've already released a hotfix to avoid stuck in this scenario.
And currently our backend shows that the related sync group is already removed, could you please let me know if there are any more question?
Regards,
Bowen
Similar Messages
-
Sql Azure Sync - Sync Group stuck in "Processing..." state
I am experiencing 4 of my sync groups being stuck in "Processing.." State
It seemed to happen when connection to the agent was lost. It has not synced now in 20+ days and although agent now connected, sync groups just keep saying "Processing...."
I can find no logs anywhere to what is causing the problem.
Please can you assist.Hi,
Thank you for your post. I am currently researching on this and will revert back to you when i have more information on this. Appreciate your patience.
Regards,
Bharath -
SQL Sync group stuck on processing status
Hi,
The sync group below has been stuck on processing since Jan 8, this sync group sync the hub DB with two Azure DB (all are on Azure), one of the Azure DB can sync normally but the other one stuck (keep in the processing status)
Azure Product Subscription ID:
43051d1f-7dc4-4e4f-81f4-3e027983733c
Sync Group ID:
4124f828-7e36-47dd-84f5-8b58a5e453a7_East Asia
Status
Processing
Would you please help me to reset the status from backend? Thanks!
Regards,
Michael YungHi Michael,
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 understanding and support.
Any of the following can result in a sync group being stuck in the processing state.
a)The client agent is offline.
Be sure that the client agent is online then try again.
b)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.
c)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
If you have any feedback on our support, please click
here.
Eric Zhang
TechNet Community Support -
Sync Group Stuck with "processing" status
I have a sync group that is stuck with "processing" status since 23/12/2014. Can this be solved from backend?
Status
Processing
LAST SYNC
23/12/2014 10:05:34
Sync Group ID
73d5bd9d-33ec-47cc-8808-df5c0504523e_West Europe
Location
West Europe
Subscription Name
Compass Cloud
Subscription ID
cb1e8791-b516-421b-898a-65f09794b512
Conflict Resolution
Client Wins
Thank you for your help.Hi SiggeWynant,
Thanks for your information about 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
understanding and support.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support -
Azure Sync group hangs in processing , can't delete or kill process
Hi support,
I have a hanging sync group that I can't stop or delete. Its been running for over 14 days for a process that normally takes 2-3 hours to run. The stop button is greyed out and I get an error "Sync group is not deleted" when try to
delete. The Agent is online.
Any engineer that can stop this process ?
STATUS
Processing
SYNC GROUP ID
be56964b-8e8f-49fb-b736-1340822ee15a_East US
SUBSCRIPTION ID
145a8ac3-96e5-42fa-9b80-cf0011ca309a
CONFLICT RESOLUTION
Client WinsThanksHi,
Sorry for the late response and appreciate your patience. We've reset the backend status for your syncgroup. Please take a look. We will keep you update with the root cause.
Regards,
Bowen -
Sync Group stuck in 'Processing'
Can you please reset the following sync group:
Status Processing
Sync Group ID 3f3f4612-b850-4b5a-bcd0-e0db7c0d9ce7_East
US Location East US
Subscription ID ca240b2a-97d7-4de8-a7e2-510fe4458740Hi Jason,
Thanks for your information about 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 understanding and
support.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support -
URGENT: 22 Sync groups stuck in processing mode and cannot be cancelled
The below sync groups stopped working and keep displaying "Processing", I've tried to stop the job but no response, I've also tried to regenerate the sync agent keys, and tried to restart the agent, reboot the client PC, but all not working. They
seems all stop working at the same time 15 hours ago. But they are across different database, different subscriptions.
Can anyone please help me out for that? the problem sync groups are as below:
Sync Group ID
f6d51362-7a47-47fb-84b3-9c23445626e3_East Asia
Subscription ID
f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
f1216549-eb83-4a2e-afa8-9135f1f92006_East Asia
Subscription ID
f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
6d45b9d2-0a57-43a9-8e14-004432512b73_East Asia
Subscription ID
f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
f14d2c29-08a4-4dd3-a49f-7bf0f7f8b2f3_East Asia
Subscription ID
f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
751dc6f2-8c85-4bae-a7cc-0bb89abcbb66_East Asia
Subscription ID
f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
574115d1-de83-40ce-8de3-5a424d8cdedc_East Asia
Subscription ID
f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
15a3a3c5-f867-4ba4-b7af-92fb5c8d36a6_East Asia
Subscription ID
f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
7ceaafb5-7af7-4b18-af5a-2de75890227a_East Asia
Subscription ID
f979186d-23f7-45e3-8d5e-c14c89c56a7f
Sync Group ID
f4b4efb3-0a4c-4eb6-a826-316f5f22fbb2_East Asia
Subscription ID
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
920b1c9a-5ba7-49af-ad1a-37470b6a47da_East Asia
Subscription ID
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
9baf8167-9ee9-4ce4-bc88-abc0797a343f_East Asia
Subscription ID
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
2ae3a888-7cb2-4e18-a0ec-9850bb91e01a_East Asia
Subscription ID
45d375de-c29f-4a14-926c-1fe744d157b7
Sync Group ID
734fcc26-46e6-444a-a0d1-d3ff4c5834f7_East Asia
Subscription ID
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
0d315093-8977-4229-8ba4-ece0fb10c3f9_East Asia
Subscription ID
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
58cb062a-57a0-4ec6-8e9d-21fe021cd5b5_East Asia
Subscription ID
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
652e5ef2-c1db-4989-8d15-472590747463_East Asia
Subscription ID
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
Sync Group ID
8cfe554c-f4df-4167-b449-23da5ed0cf68_East Asia
Subscription ID
45d375de-c29f-4a14-926c-1fe744d157b7
Sync Group ID
56c9e45b-51e1-4fe5-8a35-df86c0ab68b2_East Asia
Subscription ID
a68811f9-f82a-4e7c-b93c-d1bee226f84b
Sync Group ID
826c0497-b9e4-4664-b404-ee75f54b407d_East Asia
Subscription ID
a68811f9-f82a-4e7c-b93c-d1bee226f84b
Sync Group ID
4a604aad-e318-469d-adde-9ed4e1d52ead_East Asia
Subscription ID
a68811f9-f82a-4e7c-b93c-d1bee226f84b
Sync Group ID
db07173c-db1d-40df-98e1-47a158b6c873_East Asia
Subscription ID
a68811f9-f82a-4e7c-b93c-d1bee226f84b
Sync Group ID
9ad4eab4-6499-4976-b6f1-813b0ce93539_East Asia
Subscription ID
a68811f9-f82a-4e7c-b93c-d1bee226f84b
EDITED: Should be 31 sync groups have encountered this problem, already have caused fatal impact for our business, hope anyone can help, workaround solution also welcome. Thanks!
Group Name
Sync Group ID
Subscription ID
ew_sync_a003
f6d51362-7a47-47fb-84b3-9c23445626e3_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a013
f1216549-eb83-4a2e-afa8-9135f1f92006_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a022
6d45b9d2-0a57-43a9-8e14-004432512b73_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a026
e267e22a-1764-4e19-9ee8-a62b079a3855_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a029
f14d2c29-08a4-4dd3-a49f-7bf0f7f8b2f3_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a032
ac6e92b5-f7a3-41db-b912-47f65de3d550_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a034
751dc6f2-8c85-4bae-a7cc-0bb89abcbb66_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a035
574115d1-de83-40ce-8de3-5a424d8cdedc_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a037
15a3a3c5-f867-4ba4-b7af-92fb5c8d36a6_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a038
7ceaafb5-7af7-4b18-af5a-2de75890227a_East Asia
f979186d-23f7-45e3-8d5e-c14c89c56a7f
ew_sync_a041
f4b4efb3-0a4c-4eb6-a826-316f5f22fbb2_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a044
911932b3-e7a3-4238-9e1c-d9adb05fba8b_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a045
1d144ceb-e564-437e-854d-0f73b08f9c4a_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a046
920b1c9a-5ba7-49af-ad1a-37470b6a47da_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a047
9baf8167-9ee9-4ce4-bc88-abc0797a343f_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a049
2ae3a888-7cb2-4e18-a0ec-9850bb91e01a_East Asia
45d375de-c29f-4a14-926c-1fe744d157b7
ew_sync_a052
734fcc26-46e6-444a-a0d1-d3ff4c5834f7_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a053
8d811816-9455-4283-ab4d-e7bbb39b1319_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a054
94f34eaa-cf1c-4af0-950e-7aa565ccc781_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a056
0d315093-8977-4229-8ba4-ece0fb10c3f9_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a057
58cb062a-57a0-4ec6-8e9d-21fe021cd5b5_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a058
652e5ef2-c1db-4989-8d15-472590747463_East Asia
cda925fa-16c4-44b6-b3dc-8fc0cb82ad07
ew_sync_a060
8cfe554c-f4df-4167-b449-23da5ed0cf68_East Asia
45d375de-c29f-4a14-926c-1fe744d157b7
ew_sync_a061
56c9e45b-51e1-4fe5-8a35-df86c0ab68b2_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a063
826c0497-b9e4-4664-b404-ee75f54b407d_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a064
41126d10-b858-468a-8590-d0bb03d2814c_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a069
4a604aad-e318-469d-adde-9ed4e1d52ead_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a071
db07173c-db1d-40df-98e1-47a158b6c873_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a073
a0208e66-7d96-4528-a0ac-70e7989e44e8_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a074
9ad4eab4-6499-4976-b6f1-813b0ce93539_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84b
ew_sync_a076
5944edb5-4e2e-4fbf-8b7b-a880a8a6b27e_East Asia
a68811f9-f82a-4e7c-b93c-d1bee226f84bHi Sofiya,
Thanks for your help. According to the log from sync agent, it just like a normal log, without any error. We have set the sync to 5 minutes intervals, but seems the agent have not proceed the job as the cloud said another job is processing:
LocalAgentHost 4/8/2014 6:56:59 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 4/8/2014 6:56:59 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 4/8/2014 6:56:59 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 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0, methodName:OnStart,
message:Started a service worker thread.
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0, methodName:OnStart,
message:Microsoft SQL Data Sync Windows service started successfully.
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0, methodName:StartUxWcfService,
message: Namedpipe e0ec8c56-cf3f-4aea-855b-2981f6313d06, BaseAddress net.pipe://localhost/e0ec8c56-cf3f-4aea-855b-2981f6313d06
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0, methodName:StartUxWcfService,
message: Opened WCF Host
LocalAgentHost 4/8/2014 6:56:59 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, 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 4/8/2014 6:57:01 id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0, methodName:AgentConfigDataManager.DownloadAndCacheServiceUrisFromLocator,
message:Scale unit found
AgentCore 4/8/2014 6:57:01 id:AgentCore_InstanceStarted, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, version:4.0.89.0
ThreadId:19. Dispatcher started. Waiting
ThreadId:20. GetRequest started.
ThreadId:19. Dispatcher calling GetRequest
ThreadId:21. GetRequest started.
ThreadId:22. GetRequest started.
ThreadId:23. GetRequest started.
ThreadId:24. GetRequest started.
ThreadId:25. GetRequest started.
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling PutRequest
ThreadId:19. Dispatcher started. Waiting
ThreadId:19. Dispatcher calling GetRequest
ThreadId:20. GetRequest finished. RequestId:f4d245ad-b209-463e-8c43-4c59c7ea6737
CommandAndControlClient 4/8/2014 7:17:20 id:CommandAndControlClient_GetRequest, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737
CommandAndControlClient 4/8/2014 7:17:20 id:CommandAndControlClient_AckRequest, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737
ClientRequestHandler 4/8/2014 7:17:20 id:ClientRequestHandler_Request, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737,
serializedRequest:<?xml version="1.0" encoding="utf-16"?>
<SyncRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<PostActionSucceededWork xsi:nil="true" />
<LogInfo>
<DetailedProviderTraces>false</DetailedProviderTraces>
<SyncGroupId>0d315093-8977-4229-8ba4-ece0fb10c3f9</SyncGroupId>
<SyncGroupMemberIdList />
<HubDbId>f8e45e70-020f-4b97-9ca8-c70e879a24a7</HubDbId>
<SyncGroupMemberId>87b18bc7-551f-4efe-9082-2ad47b8a99d9</SyncGroupMemberId>
<AgentId>f995868a-18fd-4786-875e-34996ffd5325</AgentId>
<AgentInstanceId>6fe18179-e983-4288-a660-2b9f16762603</AgentInstanceId>
<TracingId>f4d245ad-b209-463e-8c43-4c59c7ea6737</TracingId>
<DssServerId>edbf9ba4-b43f-4521-84a4-6349d490f5a8</DssServerId>
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
<SqlAzureActivityId>00000000-0000-0000-0000-000000000000</SqlAzureActivityId>
</LogInfo>
<ScopeName>AA499444-A041-47EA-B79B-6A1A503E6251</ScopeName>
<SyncGroupMemberId>87b18bc7-551f-4efe-9082-2ad47b8a99d9</SyncGroupMemberId>
<LocalDatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</LocalDatabaseId>
<RemoteDatabaseId>f8e45e70-020f-4b97-9ca8-c70e879a24a7</RemoteDatabaseId>
<ConflictResolutionPolicy>LocalWins</ConflictResolutionPolicy>
<SyncDirection>UploadAndDownload</SyncDirection>
<SqlSyncProviderBatchSizeInMB>24</SqlSyncProviderBatchSizeInMB>
<SqlSyncProviderMATSizeInMB>25</SqlSyncProviderMATSizeInMB>
<SqlSyncProviderMatRowCount>50000</SqlSyncProviderMatRowCount>
</SyncRequest>
ThreadId:19. Dispatcher calling PutRequest
ThreadId:19. Dispatcher started. Waiting
ThreadId:19. Dispatcher calling GetRequest
ThreadId:24. GetRequest finished. RequestId:68dfcf90-0823-4de3-87e8-79a0bc813d00
CommandAndControlClient 4/8/2014 7:17:20 id:CommandAndControlClient_GetRequest, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:68dfcf90-0823-4de3-87e8-79a0bc813d00
CommandAndControlClient 4/8/2014 7:17:20 id:CommandAndControlClient_AckRequest, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:68dfcf90-0823-4de3-87e8-79a0bc813d00
ClientRequestHandler 4/8/2014 7:17:20 id:ClientRequestHandler_Request, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:68dfcf90-0823-4de3-87e8-79a0bc813d00,
serializedRequest:<?xml version="1.0" encoding="utf-16"?>
<CleanupTombstoneRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<PostActionSucceededWork xsi:nil="true" />
<LogInfo>
<DetailedProviderTraces>false</DetailedProviderTraces>
<SyncGroupId>00000000-0000-0000-0000-000000000000</SyncGroupId>
<SyncGroupMemberIdList />
<HubDbId>00000000-0000-0000-0000-000000000000</HubDbId>
<SyncGroupMemberId>00000000-0000-0000-0000-000000000000</SyncGroupMemberId>
<AgentId>f995868a-18fd-4786-875e-34996ffd5325</AgentId>
<AgentInstanceId>6fe18179-e983-4288-a660-2b9f16762603</AgentInstanceId>
<TracingId>68dfcf90-0823-4de3-87e8-79a0bc813d00</TracingId>
<DssServerId>edbf9ba4-b43f-4521-84a4-6349d490f5a8</DssServerId>
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
<SqlAzureActivityId>00000000-0000-0000-0000-000000000000</SqlAzureActivityId>
</LogInfo>
<RetentionInDays>45</RetentionInDays>
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
</CleanupTombstoneRequest>
ClientRequestHandler 4/8/2014 7:17:21 id:ClientRequestHandler_Response, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:68dfcf90-0823-4de3-87e8-79a0bc813d00,
serializedResponse:<?xml version="1.0" encoding="utf-16"?>
<CleanupTombstoneResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<State>Succeeded</State>
<LogInfo>
<DetailedProviderTraces>false</DetailedProviderTraces>
<SyncGroupId>00000000-0000-0000-0000-000000000000</SyncGroupId>
<SyncGroupMemberIdList />
<HubDbId>00000000-0000-0000-0000-000000000000</HubDbId>
<SyncGroupMemberId>00000000-0000-0000-0000-000000000000</SyncGroupMemberId>
<AgentId>f995868a-18fd-4786-875e-34996ffd5325</AgentId>
<AgentInstanceId>6fe18179-e983-4288-a660-2b9f16762603</AgentInstanceId>
<TracingId>68dfcf90-0823-4de3-87e8-79a0bc813d00</TracingId>
<DssServerId>edbf9ba4-b43f-4521-84a4-6349d490f5a8</DssServerId>
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
<SqlAzureActivityId>00000000-0000-0000-0000-000000000000</SqlAzureActivityId>
</LogInfo>
<PostActionSucceededWork xsi:nil="true" />
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
<RowsDeleted>44</RowsDeleted>
</CleanupTombstoneResponse>
CommandAndControlClient 4/8/2014 7:17:21 id:CommandAndControlClient_RequestProcessedSuccessfully, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:68dfcf90-0823-4de3-87e8-79a0bc813d00
ThreadId:24. GetRequest started.
ThreadId:19. Dispatcher calling GetRequest
DatabaseProvider 4/8/2014 7:17:27 id:DbProvider_EnumChanges_CompleteEnumForAllTables, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9,
syncGroupMemberId:87b18bc7-551f-4efe-9082-2ad47b8a99d9, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737, databaseId:e09fdb20-5f7e-4d42-be36-0dd45e541005, sqlAzureActivityId:00000000-0000-0000-0000-000000000000,
totalBatches:0
DatabaseProvider 4/8/2014 7:17:27 id:DbProvider_EnumChanges_NewBatchAvailable, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9,
syncGroupMemberId:87b18bc7-551f-4efe-9082-2ad47b8a99d9, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737, databaseId:e09fdb20-5f7e-4d42-be36-0dd45e541005, sqlAzureActivityId:00000000-0000-0000-0000-000000000000,
totalBatchesSpooled:1, batchDetails:
Version :3.1
BatchId :e361f8fb-7e39-4b4b-8efc-fa0f621d24c5
Batch Number :1
Is Last Batch :True
Data Cache Size :188661
Table Watermarks :[dbo.aspnet_Roles,360253],[dbo.aspnet_Users,360265],[dbo.aspnet_UsersInRoles,360254],[dbo.aspnet_Membership,360263],[dbo.aspnet_Profile,360248],[dbo.ShopWorkdayDetail,358002],[dbo.OclClientXFileUpload,356449],[dbo.ReportTurnoverHeader,356425],[dbo.ReportTurnoverDetail,356446],[dbo.ShopWorkdayPeriodDetail,358007],[dbo.TableMaster,360288],[dbo.Roster,360002],[dbo.TxSalesHeader,360287],[dbo.TxPayment,360279],[dbo.TxSalesDetail,360285],[dbo.TxSalesDetailLog,360275],[dbo.TxSalesHeaderLog,360280],[dbo.TxSalesHeaderRevokeLog,356022],
SyncController 4/8/2014 7:17:27 id:SyncController_BatchSpooledEvent, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603,
syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, memberDbId:e09fdb20-5f7e-4d42-be36-0dd45e541005, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, currentBatchNumber:1, totalBatchesSpooled:1, batchFileName:e361f8fb-7e39-4b4b-8efc-fa0f621d24c5.batch
BatchTransferUtil 4/8/2014 7:17:28 id:BatchTransfer_ClientInitialized, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737
BatchTransferUtil 4/8/2014 7:17:28 id:BatchTransfer_Start, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
BatchTransferUtil 4/8/2014 7:17:56 id:BatchTransfer_ClientInitialized, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737
BatchTransferUtil 4/8/2014 7:17:56 id:BatchTransfer_Start, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737
SyncController 4/8/2014 7:17:56 id:SyncController_BatchAppliedEvent, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603,
syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, memberDbId:e09fdb20-5f7e-4d42-be36-0dd45e541005, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, currentBatchNumber:1, totalBatches:1
DatabaseProvider 4/8/2014 7:17:56 id:DbProvider_MAT_AllBatchesApplied, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9,
syncGroupMemberId:87b18bc7-551f-4efe-9082-2ad47b8a99d9, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, tracingId:f4d245ad-b209-463e-8c43-4c59c7ea6737, databaseId:e09fdb20-5f7e-4d42-be36-0dd45e541005, sqlAzureActivityId:00000000-0000-0000-0000-000000000000,
madeWithKnowledge:ReplicaKeyMap: [(0:bfcb2abdd3e84634b1d944fd56a9a537) (1:d8cf66fd42b342dfaada1498d80c46a3)] ScopeRangeSet: [00:[(0:223078) (1:360289)]], madeWithForgottenKnowledge:ReplicaKeyMap: [(0:bfcb2abdd3e84634b1d944fd56a9a537) (1:d8cf66fd42b342dfaada1498d80c46a3)]
ScopeRangeSet: [00:[(0:142660)]], totalChanges:2, totalChangesApplied:2, totalChangesFailed:0, totalChangesPending:0, totalInserts:2, totalUpdates:0, totalDeletes:0
SyncController_SyncStatistics 4/8/2014 7:17:57 id:SyncController_SyncStatistics, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603,
syncGroupId:0d315093-8977-4229-8ba4-ece0fb10c3f9, memberDbId:e09fdb20-5f7e-4d42-be36-0dd45e541005, hubDbId:f8e45e70-020f-4b97-9ca8-c70e879a24a7, DownloadChangesApplied:2, DownloadChangesFailed:0, DownloadChangesTotal:2, UploadChangesApplied:757, UploadChangesFailed:0,
UploadChangesTotal:757, SyncStartTime:4/8/2014 15:17:20, SyncEndTime:4/8/2014 15:17:57
ClientRequestHandler 4/8/2014 7:17:57 id:ClientRequestHandler_Response, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737,
serializedResponse:<?xml version="1.0" encoding="utf-16"?>
<SyncResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<State>Succeeded</State>
<LogInfo>
<DetailedProviderTraces>false</DetailedProviderTraces>
<SyncGroupId>0d315093-8977-4229-8ba4-ece0fb10c3f9</SyncGroupId>
<SyncGroupMemberIdList />
<HubDbId>f8e45e70-020f-4b97-9ca8-c70e879a24a7</HubDbId>
<SyncGroupMemberId>87b18bc7-551f-4efe-9082-2ad47b8a99d9</SyncGroupMemberId>
<AgentId>f995868a-18fd-4786-875e-34996ffd5325</AgentId>
<AgentInstanceId>6fe18179-e983-4288-a660-2b9f16762603</AgentInstanceId>
<TracingId>f4d245ad-b209-463e-8c43-4c59c7ea6737</TracingId>
<DssServerId>edbf9ba4-b43f-4521-84a4-6349d490f5a8</DssServerId>
<DatabaseId>e09fdb20-5f7e-4d42-be36-0dd45e541005</DatabaseId>
<SqlAzureActivityId>00000000-0000-0000-0000-000000000000</SqlAzureActivityId>
</LogInfo>
<FailureLog />
<PostActionSucceededWork xsi:nil="true" />
<SyncGroupMemberId>87b18bc7-551f-4efe-9082-2ad47b8a99d9</SyncGroupMemberId>
<DownloadChangesTotal>2</DownloadChangesTotal>
<DownloadChangesApplied>2</DownloadChangesApplied>
<DownloadChangesFailed>0</DownloadChangesFailed>
<UploadChangesTotal>757</UploadChangesTotal>
<UploadChangesApplied>757</UploadChangesApplied>
<UploadChangesFailed>0</UploadChangesFailed>
<StartTime>2014-08-04T07:17:20.6974793Z</StartTime>
<EndTime>2014-08-04T07:17:57.6775945Z</EndTime>
<FailureType>None</FailureType>
</SyncResponse>
CommandAndControlClient 4/8/2014 7:17:57 id:CommandAndControlClient_RequestProcessedSuccessfully, rId:, sId:edbf9ba4-b43f-4521-84a4-6349d490f5a8, agentId:f995868a-18fd-4786-875e-34996ffd5325, agentInstanceId:6fe18179-e983-4288-a660-2b9f16762603, taskId:f4d245ad-b209-463e-8c43-4c59c7ea6737
ThreadId:20. GetRequest started.
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest
ThreadId:19. Dispatcher calling GetRequest -
Yet another Sync Group stuck "Processing"
I wish there was a way to fix this problem myself or to report the issue directly to someone who can reset the process, but the only way I know to fix this problem is to report it on this forum and wait until a MS engineer resets it.
So, here is the information about the sync that is stuck processing. Note that it has been in this state for more than two months! The customer was supposed to be monitoring the data, but just reported the issue to me.
Status Processing
LAST SYNC 8/4/2014 7:47:23 PM
Sync Group ID edf90bcb-51d7-4bbc-a752-c4967003ef00_East
US Location East US
Subscription Name Windows Azure MSDN - Visual Studio Ultimate
Subscription ID 310db8ca-cf81-4b46-b148-fa0345adc21e
Thanks in advance for reseting this process.
Cheers,
Melinda
~MIf it helps, this morning I found the following error message in the log:
Sync failed with the exception "An unexpected error occurred when applying batch file C:\Resources\directory\07eb40e27bc6414382cf30de457d7c69.NTierSyncServiceWorkerRole.BatchDir\DSS_3f17363d-becf-4c5e-b977-0359ec10b1df\sync_cc202f9712474dcbb5d1d864f9501f5f5b64778d5acb479e802c13d17935ad7f\e59ed526-aea2-4fec-aa23-89cad053494e.batch.
See the inner exception for more details.Inner exception: Failed to execute the command 'DeleteCommand' for table 'CTM.TM_Priority_CTM'; 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 ‘3f17363d-becf-4c5e-b977-0359ec10b1df’ to customer support.
~M -
Sync group has been keep processing for 2 days. But none of data synced.
SYNC GROUP ID
de9f1bcd-6989-4ace-a4a1-6f285d15d6a4_West US
LOCATION
West US
SUBSCRIPTION ID
c9fb0cb6-5c55-4b76-83e6-3e20e73d791dHi,
We have reset your sync group status at backend. Please check whether your sync group back to normal.
Let us know if any more question.
Regards,
Bowen -
My sync group is keep processing.
Sync group has been keep processing since 12 hrs ago. But none of data synced. I can't even stop it from control panel. Please help!!!!
SYNC GROUP ID
aa54b582-4cc7-480a-a684-1838e6c4ec36_Southeast Asia
LOCATION
Southeast Asia
SUBSCRIPTION ID
c2bb737b-7d57-49bd-9312-844f7f6d3fcbHi DanLuk,
I’m writing to follow up with you on this post. Was the problem resolved after performing our action plan steps? If yes, I’d like to mark this issue as "Answered". Please also feel free to unmark the issue, with any new findings or concerns you may have.
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support -
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 YungAs 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 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 YungHi 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 -
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 YungHi 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 -
My sync group is stuck in the processing state
The database sync that we have configured has been working for months and suddenly stopped successfully running 1/19/2015 2:19 PM Pacific Time. We have the sync configured to automatically execute every 5 mins and I even tried to run it manually. The job
stays perpetually in a "Processing" state with no additional info (e.g. error, warning, etc).
Can anyone provide assistance? (e.g. reset the sync status, provide detailed logging as to the cause of the issues) What is the proper course of action? (e.g. reconfigure the sync service, etc) Please advise.
Here are the technical details of the instance:
STATUS
Processing
LAST SYNC
1/19/2015 2:19:25 PM
SYNC GROUP ID
e5c228ff-a8e8-4b99-85f8-504709e22908_West US
SUBSCRIPTION ID
4caa7e07-76e5-424d-8b4b-6f26cce36026
CONFLICT RESOLUTION
Hub WinsHi,
Thanks for posting here.
Any of the following can result in a sync group being stuck in the processing state.
a)The client agent is offline.
Be sure that the client agent is online then try again.
b)The client agent is uninstalled or missing.
Please check the above and try to sync again.
In the mean time we would check from our back-end. It may take more time than expected.
Girish Prajwal -
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
Maybe you are looking for
-
My iphone says it has been backed up but whenever i need to restore my phone i lose everything
I backed up my iphone 4 and itunes said it had backed up. my phone froze later on and i ended up having to reset it, and i lost everything i went to restore my phone and only the second time i restored it i got only my contancts and apps back my vid
-
I am looking for a device that converts Component video and RCA audio to Firewire, so that a movie can be imported into iMovie. I am currently using a Canopus ADVC110 for S-Video but have an HD source with component video and would like to be able to
-
What's a good voice recording app I can use on my laptop and interface with iTunes?
Does anyone have a great recommendation for making home-made voice recordings that I can post on social media using iTunes? Is there a particular app/recorder that makes it sound more professional than a home-made job? Thanks.
-
Xcelsius (SWFfile) performance after exporting to Business objects platform
Hello, I am facing a problem wherein the SWF file takes time (almost 1-2min) to load the refreshed data in Infoview portal i.e. after exporting the xlf file to Business Objects platform. Following are the system details: 1) Business Objects XI Releas
-
Aren't Safari bookmarks supposed to sync between computers?
I think that Safari bookmarks are suppose to be the same across all of one's computers running the same OS. But that is not the case between my iMac running OS X Mountain Lion and my MacBook Pro running OS X Mountain Lion. Any help?