A network-related or instance-specific error usually hits applications, but my client saw it during SQL Server installation. Here is how to fix it in that case.
Get-AzureStorageBlob: The Remote Server Returned an Error: (403) Forbidden. HTTP Status Code: 403 – HTTP Error Message: This Request is Not Authorized to Perform This Operation
A runbook cleaning old backup blobs in Azure failed with (403) Forbidden: This request is not authorized to perform this operation. Here is the fix.
SQL SERVER – Identify the column(s) responsible for “String or binary data would be truncated.”
For years, String or binary data would be truncated never told us which column was too long. Now SQL Server does, and here is how to identify the column responsible.
SQL SERVER – Script Level Upgrade for Database ‘master’ Failed Because Upgrade Step ‘SSIS_hotfix_install.sql’ Encountered Error 15151
Another SQL Server upgrade failure: upgrade step SSIS_hotfix_install.sql hit error 15151 because a user did not exist. Here is how I fixed it.
SQL SERVER – Error in Validation: Listener in Workgroup – Unable to determine if the computer exists in the domain ‘WORKGROUP’
A client’s domain-less Always On cluster in Azure could not create a listener: Unable to determine if the computer exists in the domain ‘WORKGROUP’. Here is why.
SQL SERVER – Script Level Upgrade for Database ‘master’ Failed Because Upgrade Step ‘msdb110_upgrade.sql’ Encountered Error 8649, State 1, Severity 17
Patching SQL 2017 failed at msdb110_upgrade.sql with error 8649: the query cost exceeded the configured threshold. Here is the cause and the fix.
SQL SERVER – Error: 825 – A Read of the File at Offset Succeeded After Failing 1 Time(s)
One of my clients contacted me to give advice about an error. In this blog, we would discuss error message – A read of the file at offset succeeded after failing 1 time(s)