A quick solution to SQL Server's successful connection to the server but an error occurred during the logon process _mssql

Recently on the VS2013 connection remote database, suddenly not connected, running MSTest run, QTAgent32 crash. IIS crash when you switch to running under IIS. Before the connection is no problem, after the Internet to find information, according to the cow said the solution.

1. Exception Message

A connection was made to the server successfully, but an error occurred during the logon process. (Provider:ssl provider, error:0-the message received is either unexpected or malformed.) ---> System.ComponentModel.Win32Exception: An unexpected or malformed message was received.

2. Solution

Run the Command Manager as an administrator, enter: netsh winsock reset carriage return, this resets the LSP connection

3. LSP-related (from http://tech.sina.com.cn/s/2009-11-13/14203590640.shtml)

About Winsock LSP "Browser hijacking", the recruit has been high, because of its particularity, direct deletion without restoring the normal state of LSP will likely lead to the inability to access the Internet, so the repair need to be cautious.

First, what is Winsock LSP "browser hijacking". The Winsock LSP full name Windows Socket Layered Service Provider (tiered services provider) is the gateway to the Windows underlying network socker communication needs. Some rogue software can be added in, you can intercept, access, modify the network packet, you can add ads at will, but also to get your browsing habits. This is added to the Trojan, the consequences imaginable. And because LSP works on the ground floor, no matter what browser you use, you can't escape it. When the DLL files in the LSP are deleted, there will be no internet access.

　　Location of the LSP service in the registry

Hkey_local_machine\system\currentcontrolset\services\winsock\parameters\namespace_catalog5\catalog_entries, The default system already has LSP, which is responsible for the normal operation of the TCP/IP components (mswsock.dll) and the NTDS Component (Winrnr.dll), respectively, with entries of 000000000001 and 000000000002, which represent precedence, If a malicious program wants to hijack it, simply change its own entry to 000000000001, and then defer the system items in turn, so that the malicious program can be treated as a priority.

　　Solution:

Method 1. Repair with 360 LSP repair function. If you are prompted that "LSP is not unusual, do not repair," but you still can not go to the network, the ping command, at the IP address will appear (?) ), unable to ping the extranet. Then you will use the 360 "restore Winsock LSP to the initial state" function.

Method 2. Is familiar, is commonly used method, use lspfix this tool to repair under the disconnected network

Method 3. There are two new Netsh commands in Windows XP Service Pack 2.

"Netsh winsock reset catalog This command resets the Winsock directory to the default configuration. This command can be useful if you have installed an incorrect LSP that can cause network connections to be lost. Although you can restore a network connection by using this command, you should use caution because the previously installed LSP will require reinstallation.

Netsh winsock show catalog This command displays a list of Winsock LSP installed on your computer.

So, we can reset the Winsock with the Netsh winsock reset command without any assistive tools

The above is a small series to bring you the SQL Server to establish a successful connection with the server but the error occurred in the process of the rapid solution, I hope to help you, if you have any questions welcome to my message, small series will promptly reply to everyone, Here also thank you very much for the cloud Habitat Community website support!