As a part of my relationship with existing clients, I provide quick help to them on simple issues. Sometimes it is an interesting issue and I write a blog about it as well. Let us learn the error related to SaveToSQLServer.
SQL SERVER – Database Mirroring Login Attempt Failed With Error: ‘Connection Handshake Failed. There is No Compatible Encryption Algorithm. State 22
One of my client was trying to convert database mirroring to the AlwaysOn availability group. They had a mirroring configure where the principal server was going to become a primary replica. When they attempted to join the AG, it was failing with an error. The error messages we were getting in the wizard are not helpful. I went ahead and looked into SQL Server ERRORLOG and found below the messages
SQL SERVER – Mirroring Error: Connection handshake failed. Could not send a handshake message because the connection was closed by peer. State 26
Here is another blog based on client’s interaction via Skype. They informed me that they are trying to execute the command ALTER DATABASE SET PARTNER while attempting to set up mirroring between two servers, we see the following mirroring error recorded in the secondary error log:
SQL SERVER – The Log Scan Number Passed to Log Scan in Database ‘master’ is not Valid
If you have landed on this blog by searching below error, then I must tell you that your SQL Server service is not getting started. Let us learn in this blog how to fix The Log Scan Number Passed to Log Scan in Database ‘master’ is not Valid.
SQL SERVER – Database Mirroring Login Attempt Failed with Error ‘Connection Handshake Failed’
One of my friends was trying to configure database mirroring and was having a hard time in getting things working. The challenge was that he was using certificate for mirroring authentication because machines were workgroup not in domain. He followed one of the blog from Microsoft site but still having problems.
SQL SERVER – Installation Error – [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
One of my blog readers sent an email to me asking for assistance. They were trying to patch SQL Server 2005 in the cluster and the setup was failing to patch database services with below error related to data source name.
SQL SERVER – Cannot initialize the data source object of OLE DB provider “Microsoft.ACE.OLEDB.12.0” for linked server
As you might have seen, along with performance tuning related work, I also help community in getting answers to questions and troubleshoot issue with them. A few days ago, one of community leader and user group champion contacted me for assistance. He informed me that they are using Microsoft Access Database Engine 2010 provider to read data from an excel file. But they are seeing below error while doing test connection. Let us learn about error related to OLE DB provider.