SQL Azure Sync Agent

Hi,
Anyone can share on the network port and IP address requirement for the SQL Database sync?

1433 is between the Data Sync Agent and your SQL Server. 443 is bidirectional for Data Sync Agent to connect to Azure Data Sync Service.
the Data Sync Service itself do not connect to your on-premise SQL Server directly. Neither does the Data Sync Agent connect to the Azure SQL Database Correctly.
to illustrate
on-premise SQL <-> Data Sync Agent <-> Azure Data Sync Service <-> Azure SQL Database

Similar Messages

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

SQL Azure sync service-- absurdly slow and fails after a few days

Hello. We have been trying to use Azure Data Sync to replicate an on-premise MSSQL database to an SQL Azure database for read-only access by a customer. This was working for a while, but stopped syncing after a couple months(12hr auto-sync schedule) with
no errors in the log. I had to re-create the sync group, but now it takes even longer than originally to try to sync, and never actually completes, as it gets interrupted by bi-weekly server restarts... It used to take a few hours to sync the new data in our
database(which is appended to daily)-- but this time it fails after 4+ days... It was unacceptably slow initially(IMO), but now it's clearly unusable. The original initialization of the data when I first set it up was less than 2 days of syncing.
It seems there is a throttle on the Azure sync service. Is this true? Would it be best to clear the SQL Azure database now and re-sync? Is there a way to pre-load the SQL Azure database with MSSQL on-premise data via a SQL backup file or something?
Please advise. Thank you.

when you re-created the sync group, does the member databases/hub database have pre-existing data?
when synching a sync group for the first time, make sure databases don't contain the same set of data, otherwise, you will run into conflicts which will completely slow down your sync...
I deleted the initial sync group because it wasn't syncing(auto or on-demand), nor creating a log entry with an error indicating why.
So, I simply deleted the sync group and re-created it with the same exact databases and settings. I did not delete all data in the SQL Azure database-- I was under the assumption that the sync service, with the tracking tables were smart enough to not get
confused with pre-existing data, but apparently that's not how this works?
I obviously can't delete the data in the source database(MSSQL on-premise), but I could delete the tables in the SQL Azure database if that's supposed to fix the problem-- then we'll just have to wait multiple days for it to be completely re-initialized,
hopefully without error... Is there a way to seed the data in some way to prevent this extremely log first sync?
Thank you for your help.

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 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.

SQL SYNC AGENT is not

Hi,
I am having below error in SQL DATA SYNC AGENT. please do transfer if i left the message in wrong room.
"Connection to Microsoft SQL DATA Sync windows service timed out. Please unsure that micosoft data sync windows services
is running and restart local sync agent "
I have already restarted local sync agent.i checked the sql data sync winodws service is running in local services .
Please advice?
Superman

Hi,
Could you please check whether there are any error logs through the Event Viewer? Under the category "Applications and Service Logs" -> "SQL Data Sync".
Regards,
Bowen

SQL Data Sync - error during sync. Unable to diagnose the problem.

I have 2 SQL data sync groups setup
First one does a 1 way sync from azure to local db. Sync's only 1 table.
Second one does a 1 way sync from local db to the azure. Syncs 2 tables.
After setting it up and getting a few sync errors I was able to figure out what's wrong by checking the logs and fixing the problems. It was all running fine for a while and now it broke down.
I got a sync error every time sync is attempted - however this time I'm not able to fix anything because I don't have any visibility on what's wrong - when I click on the Log tab in the Azure Management portal it just stays blank - no details come up.
I click [Logs] Wait spinner comes up
And then it looks like this:
Another detail worth mentioning is that the error only occurs for the Second sync group that I have.
Here's what I've attempted so far
I poked around the azure management portal to try to find another way of looking at the logs - looking for something like ftp access to the log file - couldn't find anything like that.
I refreshed schema in the sync rules tab.
Used the SQL Data Sync agent tool on the premise to do the ping operation. Restarted the sql data sync windows service.
Made sure I have the latest SQL Data Sync Agent installed.
I'm wondering what are my options from here...
I'm close to trying to deleting and recreating the sync group... I'm not too comfortable doing this because I know there are some sql tables that get created in the local db to support the operation of the sync - so if I delete the sync group would that automatically
drop those helper tables as well or would I have to drop those manually - If I do drop those then that will obviously brake the other sync group that works fin as well..
Any advice is appreciated. Thanks

hi,
According to your description, it seems the issue is related to SQL Azure, I will move this thread to SQL Azure Discussions forums to get a better support.
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

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

Azure SQL Data Sync, LINQ optimization bug

How can I report the following Bug ?
var empty = new Set<int>();
var query = storage.table.Where(item => empty.Contains(item.id));
// Entity Framework Extended
query.DeleteAsync()
The query is optimized to something like this, because the set is empty, and therefore the result set is always empty:
SELECT
CAST(NULL AS uniqueidentifier) AS [C1],
CAST(NULL AS uniqueidentifier) AS [C2],
CAST(NULL AS int) AS [C3],
CAST(NULL AS int) AS [C4],
CAST(NULL AS datetime2) AS [C5],
CAST(NULL AS varchar(1)) AS [C6],
CAST(NULL AS int) AS [C7]
FROM ( SELECT 1 AS X ) AS [SingleRowTable1]
WHERE 1 = 0
Now the problem is that update and delete trigger, introduced by Azure SQL Data Sync, will fail because they require the primary key, which is not part of the optimized query. Meaning that when the set is empty the triggers will fail, but if the set contains
an id, the query is not optimized and therefore will succeed.
(SELECT [i].[PrimaryKeyId] FROM DELETED AS [i])
Notice, the problem here is not Entity Framework Extended from my perspective, but the Azure SQL Data Sync Triggers!

not sure if i understood your post correctly, but the columns available in the logical inserted and deleted tables available in the trigger are the actual columns of the table itself, not the columns in the query that caused the trigger to fire.

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

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

Azure Sync not saving access key in web portal

Azure Sync not saving access key in web portal.
You generate a new key, then press Ok and the key cannot be used and does not display again.
Could someone please have a look at this?

Hello,
After generate a new key on the Manage Access key page, you can click the clipboard symbol to copy the key to your clipboard, and then paste the key from your clipboard on the SQL Data Sync Client Agent.
Reference:http://msdn.microsoft.com/en-us/library/windowsazure/jj823137.aspx
If I have any misunderstadning, please post more details information or a screen shot about the issue.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

How do I delete a sync agent?

I am trying to clean up my Azure environment. I have a bunch of Sync Agents that are no longer being utilized, but each time I select one to attempt to delete, I get an error that states "The Sync Agent was not deleted",
without giving me any specifics.
Does anyone know how I can go about deleting Sync Agents that are no longer in use?
Thanks

Hi,
1. Local Agent cannot be deleted if its associated on-Premise database is unreachable
Description/Symptoms : If a local end point (database) that is registered with a local SQL Azure Data Sync
agent becomes unreachable, the local agent cannot be deleted.
Cause : The local agent cannot be deleted because the unreachable database is still
registered with the agent and when you try to delete the agent, the deletion
process tries to reach the database, which fails. This database cannot be
unregistered too, because during unregistration process, local agent tries to
connect to database which cannot be reachable.
Resolution/Workaround : Create a local database with the same name as the one that cannot be reached,
unregister this database from local agent, and then proceed to delete the agent.
2. Sync Group cannot be deleted within 3 minutes of uninstalling/stopping the agent Description/Symptoms
You are not able to delete a sync group with in 3 minutes of uninstalling/stopping the associated local SQL Azure Data Sync agent.
Resolution/Workaround : Remove a sync group with associated sync agents online (strongly recommended).
If agent is offline but installed, bring it online on the on-premise computer, wait for the status of the agent as online in Azure portal, and then remove the sync group.
If agent is offline because it was uninstalled, perform the following steps and try deleting the sync group.
-Remove agent XML file from the SQL Azure Data Sync installation folder if the file exists
-Install the agent on same/another on-premise machine, submit agent key from portal generated for the agent that’s showing offline
3. cannot delete my sync group
Description/Symptoms : You fail in your attempt to delete a sync group.
Cause/Fix : Any of the following can result in a failure to delete a sync group.
The agent is offline : Be sure that the agent is online then try again.
The Data Sync service is stopped :
* In the Start menu search on Services
* Click Services in the Programs section of the search results.
* Find the SQL Azure Data Sync Preview service.
* If the service status is Stopped right-click the service name and select Start from the dropdown menu.
A database is offline : Check your SQL Azure and SQL Server databases to be sure they are all online.
The sync group is provisioning or synchronizing : Wait until the provisioning or synchronizing process finishes then retry deleting the sync group.
Hope this helps.
Regards,
Shirisha Paderu

Azure sync processing but nothing happend

Since Jan 16 my sync is saying that is processing and when I check the log is saying that has processed a lot of rows but when I check the data nothing has sync between my on premise and Azure. Below the information and the log:
STATUS
Processing
LAST SYNC
1/16/2015 10:23:03 AM
SYNC GROUP ID
1630394a-3db2-4028-9cae-5ac32cc5b329_East US
LOCATION
East US
SUBSCRIPTION NAME
Pay-As-You-Go
SUBSCRIPTION ID
399ba2d3-f357-4c7b-a52e-972bcb3cc2d7
CONFLICT RESOLUTION
Client Wins
3074 rows have been processed in 900 seconds. For more information, provide tracing ID ‘a58fec2c-49ae-409a-be90-2ecdd0eee687’ to customer support.
31829 rows have been processed in 8101 seconds. For more information, provide tracing ID ‘153badc7-6ffb-4df0-9cb7-cfd49d919484’ to customer support.

Hi,
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.
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
Girish Prajwal

SQL Server 2012 Deploy Database to SQL Azure...

I have spent many days trying to copy a simple test database from my PC to SQL Azure but with little success. Then I installed SQL Server 2012 and see a new task:
Deploy Database to SQL Azure... It looks like an automated extraction to DAC and then creating the Azure database all in one step.
I was elated, but got hit with the following three types of errors.
One or more unsupported elements were found in the schema used as part of a data package.
Error SQL71564: The element Extended Property: [dbo].[Accounts].[Address].[MS_Description] is not supported when used as part of a data package (bacpac).
Error SQL71564: Table Table: [dbo].[Activities] does not have a clustered index. Clustered indexes are required for inserting data in this version of SQL Server.
Error SQL71564: Element User: [NT AUTHORITY\NETWORK SERVICE] has an unsupported property AuthenticationType set and is not supported when used as part of a data package.
(Microsoft.SqlServer.Dac)
May I know what I can do on the on-premise database to rid of the first and third error?
Thanks.

Hello,
1) Remove the Extended Property from the (?) column Address in table Accounts.
BTW, for small databases it's sometimes easiere to generate a script for the database (and modify it slightly) instead of using the Wizard
Olaf Helper
Blog
Xing
What is Extended Property? What is this .MS_Description? I can't see it in the table designer or the Column Properties. (I don't know whether this was corruption caused by Data Sync I used earlier.) How do I remove it.
Of all the methods of copying SQL Server to Azure SQL, this one gives the least mistakes. If I can solve this Extended Properties thing hopefully I can migrate the database over.

SQL Azure Sync Agent

Similar Messages

Maybe you are looking for