9

I tried to export Sql Database in azure to storage blob but the operation failed. I do this task daily last month and this issue is new. It shows as follows :

Error encountered during the service operation.Blob https://blob link/dbname-2019-1-16-14-24.bacpac is not writeable. The remote server returned an error: (403) Forbidden.The remote server returned an error: (403) Forbidden.

4
  • Do you check your SHARED ACCESS SIGNATURE? if it's expired, then will deny the access. Commented Jan 16, 2019 at 9:42
  • 3
    This is happening with our sub too. Looks like an Azure internal error. Commented Jan 16, 2019 at 20:08
  • @ZairHenrique Same thing here. Can't export a db since yesterday... will try again tomorrow. Commented Jan 17, 2019 at 14:52
  • Fyi, pinged Azure support about this, they are investigating. twitter.com/AzureSupport/status/1085920629604474881 Commented Jan 17, 2019 at 15:25

4 Answers 4

4

I had the same problem. I have contacted Azure support and this is their response.

We recently identified a regression in the import/export service that is generating incorrect SAS tokens to the storage accounts.

The engineering team has rolled out the fix, but it might take some time for the fix to get applied worldwide.

Please try the following link to access Azure portal and then perform the export operations:

https://portal.azure.com/?feature.canmodifystamps=true&microsoft_azure_storage=stage1

The portal shows an orange title bar if you open it via the above link, this is expected.

So, it should be already fixed by now.

Sign up to request clarification or add additional context in comments.

3 Comments

It seems to be working fine again today. likely an azure internal issue
The bug is not fix! I can backup the db only through your link!
@Evilripper the bugfix is probably still rolling out. I am happy that the link worked for you!
0

If you're using sql scripts for back up following this link, then I suspect that the expired date of SHARED ACCESS SIGNATURE is reached.

Please re-generate SHARED ACCESS SIGNATURE, and then use the new key for backup.

Please let me know if any more issues.

2 Comments

Hi Ivan, I am not using sql scripts. I only use azure portal export option
I also uses the same blob account to upload files from application and it's working fine. Only issue is when exporting db from azure portal
0

Make sure a firewall rule does not exist. Please go to the Azure portal "Storage Accounts → "YourStorageAccountName" → Firewalls and Virtual Networks (left vertical panel). Put it to "Allow access" from "All networks". You can also configure the storage account with exceptions for trusted Microsoft services as explained here.

1 Comment

It's already set to Allow access from all networks but not working
0

In my case, I had Delete Lock on the resource group where storage was and every attempt to export one DB to that storage ended up with the error:

Failed to export the database: my_DB. ErrorCode: undefined ErrorMessage: undefined

Export of another DB on the same server was no problem. After deleting the Lock, the export started to work. I have no idea why it was like that, even though for a few years, everything was working with the Delete lock on RG.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.