2
votes

I have a sql azure web app with a connected database. When I try to automate a daily backup of my web app including the database I get the following error:

'login failed for user ******'

The asp.net web app is connecting and getting data from the database without error. This error only happens during the web app backup process.

I have checked the connection string in both the web app PROPERTIES and the DATA CONNECTIONS blades.

The connection strings are the same in both blades and look like:

Server=tcp:****.database.windows.net,1433;Database=****;User ID=****;Password=****;Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;

If I open SSMS and use the server, password, and user from my connection string I can connect without any issue.

Also, when I got to the Blade for the database in question and click on the activity log, I get no entries and don't see any connection errors

Can someone help me figure out why my azure web app cannot backup the database during its backup operation


EDIT 1:

The activity log linked to an error log file and this is what it contained

<Error>
<Code>AuthenticationFailed</Code>
<Message>
Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. RequestId:f85ceeef-0001-00de-1a27-6cbdab000000 Time:2017-01-11T16:26:09.4122657Z
</Message>
<AuthenticationErrorDetail>
Signature did not match. String to sign used was rwdl 2017-01-08T16:16:47Z 2290-10-23T15:16:47Z /blob/******/$root 2015-04-05
</AuthenticationErrorDetail>
</Error>
2
paste the entire error - TheGameiswar
that is the entire error, it is found through looking at the activity log for the web service. Is there another place I can go to get a more detailed error? - J King
@TheGameiswar I found a link to a "log/error" file and added the contents to my post above - J King

2 Answers

2
votes

I hate these kind of answers,

but after getting no help from microsoft RANT BEGIN other than googling my question and returning stack exchange answers to me then suggesting I open a support ticket - which of course is a paid feature... RANT END

SOLUTION My best guess is that there was an issue with the backup configuration because I deleted the existing backup configuration and recreated it with the same values and now it works. Maybe I should have created the Blob container before rather than during the backup setup. I don't know but it is working now.

0
votes

Did you verify that Azure resources are whitelisted in your Azure SQL Server firewall settings?