.NET Framework Bookmark and Share   
 index > 64-Bit .NET Framework Development > Error when call DLL COM based in VFP 8.0 from EXE .NET 2.0, System. AccessViolationException
 

Error when call DLL COM based in VFP 8.0 from EXE .NET 2.0, System. AccessViolationException

Subject: Error when call DLL COM based in VFP 8.0 from EXE .NET 2.0, System. AccessViolationException.

The error message displayed is: Error System.AccessViolationException, Attempted to read or write protected memory.

This function ok in Windows 2000 and XP but not in Windows 2003 entreprise server SP1

Thanks,
Edwin Rojas
rojas556
You'll have to contact the component vendor for support.

Hans Passant.
nobugz
You'll have to contact the component vendor for support.

Hans Passant.
nobugz
Also I was thinking in the DLL but in Windows 2003 when call de DLL from VBAExcel this work good but when I call from

an EXE .NET 2.0 display an error: Error System.AccessViolationException, Attempted to read or write protected memory.



Thanks,
Edwin
rojas556
That's really good information for the control vendor to help them to diagnose the bug. Be sure to include that in your message to them.

Hans Passant.
nobugz

Edwin,

we have a similar problem. We are attempting tocall a FoxPro dll from .NET code and get a COMException. This exception only occurson some machines using windows server 2003. Curiously, some of our clientsusing windows server 2003 do not experience any problems.

We have searched the web and tried various things but still no solution. Thishas become a very annoying problem for us. Then today whilst considering calling the FoxPro COM object fromunmanaged code (VB 6), i came across this post.

I wonder have youfound a solution to your problem? Any help would be very very much appreciated, as at present i feel like i am banging my head against a brick wall with this one!!

SomeCodeMonkey.

SomeCodeMonkey

You can use google to search for other answers

Custom Search

More Threads

• Debugging VC++ 2005 web services under Windows x64
• Athalon 64 problem with Win XP Home Editon
• Configuration Manager "Any CPU"
• Exposing .NET Class as a COM Class
• the main function of the WCF Service has`t be called,when the 64 bit OS be Rebooted,The wcf service be Set the attribution of ”AutoStart?.
• PInvoke, calling Win32 API on 64 Bit produces unhandled Win32 exception. (Access violation)
• 32bit component brokering from 64bit process
• Did Windows Vista SP1 includes .Net Framework 3.0 sp1 and .Net framework 2.0 sp1
• Access registry created by 32 bit program
• OS 64bit + MOSS 64bit + VS2008 = System.BadImageFormatException