How to force FinalRelease() when clients to out of proc server "crashes"

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Pieter (msnews_at_insanegenius.com)
Date: 11/06/04 

Date: Fri, 5 Nov 2004 21:20:53 -0800

We have an out of proc COM server running as a service.
If the out of proc client crashes, or terminates without releasing the
objects (leaks), it takes either a long time for FinalRelease(), or the
objects created in the service never gets destroyed.

Is there a way to programmatically "test" the connected state of the objects
and / or "force" a release if the out of proc client no longer exists?

Regards

Pieter