Attempted to read and write protected memory issue

Question

0.00/5 (No votes)

See more:

We recently moved our application from Windows server 2003 to Windows server 2012. Application has two components-- one is MVC and other one is simple ASP.NET with aspx pages. Application is working fine but sometimes we receive-- Attempted to read and write protected memory . This is often an indication that other memory is corrupt error.

When I checked Event Viewer for the error, below is the exception: Exception information: Exception type: HibernateException Exception message: Creating a proxy instance failed

When we get this error, we usually recycle app pool and issue gets resolve. Need your inputs for long term fix.

What I have tried:

We recently moved our application from Windows server 2003 to Windows server 2012. Application has two components-- one is MVC and other one is simple ASP.NET with aspx pages. Application is working fine but sometimes we receive-- Attempted to read and write protected memory . This is often an indication that other memory is corrupt error.

When I checked Event Viewer for the error, below is the exception: Exception information: Exception type: HibernateException Exception message: Creating a proxy instance failed

When we get this error, we usually recycle app pool and issue gets resolve. Need your inputs for long term fix.

Posted 18-Jul-17 6:47am

Surendra Patil

Updated 18-Jul-17 7:41am

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

W∴ Balboos, *GHB* · Answer 1 · 2017-07-18T07:01:00

A bit simple-minded a comment, but in case you've not considered it:

Symptoms and Attributes:
1 - You can resolve issue by modifying a resource that's limited.
2 - You only get this message sporadically.
3 - Likely cause, then, is a failed allocation, leaving you reading/writing to a null pointer.
4 - Perhaps no error handler to check for this, either?

You need to have the app pool recycle to occur as a job - not wait for it to fail.
Trap the untrapped error (if any).

The above is generically true for this type of error; going back to the days of 'C'.

Dave Kreskowiak · Answer 2 · 2017-07-18T07:41:00

There is no way for anyone to be able troubleshoot this except yourself. You haven't provided any usable information at all.

But, there is a hint in the Exception message:

Exception information: Exception type: HibernateException Exception message: Creating a proxy instance failed

According to the Java documentation, a HibernateException is the parent class for a ton of SQL related exceptions.

It would appear that you're doing something properly related to any SQL database work, possibly not properly closing a dataset somewhere, a connection object, a reader, ... anything.

With the information you provided, that's the best answer you're going to get.

Attempted to read and write protected memory issue

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0