Shulou(Shulou.com)06/03 Report--

This article mainly introduces the relevant knowledge of "trying to read or write to protected memory, which usually indicates that other memory is corrupted". The editor shows you the operation process through an actual case. I hope that this article "about trying to read or write to protected memory, which usually indicates that other memory has been corrupted," can help you solve the problem.

First of all, let's introduce the reason for this error. Seeing that someone in the garden had written a blog post about Web Api 2.0, I also wanted to learn this technology, so I went to the official website of Microsoft to read the introduction about web api, and then I had the impulse to write a demo myself. Because I installed vs2012 and needed to upgrade to sp4, but I didn't want to upgrade to sp4, the key was that I wanted to experience vs2013, so I waited for 2 hours, and vs2013 was finally downloaded. After the installation, the exciting moment has finally arrived. I can write a web api demo by myself immediately, and the speed of 2013 is better than 2012. According to the introduction of Microsoft's official website, I am still very excited, but the sad story also begins.

When I opened vs2012 and familiar projects as usual, I generated the same solution and entered the same account and password of the system. All of a sudden, the process of the developer server that came with vs was killed, which really scared me. I could hardly believe my eyes. I tried it again yesterday, and it was the same result. Then I debugged all kinds of things. It was found that there was a problem connecting to the database with the following error:

Finally, there was nothing I could do about it, so I asked du Niang and Brother Gu, and looked at the search results. I was very happy, because many people had the same mistake. If you look carefully, everyone's results are different, and most of them are related to calling dll. The most frightening thing is that it is normal for other people to connect to the database, and it is also normal to connect to the database on this computer. There are signs that there should be something wrong with your own system. Suddenly remembered that he is in the installation of vs2013 after the emergence of this problem, so I uninstalled vs2013, uninstall found that still not, really drive me crazy, this is not good, then I will restore the system, I will install vs2013 installed all the plug-ins have been deleted, and finally a miracle appeared, remote connection to the database can be used.

Solution:

After that, I kept thinking about it and found that it was the cause of .NET Framework 4.5.1, and it would be good to uninstall it. But now I don't know why. If you know, please give me some instructions.

That's all for trying to read or write to protected memory, which usually indicates that other memory is corrupted. Thank you for reading. If you want to know more about the industry, you can follow the industry information channel. The editor will update different knowledge points for you every day.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.