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 – Read Only Routing Error: Client Unable to Establish Connection Because an Error was Encountered During Handshakes Before Login
A client’s Always On read-only routing failed with: an error was encountered during handshakes before login. Here are the checks I shared and how we fixed it.
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)
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.
SQL SERVER – Error 1051: A Stop Control Has Been Sent to a Service that Other Running Services are Dependent On
Stopping SQL Server in my lab gave Error 1051: A stop control has been sent to a service that other running services are dependent on. Here is what caused it.
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 – Always On Availability Group Listener Missing in SSMS but Working Fine in Failover Cluster Manager
My client’s AG listener worked fine in Failover Cluster Manager, yet SSMS showed nothing. Here is what causes a listener missing in SSMS and the fix.