When using an ESX vmware server for a Microsoft Windows Server 2003 64-bit vmware image, there is a chance that the COM+ registry may become corrupt. As a result, TIBCO iProcess Engine (SQL) enabled processes will not start up.
Article ID: KB0094232
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Engine (SQL) | - |
| Not Applicable | - |
Description
Resolution:
Subscribers to COM+ events are not notified when events are raised due to the corruption in the COM+ registry. The reason for the corruption is not known, though according to Microsoft, they suspect a problem with Registry Reflection.
The Process Sentinels (procmgr.exe) start up ok, but none of the other iProcess Engine enabled processes will start.
Microsoft published the KB Article 968447, documenting a fix to this issue - http://support.microsoft.com/kb/968447
The single hotfix to resolve this issue is in two parts:
A. Resolve a registry reflection issue on 64-bit machines, which is known to have the potential to corrupt the registry.
B. Make queries to the event subsystem resilient to corruptions. When subscribers need to be notified, a query is made to the event system to get all the active subscriptions.
Prior to applying the Microsoft hotfix, the query stopped processing as soon as it found a corrupted subscription. With the hotfix applied, the query ignores corrupted subscriptions and continues processing the query, so that valid subscriptions are returned and hence subscribers are notified.
This issue was originally identified for TIBCO iProcess Engine 10.6.0, but it also happened with 10.6.3.
Subscribers to COM+ events are not notified when events are raised due to the corruption in the COM+ registry. The reason for the corruption is not known, though according to Microsoft, they suspect a problem with Registry Reflection.
The Process Sentinels (procmgr.exe) start up ok, but none of the other iProcess Engine enabled processes will start.
Microsoft published the KB Article 968447, documenting a fix to this issue - http://support.microsoft.com/kb/968447
The single hotfix to resolve this issue is in two parts:
A. Resolve a registry reflection issue on 64-bit machines, which is known to have the potential to corrupt the registry.
B. Make queries to the event subsystem resilient to corruptions. When subscribers need to be notified, a query is made to the event system to get all the active subscriptions.
Prior to applying the Microsoft hotfix, the query stopped processing as soon as it found a corrupted subscription. With the hotfix applied, the query ignores corrupted subscriptions and continues processing the query, so that valid subscriptions are returned and hence subscribers are notified.
This issue was originally identified for TIBCO iProcess Engine 10.6.0, but it also happened with 10.6.3.
Issue/Introduction
When using an ESX vmware server for a Microsoft Windows Server 2003 64-bit vmware image, there is a chance that the COM+ registry may become corrupt. As a result, TIBCO iProcess Engine (SQL) enabled processes will not start up.
Feedback
Yes
No
Powered by
