ATL Service with COM Object called by ISAPI Extension
Hi Tom,
Quote:
> I hope someone has experienced this. I have used the ATL
> Wizard to create a service. I have also added an ATL COM
> object within the service. The hope is that I can start
> the service, initialize a global object and provide access
> to that global object through a COM object.
> I have done this successfully before, but now I am having
> problems. The issues is that every time a client
> instantiates the COM object, the GetMessage loop of the
> service receives a WM_QUIT, which exits the loop and
> terminates the service. This happens both when I use a VB
> client or an ISAPI client.
> Does anyone know why this is happening?
Search for PostMessage or PostThreadMessage of WM_QUIT in your service
implementation files. Maybe you terminate yourself somehow when a COM call
comes in. Attach the de{*filter*} to the service and put a breakpoints on those
PostMessage/PostThreadMessage calls.
How do you call CoRegisterClassObject?
bye,
Sven
