Windows7 SQL Server 2012 attempts to read or write protected memory. This usually indicates that other memory is damaged by the repair

Project, the use of SQL SERVER2012 database, the server is 2012, if the client is 2008, will be error:

Index error.

There is no way to install the SQL SERVER2012 client. However, the error is not connected to the database server.

A prompt error is attempted to read or write protected memory. This usually indicates that other memory is corrupted. (System.Data)

When you try to connect again, SQL server Management Studio crashes.

Search the Internet for a keyword to find a solution:

Win7 sqlserver2012 memory read, Win7 sqlserver2012 attempt to read,

Win7 sqlserver2012 thunderbolt, Win7 sqlserver2012 lsp repair, Win7 sqlserver2012 winsock

The error message is as follows:

1. Attempt to read or write protected memory. This usually indicates that other memory is corrupted. (System.Data)

It sharing QQ20131107203307

2. The connection to the server was successfully established, but an error occurred during the login process. (Provider:ssl provider,error:0-received a message exception, or is not in the correct format.) ) (Microsoft SQL Server)

It sharing QQ20131107203322

Then the management collapsed.

It sharing QQ20131107203337

Find a variety of reasons, found that the Thunder is noisy. Maybe Thunderbolt changed some of the settings for Winsock,

Reset a bit of Winsock OK, command: netsh winsock reset.

The original Thunderbolt also gave me a trouble. Nnd What a rascal.

[NET project IE debug appears script block object does not support ' attachevent ' property or method ' workaround]

The solution is simple, just fix the LSP.

1, do not use the tool method:

Try resetting the LSP

Administrator run cmd-input netsh winsock reset

This problem may be caused by VS2013 or office.

2, the use of LSP repair tools: We recommend the use of Jinshan defender's treasure chest of the LSP repair.

：

Http://www.ijinshan.com/ws/index.shtml

or click Download directly:

Windows7 SQL Server 2012 attempts to read or write protected memory. This usually indicates that other memory is damaged by the repair