Tuesday, March 8, 2016

SQL DBA: SQL Server connectivity Issue – A connection was s...

SQL DBA: SQL Server connectivity Issue – A connection was s...: We were able to make a connection to SQL server from local SSMS and from few other servers. But we got below error from application se...

Monday, March 7, 2016

SQL Server connectivity Issue – A connection was successfully established with the server, but then an error occurred during the pre-login handshake.


We were able to make a connection to SQL server from local SSMS and from few other servers.
But we got below error from application servers:

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (Provider: SSL Provider, error: 0 - The Local Security Authority cannot be contacted) (Microsoft SQL Server, Error: -2146893052)

Error connecting to local/remote SQL server through SSMS:


Windows server Event Log has many SChannel errors as below:
The following fatal alert was generated: 51. The internal error state is 602.

This error was caused by a bad update of windows server related to a security configuration/spoofing.

To resolve this:
or
1.       Go to regedit
2.       Locate and then click the following subkey in the registry: HKLM\System\CurrentControlSet\Control\SecurityProviders\Schannel
3.       On the Edit menu, point to New, and then click DWORD Value.
4.       For the computer that is receiving the connection request, type DisableServerExtendedMasterSecret: REG_DWORD for the name of the DWORD, and then press ENTER.
5.       For the computer that is initiating the connection request, type DisableClientExtendedMasterSecret: REG_DWORD for the name of the DWORD, and then press ENTER.
6.       Right-click the new DWORD entry, and then click Modify. Type 1 or a non zero value.

Note : Make sure that Regedit values are added correctly. Server restart is not required.