J
Jose_Manuel_Jurado
Today, I worked on a service request that our customer got the following error message: Cannot open backup device 'https://XXX.blob.core.windows.net/NNN/YYY.bak'. Operating system error 86(The specified network password is not correct.). RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3201). Following I would like to share with you some details why this issue and the activities done to resolve it.
The Core Issue: Error 3201
Error 3201 essentially signifies that SQL Server is facing challenges accessing the backup device or file specified during a backup or restore operation.
Diving Deeper: "Operating system error 86"
This error explicitly states: "The specified network password is not correct." When we're dealing with Azure Blob Storage as the backup destination, this "network password" can often be a reference to the Shared Access Signature (SAS) token used for authentication.
Common Triggers and Solutions
Conclusion
Error 3201, combined with "Operating system error 86," points to challenges in Azure SQL Managed Instance accessing backup devices in Azure Blob Storage, often due to incorrect SAS tokens or network barriers. In this case, we found the firewall/network/UDR configuration prevents the access from Azure SQL Managed Instance to Azure Blob Storage causing this problem.
Continue reading...
The Core Issue: Error 3201
Error 3201 essentially signifies that SQL Server is facing challenges accessing the backup device or file specified during a backup or restore operation.
Diving Deeper: "Operating system error 86"
This error explicitly states: "The specified network password is not correct." When we're dealing with Azure Blob Storage as the backup destination, this "network password" can often be a reference to the Shared Access Signature (SAS) token used for authentication.
Common Triggers and Solutions
Incorrect SAS Token: Azure Blob Storage uses SAS tokens to grant limited access to its objects. If this token is either wrong or expired, an authentication error like "Operating system error 86" will manifest. Ensure that the SAS token is correctly generated and still valid. Also, you could receive message with "Access Denied"
Network Configuration Issues (Firewall): Network barriers like firewalls can block Azure SQL Managed Instance from reaching Azure Blob Storage. Ensure that there are appropriate rules allowing traffic between your Azure SQL Managed Instance and Azure Blob Storage.
Azure SQL Managed Instance and Azure Blob Storage Communication: When using Azure SQL Managed Instance, ensure that you have set up the necessary networking components, like Virtual Network (VNet) peering or VNet service endpoints, to allow smooth communication with Azure Blob Storage.
File Path or Backup Device Misconfiguration: This can be a straightforward issue where the specified file path is incorrect or the backup device has issues. Double-check the path and the device's status.
Conclusion
Error 3201, combined with "Operating system error 86," points to challenges in Azure SQL Managed Instance accessing backup devices in Azure Blob Storage, often due to incorrect SAS tokens or network barriers. In this case, we found the firewall/network/UDR configuration prevents the access from Azure SQL Managed Instance to Azure Blob Storage causing this problem.
Continue reading...