I had issues trying to re-provision an on-premise database. After the re-provisioning succeeded, I am now getting the following error:
Sync failed with the exception "Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
Inner exception: The remote server returned an error: (403) Forbidden.
For more information, provide tracing id ‘0d0121e0-6407-4d64-a74b-c823f7eaed3d’ to customer support.
Sync Group Id: 8ded819b-8456-4a4a-bcba-995dbf58b639
Server Id: e4e38c20-9487-435f-94ae-1ded32731eaa
Region: Wes Europe
Trace output: http://sdrv.ms/P03BtM
I also ran a trace on the agent server it seems that there seems to be an issue uploading data to cloud storage.
Any ideas on what can be wrong? Only answers I saw was on time settings etc.
Sync failed with the exception "Server failed to authenticate the request.
Make sure the value of Authorization header is formed correctly including the signature.
The remote server returned an error: (403) Forbidden.
For more information, provide tracing id ‘537b28ad-619c-48c8-a679-67ec6ccee748’ to customer support.
This happens while syncing a table with about 200k records from on-premise to the cloud.
I was trying to collect the data you suggest, but failed to find the Agent Log or a way to enable logging.
The cloud log does not provide the information you request (id:SyncController_BatchSpooledEvent) and the local log folder (C:\Program Files (x86)\Microsoft SQL Data Sync\logs) is empty.
The version of the SQL Data Sync Agent is 188.8.131.52 and should be the most recent one.
EDIT: Some more detail
The amount of data that should be synced is about 11Mb. After starting a sync process, on our firewall we see an upload of roughly this amount of data. It seems as if the error occurs immediately after the upload process. It takes aproximately 3-4 minutes
to upload 11Mb of data with our ADSL connection.
NB: If we reduce the amount of data (say 200 records instead of 200k) the sync process completes successfully!
Edited byoaksboardFriday, September 21, 2012 9:17 AMadditional information
From the log, we found out that your agent spent about 10 mins to continuously upload data to storage blob with no response until uploading failed finally with blob access key expired. We are still working with storage team
to figure out the root cause while the issue might also be related to your machine network environment.
One thing you can further try is to reboot your machine and see whether the issue continues to happen.
Also to mention that, SQL Data Sync product team is currently in holiday until the end of this week.
We will go back to you ASAP when we get more clear after the holiday.
we did the tests from two different machines to two different azure subscriptions with the exact same error. We already did restart the machines multiple times. Both machines are in the same network infrastructure and our upload capacity is limited to 512kbit/s.
In some previous test the elapsed time until the error occured was around 3 to 4 minutes. Monitoring network traffic it seems that the whole data (~ 11 Mb) is uploaded. The error occurs immediately after the upload process has finished.
I check the process monitor log you provided, the upload speed is about 300kbit/s. The upload failed because it's not finished within the connection lifetime. So I would suggest you install the SQL Data Sync Agent on a machine with faster network connection.
If it still keep failling, we will further investigation this. Sorry for the issue.
I did not respond earlier to your post because we were hoping that the new Data Sync Agent may solve the problem. This was not the case.
Coming back to your reply: does that mean, that if you have to sync large amounts of data it depends on the network speed, if the sync will be successful or not? Is SQL Data Sync only suitable for small amounts of data? I cannot belive that this is the case.
What is the connection lifetime? Is there an initial sync option to upload all the data? Or is there a manual way to upload the data. Our problem seems to be the first sync of the table with aprox. 300000 records. Subsequent sync operations would never be
We could try with a faster network connection, but as we are developing a solution for our customers, and their network connection at best is on par with our test environment, we have to make sure SQL Sync will work on slow connections, too.
Edited byoaksboardTuesday, November 13, 2012 10:07 AMadditional information
I did some additional testing and found out something interesting:
I deleted all 300000 records from the table that is causing the sync issues with "DELETE FROM TABLE". Doing so did not delete the corrisponding records from the "DataSync.TABLE_dss_tracking" table. I know this is not a recommended way of doing things, but
it brought me one step forward:
Sync still did upload for ~10 minutes and then quit with the "server failed to authenticate" error (but now we are without data to sync).
This seems to be because of the DataSync.TABLE_dss_tracking still containing the "sync timestamp" of the 300000 records.
As if Data Sync was trying to upload the whole 300000 DataSync timestamps/records and reaching the timeout limit in doing so (due to our limited upload bandwidth). When this happens, Sync gives back the "server failed to authenticate" error (maybe because
a timeout syncing the sync-tables isn't supposed to happen?).
We have to make sure, SQL Data Sync will work on slower network connections, too, because as I said before, our customers do not have fast internet. Most of them are on 4Mbit/256kbit/s ADSL lines.
Thanks for the feedback oaksboard. We are keep improving the SQL Data Sync to provider better experience for our customer.
Per your questions:
SQL Data Sync can support very large data set. There's customer who use it to sync tens of GB data. Manually upload data and other options to help accelerate the init sync are all in our plan. But currently, we do not have timeline when this will
For the slow network, we have done some change in current developing service update which should be helpful to address this issue. It's not in the latest local agent you had upgraded but will be coming in the near future. For the network speed SQL Data
Sync need to support, we are still in planning phase, so your feedback is quite important for us. Really appreciate.