RVCM triggers from TIBCO InConcert server are not received
Article ID: KB0089584
Updated On:
| Products | Versions |
|---|---|
| TIBCO InConcert | - |
| Not Applicable | - |
Description
Resolution:
The customer's problem happen after they moved the TIBCO InConcert server from one host to another. The debug log showed that triggers were being processed but the audit log showed a failure with an error code of 0.
What the customer did was to copy the IC_HOME/ledger/* file but changed the owner ship of the ledger file. To fix the problem change the owner ship back to the icadmin or whoever own the original file and then restart the IC server.
This is a test.
The customer's problem happen after they moved the TIBCO InConcert server from one host to another. The debug log showed that triggers were being processed but the audit log showed a failure with an error code of 0.
What the customer did was to copy the IC_HOME/ledger/* file but changed the owner ship of the ledger file. To fix the problem change the owner ship back to the icadmin or whoever own the original file and then restart the IC server.
This is a test.
Issue/Introduction
RVCM triggers from TIBCO InConcert server are not received
Feedback
Yes
No
Powered by
