Somewhere you are not freeing your COM resources.
This can do several things:
1. Create resource leaks consuming memory until failing and the server just
crashses or
2. Locking some threaded resources which never release and cause the system
to crash.
I have an inkling it is the former.
If you want tools check out www.sysinternals.com
> We are running a ASP.NET application which uses a COM DLL to go to active
> directory and a couple of dataabases. There is no UI to the ASP.NET
[quoted text clipped - 7 lines]
> Is it a memory leak ? if yes how can we monitor it. what tools we can use ?
> can we run the COM dll in a managed environment ?