Error when trying to create .NET object from VB6

Question

I am suddenly getting the following error when trying to create a .NET object from VB6 code. It has been working up until now.

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

What is the cause?

FWIW, the error code here is E_POINTER, which usually means that an invalid (or NULL) reference was used for an out parameter to a call. Did you change either the .NET code or the VB code? — reuben
– reuben, Commented Feb 20, 2012 at 3:44
No changes I'm aware of. Of course I will have to check, but I would like to know what the actual problem is. — Gary Jones
– Gary Jones, Commented Feb 20, 2012 at 3:58
This seems like the sort of issue that you'll have to get under a debugger to learn more. Depending on where the issue is, you may need to debug one or both sides of the interop--in VB6 and/or .NET. — reuben
– reuben, Commented Feb 20, 2012 at 4:01
The error is E_POINTER but the message is an AccessViolation. Pretty standard failure mode for DLL Hell. Rebuild the .NET component, recreate the type library, re-register and update the VB6 reference. — Hans Passant
– Hans Passant, Commented Feb 26, 2012 at 20:15

Jeff · Accepted Answer · 2012-02-20 04:19:04Z

1

Has your .NET COM interface changed? If so, you will need to re-regasm your .NET dll in order to update the COM registry accordingly.

Also, if you update the version of the .NET dll with new builds, you'll want to make sure you don't have conflicting versions registered. Try searching the registry for the name of your dll and deleting any keys under HKCR. Then try re-regasm'ing your .NET dll.

Finally, I've seen this error when a constructor (or static constructor) in .NET throws an exception during the creation of your .NET object. Add some tracing and error handling to make sure this isn't the case.

answered Feb 20, 2012 at 4:19

Jeff

36.7k16 gold badges117 silver badges234 bronze badges

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

1 Comment

Deanna Over a year ago

Also make sure that other .NET dlls int he same process havent loaded (their own local) older copies causing even more hell.

Collectives™ on Stack Overflow

Error when trying to create .NET object from VB6

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related