"Go" SQL Server--the connection to the server has been successfully established, but an error occurred during the logon process

SQL Server-- a connection to the server was successfully established, but an error occurred during the logon process

Recently connected to the remote database on the VS2013, the sudden connection is not up, running MSTest under the time,QTAgent32 Crash. Replace IIScrash when running under IIS . Before the connection is no problem, after the Internet to find the information, according to the cow people said the solution.

1. Exception Message

The connection to the server was successfully established, but an error occurred during the logon process. (Provider:ssl provider, error:0- The message received is abnormal, or is malformed.) )---> System.ComponentModel.Win32Exception: The received message is abnormal, or the format is incorrect.

2. Solution

Run Command Manager as an administrator, enter:netsh winsock reset return , This reset LSP Connection

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

About the Winsock LSP "browser hijacking", the recruit has been high, because of its particularity, direct deletion without restoring the normal state of the LSP is likely to lead to a lack of access to the Internet, so the repair needs to be cautious.

first talk about what is the Winsock LSP "browser hijacking". The Winsock LSP full name Windows Socket Layered Service Provider (tiered service provider), which is the gateway to the Windows underlying network Socker communication. Some rogue software can be added in, you can intercept, access, modify the network of data packets, you can freely add ads, but also to get your browsing habits. This Riga into a 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 file in the LSP is deleted, there will be no internet access.

The 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 an LSP, which is responsible for the normal operation of the TCP/IP components (mswsock.dll) and the NTDS Components (Winrnr.dll) , respectively, 000000000001 and 000000000002, these two items indicate priority, if the malicious program wants to hijack, as long as its own entries to 000000000001, the system items are pushed down, so that the priority to deal with the malicious program.

　　Workaround:

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

　　Method 2. is familiar, that is, commonly used methods, with lspfix This tool under the disconnection network repair

　　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 is useful if you have installed an incorrect LSP that can cause network connections to be lost. Although you can use this command to restore network connections, you should use caution, because previously installed LSP will need to be reinstalled.

The netsh winsock show catalog This command displays the list of Winsock LSP installed on the computer.

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

Transferred from: http://www.cnblogs.com/caijingui/p/3612970.html

"Go" SQL Server--the connection to the server has been successfully established, but an error occurred during the logon process