Questions[com+](server)

I have an odd issue that I haven't been able to track down.

We have a COM+ component on our Windows Server 2008 R2 (Windows 7 on our developer machines) that is called by an ASP.net application.

At times the COM+ component will throw back the error:

System.Runtime.InteropServices.COMException (0x8000401A): The server process could not be started because the configured identity is incorrect. Check the username and password. (Exception from HRESULT: 0x8000401A)

Someone has to go into the COM+ component and reapply the password for the service account the component runs as, and then everything is fine.

On the development machines they report it happening every night.

On the PRD machine someone remains logged in via RDP and the issue never happens.

I'm somewhat perplexed by what's going on here. Anyone see this before?

A Windows Serve 2003 machine logged an error in Event Viewer with the COM+ Event System, saying it could not marshal the subscriber for a particular subscription and then gave the SID/GUID, which is:

{DF540FFA-D787-4FDF-82E4-4BD5C1302F23}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}.  The HRESULT was 800706BB.

I don't quite understand the error.

I'm trying to look up the GUID to find the application.

I tried opening up the registry and searching for it but it didn't find anything. A google research revealed I need to load the cluster database in the registry and look up the GUID. The problem is I cannot find the CLUSDB file. It is not in %SystemRoot%\Cluster.

What do I need to do to identify the application in question?

I have a COM+ component on a different server, but when I made an update to one these components then it stopped working. How to configure MSDTC?

From the application log:

A caller has attempted to propagate a transaction to a remote system, but MSDTC network DTC access is currently disabled on machine 'NACHINE11'. Please review the MS DTC configuration settings.

I tried this http://www.howtogeek.com/howto/windows/fix-new-transaction-cannot-enlist-in-the-specified-transaction-coordinator-on-server-2003-sp2/

But it doesn't look so in Windows Server 2008 R2. Is it located somewhere else?

If the Component Services console is used to shut down a COM+ Application while there are active threads, what happens to those active threads that the COM+ application created to service the client calls? Are they forcibly closed, or are they allowed to complete before the application is shut down?

Is there a PowerShell module or commands for administering COM+ components? In particular, I'd like to:

• Query whether a COM+ application is installed/registered.
• Start or Stop a COM+ application.
• Install/register or uninstall/unregister COM+ application.

I am new to both PowerShell and COM+ so may be using the wrong terms (install vs register, etc).