Automation Error

[chand]

--------------------------------------------------------------------------
Run-time errro '-2147418105(80010007)':

Automation error
The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have been executed.
--------------------------------------------------------------------------

I have a VB6 application that supports plugins. All the plugins (activex dll's) interface with the application through an activex dll.

I get this error when the plugin tries to call a function in the application [through the plugin interfacing dll]

On some rare occasions I dont get this error.

Can this be fixed????

Thanks in advance!

[Chubby]

This maybe a duuuuuuuh kind of offering but I have only ever seen this error relating to ActiveX Exe's and it occurs if the ActiveX Exe has gone out of memory for whatever reason. Is the Interface structure EXE > ActiveX DLL > DLL or is there some hooking singleton object (ActiveX EXE (namely Server type)) object in the mix ?


Chubby..

[chand]

Not using Activex EXE anywhere.
The interfacing dll is partly implemented by the application exe and partly by the plugin dll.

I get this error only while debugging the plugin and not while using the compiled version of the plugin.
This is making debugging very difficult.

Btw, both the interfacing dll & plugin dll are activex dll's

[Chubby]

Not using Activex EXE anywhere.
The interfacing dll is partly implemented by the application exe and partly by the plugin dll.

I get this error only while debugging the plugin and not while using the compiled version of the plugin.
This is making debugging very difficult.

Btw, both the interfacing dll & plugin dll are activex dll's

OOK,.... doesnt happen in production.... one suggestion maybe that the ActiveX Dll plugin cannot see the running instanace of the EXE project at some point or other.. If this is purely debugging then for my money I would implement some kind of debugging file write, compile the lot and and run some test scripts to ensure all calls & sinks get to and from their destination... ??

Chubby..

[badbee]

I experience the similar automation error in the following scenario:
When there was a runtime error in any Active-X DLL that my program used (some error that may sound more reasonable like Type Mismatch etc).
This error caused the DLL to crash. Now if I try to execute some operation of the same DLL, the automation error appeared.

I would suggest that you investigate/debug some message that appeared before this automation error. This might give you the idea where error actuallyu exists.

[chand]

I seem to have found a little pattern that allows debugging without the main application exitting.
Before I break in the plugin dll's source, I make sure that the ide has focus and not the main application.
For example - currently for my import plugin a common dialog appears first for file selection - next I give the ide focus & after that I focus on the common dialog.

If the application exe is given focus before the common dialog then most of the times the application exits {even with a completely functional plugin}.

Thanks for ur help.