Troubleshooting errors with the TrueSight Operations Management integration
When you integrate
with BMC ProactiveNet, certain errors might occur.
Issue symptoms | Issue scope | Resolution |
---|---|---|
Change events are not displayed on the TrueSight Operations Management Console | The integration is not active. |
|
Error out events are not sent to TrueSight Operations Management | Special characters are used in the event. | Resend the Error out events to TrueSight Operations Management:
|
TrueSight Operations Management instance is not displayed in the configuration form | The UDDI Registry is not installed. |
|
Change CI Event Notification to BPPM link not visible | The required extensions are not installed. | Make sure that the required extensions are installed. Perform following steps:
|
CLI command to activate the and TrueSight Operations Management integration displays a timeout error | There is a deadlock condition in the Microsoft SQL server. | The timeout error occurs due to a deadlock condition in the Microsoft SQL server. This issue can be resolved by using snapshot isolation to reduce possibility of deadlocks in Microsoft SQL Server. This error can occur if the mandatory setting required in the Microsoft SQL Server after the installation is completed is skipped. To use a snapshot isolation level with the database, see the "To use a snapshot isolation level with the AR System database" procedure described under Using Microsoft SQL Server with BMC Helix Innovation Suite. |