51f
Subj : Problems running a COM-Automation-Server in a service
To   : borland.public.cpp.borlandcpp
From : Chris
Date : Thu Sep 30 2004 06:02 pm

Hi,

I'm having trouble running a COM-Automation-Server in a TServiceApplication. 
When I try to call an Interface-Method the calling client allways starts a 
new exe and don't uses the running service. I don't have the problem when I 
implement the COM-Server in a normal Application.

I tried several settings and threading-models on the server side (the Object 
was made with the COM-Automation-Expert) but couldn't fix it.
On Client side I implemented the server by an extra component (library 
import with component-wrapper). I noticed that it only works with 
"ConnectKind = ckNewInstance", but while the clients only use one exe when 
the server-object is embedded in a normal application they allways start a 
new exe when the server-object is embedded in a service (no matter if the 
service is running or not).

What I don't know: is the service having problems running more than one 
instance of the COM-Object or is the difference to a normal application that 
it locks the server and the instance can't be released by the client while 
that works with a normal application?

 Any suggestions on this?

greetings,
Chris

.

0