DISP_E_MEMBERNOTFOUND exception

[hansw]

Something I've been ignoring but now would like to get rid of.
With cerain TeeChart applications I get this message when exiting the application from Debug Mode.
I suspect it can ony be TeeChart becasue a similar application which does not use TeeChart does not casue this error. !


Warning: constructing COleException, scode = DISP_E_MEMBERNOTFOUND ($80020003).
Warning: constructing COleException, scode = DISP_E_MEMBERNOTFOUND ($80020003).

[Christopher]

Hi --

Something I've been ignoring but now would like to get rid of.
With cerain TeeChart applications I get this message when exiting the application from Debug Mode.
I suspect it can ony be TeeChart becasue a similar application which does not use TeeChart does not casue this error. !

From:
http://msdn.microsoft.com/library/defau ... bcsmfc.asp

*************************************************************
Debugging Output You Can Safely Ignore
When you're debugging a control, you may get a series of messages in Visual
C++'s debugging window. Although it's not documented anywhere, some of these
messages can be safely ignored. For instance, when I debug the StopLite
control in the test container using Visual C++ version 4.2, I get the
following:

Loaded symbols for 'C:\WINNT35\system32\MFC42.DLL'
LDR: WARNING ! MAJOR PERFORMANCE LOSS in TSTCON32.EXE
LDR: Dll MFC42D.DLL base 5f400000 relocated due to collision with
C:\WINNT35\System32\MFC42.DLL
Loaded symbols for 'C:\WINNT35\system32\MFC42D.DLL'
Loaded symbols for 'C:\WINNT35\system32\MSVCRTD.DLL'
Loaded symbols for 'C:\WINNT35\system32\MFCO42D.DLL'
Warning: constructing COleException, scode = DISP_E_MEMBERNOTFOUND
($80020003).
First-chance exception in TSTCON32.EXE (MFCO42D.DLL): 0xE06D7363: Microsoft
C++ Exception.

The first line is just notification that the debugging symbols for the
release version MFC DLL were loaded when the test container, which uses the
release version of the MFC DLL, was loaded.

The second and third lines (which begin with "LDR:") warn that the debugging
version of the MFC DLL (used by the StopLite control) had to be relocated in
my address space because it conflicted with the release version of the same
DLL (which is being used by the test container). Although this means that it
took a little longer to load the MFC DLL, it isn't a big deal because it
only happens when you're debugging in the test container. You can ignore
these messages. (Since Visual Basic apps don't use the MFC DLL at all, you
won't get this message if you use a Visual Basic app as your test
container.)

The next three lines are notifications that debugging symbols have been
loaded.

The last two lines are notification that an exception has been thrown
because the test container didn't provide a Color property to be read. This
is okay, because we've provided a default value for the property. You won't
get this error if you use a container that provides the property, such as a
Visual Basic application.

In Visual C++ version 4.1, the only line I got was a warning about the
exception for properties that couldn't be loaded from the container.

First-chance exception in TSTCON32.EXE (MFC40.DLL): 0xE06D7363: Microsoft
C++ Exception.

Depending on how your container handles threads, you may also get occasional
messages about threads exiting. You don't need to worry about these, either.
************************************************************

Possibly you don't have to worry!

[hansw]

Thnaks....
H'mmm goes against the grain... I hate any compiler/linker warning messages.
Still my debug code to check for memory leaks is not reporting anything wrong. I stil ahte "bump in the night code"

Thanks for the link.

Best rgeards
Hans W