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.
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 – SSIS – Package Error: “ODBC Source” Failed Validation and Returned Validation Status “VS_NEEDSNEWMETADATA”
A client’s SSIS package failed: “ODBC Source” failed validation and returned validation status “VS_NEEDSNEWMETADATA”. I explain which metadata and the fix.
SQL SERVER – FIX: Error 17836: Length Specified in Network Packet Payload Did Not Match Number of Bytes Read; the Connection has been Closed
One of my clients reported that they are seeing below error in SQL Server ERRORLOG. He noticed a strange error of the network packet.