I am Unable to install MS SQL Azure Data Sync (Preview).
I have Win 7 Ultimate - I am logged in with Administrator account.
During Installation it asks for User ID with proper network access - so I tried this admin account by entering its ID and pwd and also tried by left the text boxes blank - but it failed. I then also created another User ID on my machine made it Admin and also give it various privileges by NTRights utility (http://support.microsoft.com/kb/315276) and by GPEdit - (we do not have Domain but workgroup) - And it still fails.
I got this error message:
Service 'SQL Azure Data Sync Preview' could not be installed. Verify that you have sufficient privileges to install system services.
And when I did not type any ID - I got this error message:
failed to grant 'logont as service' rights to user -2147023564 account with network access
Checkout the troubleshooting section here.
SDE, Sync Framework - http://www.giyer.com
- Proposed as answer by GaneshanMicrosoft employee Monday, October 17, 2011 4:31 PM
Thanks for the quick response, I tried but with same errors - and tried 3 ways to install - all fail.
-entering Admin ID during installation (Running setup as admin)
-entering another Admin ID (with lot of other privileges) during installation (Running setup as admin)
-enter no ID during installation (Running setup as admin)
Are you installing as Local Administrator or Domain Administrator ?
If you are installing as Local Administrator, you have to specify the username as .\Administrator
Hope this helps !!!
Arunraj Chandrasekaran, MCTS, Author: SQLXpertise.com
If you found this post useful, Please "Mark as Answer" or "Vote as Helpful"
As Arunraj suggested, try using the local administrator as .\Administrator or I would recommend using the domain account which has sufficient Privileges to install local agent.
You can also enable detailed logging for local agent to see more information.
Open LocalAgentHost.exe.config in notepad. This file should be present in your installation directory.
a) Uncomment the section that is currently commented
<add name="SyncAgentTracer" value="4" />
<trace autoflush="true" indentsize="4">
<add name="myListener" type="Microsoft.SqlAzureDataSync.ClientLogging.DSSClientTraceListener, Microsoft.SqlAzureDataSync.ClientLogging, Version=188.8.131.52" initializeData="DSSAgentOutput.log" />
<remove name="Default" />
b) Stop and restart SQL Azure Data Sync Preview Windows Service.
Now you would find the detailed logs in files named DSSAgentOutput*.log. Logs in this file are more detailed than log entries in the Event Viewer.
- Proposed as answer by Praveen M [MSFT]Microsoft employee Monday, October 17, 2011 7:59 PM
had the same problem.
if its a local user account you're entering in the User Id, try using MACHINENAME\UserName format (e.g., MyPC\AdminUser)
That turned out to be my problem as well. The installer claims that you can use "DOMAIN\domainuser" or ".\localuser", but for the local user case it fails unless you specify "MACHINENAME\localuser".
I would have filed a bug report on Connect, but SQL Azure Data Sync is not listed there yet from what I could find.
they're already aware of this issue and is tracking it already.
Sql Azure Data Sync is in Sql Server's connect site.
To log a bug in this release, use the following steps:
- Navigate to https://connect.microsoft.com/SQLServer/Feedback.
- You will be prompted to search our existing feedback to verify your issue has not already been submitted.
- Once you verify that your issue has not been submitted, scroll down the page and click on the orange Submit Feedback button in the left-hand navigation bar.
- On the Select Feedback form, click SQL Server Bug Form.
- On the bug form, select Version = SQL Azure Data Sync Preview
- On the bug form, select Category = SQL Azure Data Sync
- Complete your request.
- Click Submit to send the form to Microsoft.
.\userId causes the agent install to fail.
See the warning below figure 10 at http://social.technet.microsoft.com/wiki/contents/articles/5018.aspx#NewAgent - it describes the problem and solution.
I had exactly this problem. It turned out that my machine name was longer than 15 characters (Nicks-Big-Laptop\DataSynUser).
When I used 'Nicks-Big-Lapto\DataSyncUser' it all worked.
By that stage I had already granted 'LogOnAsService' rights to that account, but the installer should do that for you if you haven't.