>Hi,
>
>I've built a COM server exe which is called by another developer using ASP.
>
>The COM server works great, but we've come up with a problem - if the user closes his browser while the COM server is running, the object is never released and remains as a process on the server.
>
>If this happens multiple times, the instances of the object build up on NT. The only way we have found to release these instances is to reboot the server - stopping and starting the web server doesn't help [and would be unacceptable in any case].
>
>Can anyone think of a solution for this ?
>
>Best.
>
>Matt.

How about building it as a DLL and running it under MTS or Win2K Component Services.