I wrote a blog earlier about my first experience (and error encountered) with “Stretch Database” feature. In this blog I would talk about the error – Free Trial subscriptions can provision Basic, Standard S0 through S3 databases, up to 100 eDTU Basic or Standard elastic pools and DW100 through DW400 data warehouses.
This was my first experiment with this feature called Stretch Database. I have started the wizard and encountered at the very end. Here is the error message.
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.
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.
To keep up with the market trend, I have already done my hands-on with SQL in Azure Virtual Machine. In this blog, I would share my learning about a connectivity issue which I faced recently.
SQL SERVER – Unable to Set Cloud Witness. Error: The Client and Server Cannot Communicate, Because They do Not Possess a Common Algorithm
Recently, I was trying to simulate a client’s environment for which I need to have windows cluster with cloud witness. It didn’t go well, and I encountered an error message. In this blog, I will share the solution of error – “The client and server cannot communicate, because they do not possess a common algorithm” which I received while adding cloud witness. I was following below documentation: Deploy a Cloud Witness for a Failover Cluster
SQL SERVER – Error: Parameter ‘ProbePort’ does not exist on the cluster object. Unable to set Probe Port for Azure Load Balancer
Azure is gaining popularity and I am getting clients who want to create Always On availability group as their high availability solution in Azure Virtual machine. To keep myself up to date, I also try creating the customer’s scenario in my lab. In this blog, we would how to fix error Parameter ‘ProbePort’ does not exist on the cluster object while configuring probe port.