Run-time Error '-2147417848(80010108)': in visual basic 6 - Bug

[Vinoth Kumar]

Hi,

I am facing this runtime error in visual basic 6 sp6. This error pops up
randomly while accessing any public property of an custom activex control.

I have two custom activex controls (one done in vb another in vc). each has
public properties and methods. While my vb6 client exe application accesses
the public properties in the activex, my client app crashes with the above
error.

I have seen the following microsoft url and found that it was a bug in vb 6.
But it got fixed in SP3.

"Article ID : 223116 FIX: Public Type Statement Causes Application Error"

But my visual basic 6 has sp6 installed. Eventhough this bug presents.
Any solutions / suggestions appreciated.

Thanks

[expvb]

Post by Vinoth Kumar
Hi,
I am facing this runtime error in visual basic 6 sp6. This error pops up
randomly while accessing any public property of an custom activex control.
I have two custom activex controls (one done in vb another in vc). each has
public properties and methods. While my vb6 client exe application accesses
the public properties in the activex, my client app crashes with the above
error.
I have seen the following microsoft url and found that it was a bug in vb 6.
But it got fixed in SP3.
"Article ID : 223116 FIX: Public Type Statement Causes Application Error"
But my visual basic 6 has sp6 installed. Eventhough this bug presents.
Any solutions / suggestions appreciated.

What type of ActiveX files are you using? OCX, AxEXE, DLL?

Second, search MSKB for "0x80010108", you will find 6 results:

http://support.microsoft.com

If you have ActiveX EXE that crashes while you are using it, use the
following method to pinpoint the line that causes the crash by using VC6. If
you don't have VC6, search for WinDbg, but I haven't used it.

http://groups.google.com/group/microsoft.public.vb.general.discussion/msg/d4dd2618400e8b08

[Vinoth Kumar]

Both of activex controls are in ocx. My client is vb6 exe. I went through all
the 6 kb articles but the one which i mentioned in the post was the exact
issue happens. Crash is happening while accessing the property of the actiex
control.

But the crash is random. its not reproducible always.

My question is in the article it says this issue got fixed in VB sp3. But I
am still facing this issue though i have sp6.

~Vinoth

Post by expvb

Post by Vinoth Kumar
Hi,
I am facing this runtime error in visual basic 6 sp6. This error pops up
randomly while accessing any public property of an custom activex control.
I have two custom activex controls (one done in vb another in vc). each has
public properties and methods. While my vb6 client exe application accesses
the public properties in the activex, my client app crashes with the above
error.
I have seen the following microsoft url and found that it was a bug in vb 6.
But it got fixed in SP3.
"Article ID : 223116 FIX: Public Type Statement Causes Application Error"
But my visual basic 6 has sp6 installed. Eventhough this bug presents.
Any solutions / suggestions appreciated.

What type of ActiveX files are you using? OCX, AxEXE, DLL?
http://support.microsoft.com
If you have ActiveX EXE that crashes while you are using it, use the
following method to pinpoint the line that causes the crash by using VC6. If
you don't have VC6, search for WinDbg, but I haven't used it.
http://groups.google.com/group/microsoft.public.vb.general.discussion/msg/d4dd2618400e8b08

[Ralph]

Post by Vinoth Kumar
Both of activex controls are in ocx. My client is vb6 exe. I went through all
the 6 kb articles but the one which i mentioned in the post was the exact
issue happens. Crash is happening while accessing the property of the actiex
control.
But the crash is random. its not reproducible always.
My question is in the article it says this issue got fixed in VB sp3. But I
am still facing this issue though i have sp6.
~Vinoth

Well ... (wild random thoughts follows lol)

It is always possible that you might have installed SP6 but still using a
different earlier version of something in the OLE stack.

You might visit SysInternals:
http://technet.microsoft.com/en-us/sysinternals/default.aspx
and use some of their tools to make sure you are chewing on the correct
animal.

Exvb and I differ on debugging tools. (friendlily of course) I use WinDbg.
In this case it has the advantage of being installed as Windows
just-in-time-debugger, a la Dr. Watson. When the error occurs it will
deliver a Call Stack pointing out the component at fault and then an
immediate peek into the component.

I vaguely remember an issue with multiple controls in the same OCXs. Think
it turned out to be an issue with GUIDS or identifiers. (Duh! <g>) Make sure
you have throughly cleaned the Registry and deleted any OCAs, previous OCXs,
etc. that may be laying about.

-ralph