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

(0) Share

Report

Posted on by yousefsuli

Hello

I have issue when updating worker information, the screen freeze and roll back the changes after debug the code I found this issue on dirpartytable.

we are using D365FO.

0458.community.png

All responses (5)

Answers (0)

Martin Dráb 231,923 Most Valuable Professional on at

Like (1)

Report

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

Try putting the breakpoint at a different place. You could also try a different web server (IIS instead of IISExpress or vice versa) or a different version of Visual Studio.
yousefsuli 55 on at

Like (0)

Report

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

I did a full build the freezing issue still exists, and I checked the blocking transactions on SQL Server but there's no data. goshoom do you have any other suggestion?
Martin Dráb 231,923 Most Valuable Professional on at

Like (0)

Report

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

All right, so you indeed doesn't get AccessViolationException in that case.

Try if rebuilding the model doesn't solve the problem with debugging. You can also check blocking in SQL Server; it could be the cause.
yousefsuli 55 on at

Like (0)

Report

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

If I run without debugging when updating worker profile like name and press the save button system freeze for a couple of minutes, then refresh the application and roll back my change.
Martin Dráb 231,923 Most Valuable Professional on at

Like (0)

Report

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

Do you get any error if you run the code without debugging?

Most cases when I saw this error where related to the debugger, not to the actual code.