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 – Unable to Set Cloud Witness. Error: An Existing Connection Was Forcibly Closed by The Remote Host
Setting up a cloud witness for a client failed with: An existing connection was forcibly closed by the remote host. Test-NetConnection pointed to the real cause.
SSMS – Azure Storage Error – A Connection Attempt Failed Because the Connected Party did not Properly Respond After a Period of Time
SSMS could not open Azure Storage: a connection attempt failed because the connected party did not properly respond. Here is what caused it.
SQL SERVER – FIX: Cannot Connect to SQL in Azure Virtual Machine From Laptop
SSMS on my laptop could not connect to SQL in Azure Virtual Machine, even though it worked fine on the VM itself. Here is how I fixed the connection.
SQL SERVER – Unable to Set Cloud Witness. Error: The Client and Server Cannot Communicate, Because They do Not Possess a Common Algorithm
Adding a cloud witness to my cluster failed: The client and server cannot communicate, because they do not possess a common algorithm. I share the fix that worked.
Set-ClusterParameter Error: ProbePort Does Not Exist on the Cluster Object
The Set-ClusterParameter error said Parameter ‘ProbePort’ does not exist on the cluster object. I hit it while setting up a probe port for an Always On listener in Azure. Two wrong values in my script were the cause, and fixing both let the script run.
Backup to URL Hangs on PREEMPTIVE_HTTP_EVENT_WAIT in an Azure VM
Backup to URL hangs on PREEMPTIVE_HTTP_EVENT_WAIT when an outbound rule denies internet access on an Azure virtual machine. I saw it after blocking the internet on my own VM. An outbound rule that allows the Storage destination fixed it.