SQL SERVER – Unable to Set Cloud Witness. Error: An Existing Connection Was Forcibly Closed by The Remote Host

After finishing my lab and testing, I went to my client and they showed me error while setting up cloud witness. They showed me a different error then earlier. In this blog, we would learn about fixing error Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host while configuring cloud witness.

Read More

SQL SERVER – Error 1051: A Stop Control Has Been Sent to a Service that Other Running Services are Dependent On

Sometimes there are some random unexpected errors and it’s always fun to find the cause of them. In this blog we would learn about an error 1051 (A stop control has been sent to a service that other running services are dependent on) which I received while stopping SQL Service in my lab server.

Read More

SSMS – Azure Storage Error – A Connection Attempt Failed Because the Connected Party did not Properly Respond After a Period of Time

This was an interesting situation where I learned something new. In this blog we would learn about error – “A connection attempt failed because the connected party did not properly respond after a period of time.” while using “Azure Storage” option in SQL Server Management Studio.

Read More

SQL SERVER – Always On Availability Group Listener Missing in SSMS but Working Fine in Failover Cluster Manager

I have helped many customers to solve complex issues in their environment by Comprehensive Database Performance Health Check. Sometimes, the issue looks very complex but once the solution is found it seems very easy. In this blog, we would learn about a situation where the listener is missing in SSMS but working fine in failover cluster manager (cluadmin.msc).

Read More
Exit mobile version