I recently had a very simple and interesting error received while I was performing an upgrade mode with Docker and Persistence Storage for my upcoming workshop.
SQL SERVER – Automatic Seeding of Availability Database ‘DB’ in Availability Group ‘AG’ Failed With an Unrecoverable Error
Automatic seeding of availability database failed with an unrecoverable error: it showed on the secondary, then vanished. Here is what ERRORLOG said.
SQL SERVER – Drop failed for Availability Group – Failed to Destroy the Windows Server Failover Clustering Group Corresponding to Availability Group
While recovering a cluster in ForceQuorum mode, dropping an availability group failed: Failed to destroy the WSFC group. Here is how I got past this error.
SQL SERVER – Installation Error: System.ArgumentNullException – Value Cannot be Null
A client automating SQL Server installs saw random failures: System.ArgumentNullException, Value cannot be null. Here is what Detail.txt showed and the cause.
SQL SERVER – Error: 9642 – An error occurred in a Service Broker/Database Mirroring transport connection endpoint
Error 9642 in the ERRORLOG: an error occurred in a Service Broker/Database Mirroring transport connection endpoint. Here is what caused it for my client.
SQL SERVER – FIX: Install Error: A Network-Related or Instance-Specific Error Occurred While Establishing a Connection to SQL Server
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.