what Microsoft.VisualStudio.OLE.Interop corrupt

Question

Hi all,

in the SQL Server Management Studio 2014, after right click a table and choose Edit top(n) Rows, this exception pop up.

it used to work well until our database has moved to 2017 server. Do I need to upgrade my management studio also? thanks,

TITLE: Microsoft SQL Server Management Studio

---

Exception has been thrown by the target of an invocation. (mscorlib)

---

ADDITIONAL INFORMATION:

Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (Microsoft.VisualStudio.OLE.Interop)

---

BUTTONS:

OK

---

Answer 1

Hi @sheldon ,

Is the reply helpful?

BR,
Mia

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Answer 2

Hi @sheldon ,

...Do I need to upgrade my management studio also?

Yes.You do. Download the latest SSMS here: release-notes-ssms

Quote from this doc.:error-in-ssms-attempted-to-read-or-write-protected-memory

...It’s an internal error in the Object Explorer code caused by something in an older version of SSMS working with newer version of SQL....

BR,
Mia

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Answer 3

Microsoft detached SQL Server instance and SSMS from each other already long time ago.
They are coming with their own separate installers.

You can install the latest available version of SSMS, that is currently v.18.7
It will allow to use it with any SQL Server instance version, i.e. 2019, 2017, 2016, etc.