SQL SERVER – FIX: Backup to URL Error: Operating System Error 50(The Request is Not Supported.)

It is always fun to work with “Backup to URL” feature of SQL Server. The error messages which are raised are from Azure storage side and an SQLDBA won’t be able to understand the meaning. While I was working with my VM to learn something about Backup to URL feature, I realized that my backups were failing. In this blog, let us learn how to fix the back to URL error: Operating system error 50(The request is not supported.). Here are the exact messages which I was getting in ERRORLOG.

2018-08-17 00:58:22.85 spid125 Error: 18204, Severity: 16, State: 1.
2018-08-17 00:58:22.85 spid125 BackupDiskFile::CreateMedia: Backup device ‘https://sqlauthbackup.blob.core.windows.net/backupcontainer/sqlauthdb_ebd0fe66f91f43f199c3b52d803bb136_20180814005822-07.log’ failed to create. Operating system error 50(The request is not supported.).
2018-08-17 00:58:22.85 Backup Error: 3041, Severity: 16, State: 1.
2018-08-17 00:58:22.85 Backup BACKUP failed to complete the command BACKUP LOG sqlauthdb. Check the backup application log for detailed messages.

I have already blogged about the same error earlier where the cause was different.

SQL SERVER – Backup to URL error: Operating system error 50(The request is not supported.)

In the current situation, this was the managed backup which was configured using the Azure portal. Recently I generated a new SAS token and updated it in the credential. Since then it was failing with an error.

WORKAROUND/SOLUTION

I actually performed to update the new SAS token by copying/pasting the value in the SSMS (below UI)

It didn’t take much time to realize that I missed removing “?” symbol from the SAS token. The SAS token on the portal starts from “?sv” and while creating a credential, we need to remove “?” and start the value from “sv”

I have done the same in the script which is available on my earlier blog.

SQL SERVER – Backup to URL – Script to Generate Credential and Backup using Shared Access Signature (SAS)

Have you encountered a similar error and found some other cause? Please share via the comment section.

Reference: Pinal Dave (https://blog.SQLAuthority.com)