Resolution:
Description:
============
Unable to start up iProcess Engine with the following errors:

1) swsvrmgr00.log

100517145752.857385:v004: ==> iel_msq_subscribe_to_event ()
100517145752.857464:v004: ==> AddTransientSubscription ()
100517145752.857538:v004: ==> GetTransientSubscriptions ()
100517145752.859326:v001: GetTransientSubscriptions (): CoCreateInstanceEx (): failed: 80040154

2) event log

Event Type: Error
Event Source: TIBCO iProcess Engine
Event Category: None
Event ID: 0
…
Description:
The description for Event ID ( 0 ) in Source ( TIBCO iProcess Engine )
cannot be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following information
is part of the event: TIBCO iProcess Engine error : 0x80040154

, CSWEventInstall(): CoCreateInstance() failed.

Event Type: Error
Event Source: Staffware iProcess Engine
Event Category: None
Event ID: 0
…
Description:
The description for Event ID ( 0 ) in Source ( Staffware iProcess Engine
) cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a
remote computer. You may be able to use the /AUXSOURCE= flag to retrieve
this description; see Help and Support for details. The following
information is part of the event: Staffware iProcess Engine Assertion,
Staffware Service: failed to start the Staffware COM+ Event component.

Environment:
==========
TIBCO iProcess Engine 10.6.3.4
SQL 2005
Windows server 2003 (x64 architecture) with SP1

Symptoms:
=========
Unable to start up iProcess Engine, the process sentinels start but no other processes are able to be started.

Cause:
=====
The comadmin.dll was not registered.

Resolution:
=========
The comadmin.dll needs to be re-registered if a CoCreate issue happens that occurred in the logs.

Process Monitor would show that the comadmin.dll was not registered.

Use process monitor to start a trace, restart the TIBCO service and then stop the trace. The trace will show that it failed to find the following clsid:

procmgr.exe
5268
RegOpenKey
HKCR\Wow6432Node\CLSID\{F618C514-DFB8-11D1-A2CF-00805FC79235}
NAME NOT FOUND

CLSID is from comadmin.dll. Code is accessing the COM Admin objects in order to run a query against the EventSystem service but failing to event create that COMAdmin component. Resolve by registering the .dll using c:\windows\syswow64\regsvr32.exe comadmin.dll.