"Attempted to read or write protected memory" error when accessing COM component from C#

Question

I have an ASP.NET application which uses an old and now unsupported third party COM component. The Application runs reliably on windows server 2003, but when I try to run it on 2008 r2 or windows 7, I get the above message. Obviously i've switched the application pool into 32 bit mode.

I realise I will eventually need to replace this with a new component but for the moment I'm just trying to get this legacy app working in the new environment. I can change the C# code that calls it but I can't change the COM component itself.

any thoughts gratefully received

Andy

this link might help you stackoverflow.com/questions/2809489/… — santosh singh
– santosh singh, Commented Apr 30, 2011 at 20:03
Thanks, but I'm pretty sure it's not DEP related as I have tried disabling DEP on the machine and it makes no difference. — Andy
– Andy, Commented Jun 8, 2011 at 10:13

Cole W · Accepted Answer · 2011-05-02 19:50:45Z

1

Try compiling your ASP.Net application targeting the x86 platform.

Edit:

Also when you recompile I would make sure to grab the new Interop it creates in relation to your COM component.

edited May 2, 2011 at 19:50

answered May 2, 2011 at 19:45

Cole W

15.4k7 gold badges56 silver badges88 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

ChrisLively Over a year ago

+1: Most of the time I've seen this is because the app is running in (or was compiled in) x64 mode

Collectives™ on Stack Overflow

"Attempted to read or write protected memory" error when accessing COM component from C#

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related