Attempted to read or write protected memory.This is often an indication that other memory is corrupt

06 April,2018 by Jack Vamvas

Question: When attempting to open a table via SSMS 2012 – through the Edit top 200 rows , I get the Exception has been thrown by the target of an invocation , Attempted to read or write protected memory.This is often an indication that other memory is corrupt   error message

Corrupt_memory

How can I fix?

Answer: There are a number of potential fixes to this problem

1)Is the SSMs the correct version? In other words is the SSMS a lower version from the target SQL Server?   For example – are you attempting to connect to SQL Server 2016 from a SSMS version 2012?

2)Have you recently installed\upgrade .Net framework? You may need to repair

3) Have you rebooted the machine hosting the client ?

 

Read more on SSMS

How to fix System.OutOfMemoryException when using SSMS (SQL ...

SQL Server – Open SSMS without the splash screen graphic

SQL Server - Open SSMS on the Command Line (SQL Server

 

 


Author: Jack Vamvas (http://www.sqlserver-dba.com)


Share:

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment on Attempted to read or write protected memory.This is often an indication that other memory is corrupt


sqlserver-dba.com | SQL Server Performance Tuning | SQL Server DBA:Everything | FAQ | Contact|Copyright & Disclaimer