Comments
3 comments
-
On the machine where the SQL Server instance is running, open the folder where SQL Backup is installed e.g.
C:\Program Files (x86)\Red Gate\SQL Backup 10\<instance name>\
Open the file named log4backup.config. Change the restrictedToMinimumLevel setting to debug.
Now open a command prompt window and navigate to the same folder. Run the following:
sqbhostedstorageclient.exe authorize --instance <SQL Server instance name> --azure "<Azure account name>" "<Azure access key>" "<blob container name>"
replacing <SQL Server instance name>, <Azure account name>, <Azure access key>, and <blob container name> with your values.
Run the command, and a detailed log will be generated in the C:\ProgramData\Red Gate\Logs\SQL Backup 10\ folder. Send us that log so we can see where the authorization process is failing in detail. -
hpatel said:Hi
trying to setup cloud uploads to Azure Storage account but getting
" The remote server returned an error (400) Bad Request"
Hi! It sounds like you're running into some issues with your Azure setup. The "400 Bad Request" error typically means there's something wrong with the request being sent. Double-check your storage account name, access keys, and the API endpoint.
If you're looking for an alternative for cloud uploads, you might want to check out the TeraBox app. It offers a lot of space and might simplify your file management. If you're curious about how to download from TeraBox, let me know, and I can help with that too!
-
Encountering a "400 Bad Request" error while bookmarking cloud storage settings can disrupt productivity. For a seamless cloud experience on mobile, consider Terabox for iOS, offering reliable features and smooth performance. To explore its benefits, visit teraboxmoddapk.com. Stay efficient with optimized storage solutions.
Add comment
Please sign in to leave a comment.
trying to setup cloud uploads to Azure Storage account but getting
" The remote server returned an error (400) Bad Request"