I developed a service that uses the COM interface on different applications
to do printing. I am now migrating it to a ISAPI ATL Server.

My problem is that IIS craches when I try to create the COM object. For
example the line:

excelApplication.CreateDispatch("Excel.Application");

makes the following entries in the Event log:
* A total restart of IIS
* A timeout notification from DCOM

I have tried to setup dcomcnfg to use a impersonated user with the same
result. Of course I can separate the ISAPI functions from my application by
using named pipes. Since all code works when run as a service I don't think
that there are any simple bugs in my code. (Yes, I have called
"CoInitialize(NULL);" just before).

I had to put my application code in a separate dll called by the ISAPI
application dll to get rid of the usual dllmain linking problems. The
application is developed in C++ with Visual Studio .Net 2003, using the
standard ATL Server Application template, and is running in a W2000 server.

Is it at all possible to create COM Objects this way from an ISAPI
application? Any hints would be appreciated.