Registering Database with Microsoft SQL Azure Data Sync Agent Preview

Question

I've already installed the Data Sync Agent but when it comes down to registering the Database, I'm unable to do so. Am I putting the wrong server name and/or database? Is there something I'm missing? I would appreciate any help you guys can give me. Thank you.

Answer 1

it would help if you can post what error  you are getting...

please note that the Data Sync Agent is for registering on-premise databases only. SQL Azure databases are registered in the portal.

Answer 2

Yeah I know that the Data Sync Agent is for registering on-premises databases only. For some reason I'm unable to register the SQL Server Database I have here on my laptop. When I click "register" on the upper left hand corner of the data sync software, a "SQL Server Configuration" window pops up and that's what I"m having the issue with. I'm putting in the credentials but apparently it's not working. I'm unsure if I'm placing the correct credentials. Are you able to assist me with this?

Answer 3

are you able to connect to your on-premise sql server using SQL Management Studio and using the same credentials? 

Answer 4

For some strange reason, I'm unable to install it on my computer. It usually freezes during the installation process and an error occurs. Also, the Data Sync Agent has stopped working as well and I'm unsure what to do. I wish someone could control my computer via logmein and do this for me

Answer 5

Answer 6

Can you go to Control Panel and check whether SQLAzure Data Sync Windows Service is started successfully there? If not, could you double check the service startup account and try with administrator account as startup account, to see whether the service can be started successfully?

---

Oliver Yao - MSFT

Answer 7

Okay thanks! I got it up and running now but apparently I need to use the SQL Management Studio to locate my SQL Server and stuff like that. There are too many processes. Can anyone help out a little with this issue?

Answer 8

I did not get understood well the exact issue you are trying to report. are you saying you are able to use SQL Management Sutido to connect into the SQL Server, but not able to use Data Sync Agent UI to register that database with same user name and password? If that is the case, how did you make it work at the end?

---

Oliver Yao - MSFT

Answer 9

I had to use .\Owner as the username in order for it to work. Now the only issue I'm having is getting the provisioning portion of the syncing to work. I usually get provisioning failed when trying to sync the On-Premises database.

Answer 10

Can you paste the full error message you saw from the Logviewer about the provision? And can you tell the data center name where your sync group is created, WA Subscription ID and Sync Server ID?

---

Oliver Yao - MSFT

Answer 11

I'm not too familiar with this so may you please tell me exactly where I can go to find this information? It would be a big help

Answer 12

Database provisioning failed with the exception "SqlException Error Code: -2146232060 - SqlError Number:271, Message: The column "Duration" cannot be modified because it is either a computed column or is the result of a UNION operator. 
"

For more information, provide tracing id ‘aa280e60-1497-44fb-9dd4-1b9fc1b6d196’ to customer support.

Answer 13

It seems that Duration column is a computed column which is a known issue, please check Data Sync Known Issue.

---

Alex Feng | MCTS: SQL Server 2008, Implementation and Maintenance

Answer 14

Hi,

I have problem registering my Azure Data Sync Agent on my on-premise server running: Windows Server 2008 R2 Enterprise x86, Microsoft SQL Server 2008 R2 and Azure Data Sync Agent Preview. I get the message below.

------------------------
Connection failed. Please check database credentials along with permissions for Local Sync Service logon account to connect to database with specified credentials.

Other reasons for failure:

SQL Azure databases have to be added on the Azure Sync Service portal.
SQL Server databases lower than SQL Server 2005 SP2 are not supported on the Azure Sync Service.
---------------------------

1. I can connect to my on-premise sql server database with same specified credentials (SQL and Windows authentication) but can not connect in Azure Data Sync Agent. I tried both authentication - SQL & Windows but same message.

2. I already submit agent key and Ping sync service is also successfully pinged, so Agent is configured successfully.

3. As per above message my database is also higher then SQL Server 2005 SP2 so this is not happen in my case.

SO PLEASE HELP ME TO SOLVE THIS ISSUE.

Answer 15

Hi,

I have problem registering my Azure Data Sync Agent on my on-premise server running: Windows Server 2008 R2 Enterprise x86, Microsoft SQL Server 2008 R2 and Azure Data Sync Agent Preview. I get the message below.

------------------------
Connection failed. Please check database credentials along with permissions for Local Sync Service logon account to connect to database with specified credentials.

Other reasons for failure:

SQL Azure databases have to be added on the Azure Sync Service portal.
SQL Server databases lower than SQL Server 2005 SP2 are not supported on the Azure Sync Service.
---------------------------

1. I can connect to my on-premise sql server database with same specified credentials (SQL and Windows authentication) but can not connect in Azure Data Sync Agent. I tried both authentication - SQL & Windows but same message.

2. I already submit agent key and Ping sync service is also successfully pinged, so Agent is configured successfully.

3. As per above message my database is also higher then SQL Server 2005 SP2 so this is not happen in my case.

SO PLEASE HELP ME TO SOLVE THIS ISSUE.

Answer 16

Hari Das,

  Couple of questions:

1) Is the agent installed on a remote machine, i.e. a different machine that the SQL Server machine?

2) When you successfully connected to the SQL Server in question, were you connected to it remotely via SSMS?

Answering those questions will help to tackle your issue.  You need to ensure the the SQL Server is allowed to be connected remotely.  In addition, please also ensure that there isn't any other firewall policy set locally to prevent the Agent to handshake with the SQL Server in question.

 

Answer 17

Hi,

I actually have the same problem as Hari Das.

Im using a virtual maschine within Windows Azure where SQL Server 2012 is installed on
(SQL Server 2012 SP1 Standard on Windows Server 2008 R2 SP1).

I already enabled remote connection (as described here: http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx

and server authentication for SQL Sever credentials and Windows account.

Is there anything else I can do to solve this issue?