Troubleshooting impact analysis issues
Issues when running impact analysis from incidents or change requests
| Symptom | Issue scope | Resolution |
|---|---|---|
While running impact analysis from an existing incident or change request by selecting More > Impact Analysis Console and creating a new impact analysis run, the following error message is displayed: Error (245150) Could not retrieve any starting CIs. Verify if the CIs are synced to DSM. | Occurs when you attempt to create a new impact analysis by using associated CIs or selecting input CIs in the impact analysis console. | Run a Smart Graph Sync Schedule from BMC Helix CMDB. For more information, see Scheduling a DSM Sync to share impact attributes with BMC Helix NetOps in the BMC Helix CMDB online documentation portal. |
While running an impact analysis from an existing incident or change request, and creating a new impact analysis run, the following error message is displayed: Error (245124) You cannot run the impact analysis till the data sync is complete. | Occurs when you attempt to run impact analysis in one of the following ways:
| Run a Smart Graph Sync Schedule from BMC Helix CMDB. For more information, see Scheduling a DSM Sync to share impact attributes with BMC Helix NetOps in the BMC Helix CMDB online documentation portal. |
While running an impact analysis from an existing incident or change request, and creating a new impact analysis run, the following error message is displayed: Error (245116) Currently, there are no CIs associated to this ticket. You must associate a CI to run the impact analysis. | Occurs when you attempt to create a new impact analysis by selecting input CIs in the impact analysis console. | Associate impact CIs with the Association type other than Impacts to the incident. For more information, see Adding-configuration-items-to-tasks. |
While running impact analysis from an existing incident or change request by selecting More > Impact Analysis Console and creating a new impact analysis run, the following error message is displayed: Error (245114) The impact analysis is already in progress. After the existing process is complete, you can initiate another impact analysis. | Occurs when you attempt to create a new impact analysis by using associated CIs or selecting input CIs in the impact analysis console. | Wait until the impact analysis completes, then run it again. For more information, see Performing-an-impact-analysis-on-an-incident-ticket. |
While relating impacted CIs back to an incident or change request, the following error message is displayed: Warning (245121) The selected CIs are already related to this ticket. | Occurs when you select CIs and attempt to relate CIs to an incident using the Relate selected CIs option in the impact analysis console. | Select other CIs and then click Relate selected CIs. For more information, see Performing-an-impact-analysis-on-an-incident-ticket |
Issues with automated impact analysis rules
| Issue symptom | Issue scope | Resolution |
|---|---|---|
| Impact analysis is not triggered when a CI is associated with an incident by using the relationship type Impacts, despite a rule being configured with CI association as a trigger event. | A rule is configured with CI Association as a trigger event in BMC Helix Telco Extensions Network Impact Analysis settings. Despite the rule being correctly defined with the required fields, impact analysis is not triggered. | Automated impact analysis does not consider CIs associated using the Impacts relationship type. To ensure the rule is triggered correctly, use a supported relationship type other than Impacts when associating CIs with incidents. For more information, see |
| Impact analysis is not triggered automatically when a new incident is created, even though rules are configured. | Below are the conditions under which the issue occurs:
| Ask your administrator to verify that:
For more information, see |
| Impact Analysis is not triggered automatically when a Configuration Item (CI) is removed from an incident. | The issue occurs when a service desk agent or incident user, or incident master removes CIs from an incident request. | Ask your administrator to verify that:
For more information, see |
| The service desk agent gets the information in the activity note that the automated impact analysis is not complete. | The impact analysis for the change request is not triggered, even though I have created a rule. | Make sure that the following conditions are true:
|
Issues in the impact analysis summary
| Issue symptom | Issue scope | Resolution |
|---|---|---|
| While generating an impact analysis summary, the following error message is displayed:Error: 500 - NOT_ABLE_TO_GENERATE_SUMMARY | Occurs when you attempt to generate an impact analysis summary. | Make sure the BMC HelixGPT is properly configured and ready to use. For more information, see Configuring-BMC-HelixGPT-for-BMC-Helix-Telco-Extension. |
Issues related to service classes
| Issue symptom | Issue scope | Resolution |
|---|---|---|
| The setting to configure a service class is not available. | When attempting to create, update, or delete the configuration from the impact analysis setting, the configure a service CI class setting is dimmed. | Make sure that the following conditions are true:
For more information, see |
Certain service CI classes are not displaying in the service CI column of the impact analysis results. | Occurs when you run an impact analysis. | Make sure you have configured the service CI classes in the BMC Helix Telco Extensions. For more information, see Configuring the impact analysis settings |
General impact analysis issues
| Issue symptom | Issue scope | Resolution |
|---|---|---|
The rerun impact analysis option is not available for runs that are still in Progress. | Occurs when you attempt to rerun the impact analysis from an existing incident or change request. | Make sure that the impact analysis is in one of the following states:
For more information, see
|
The option for relating the CIs is not available or is not functioning. | Occurs when you try to relate impacted CIs from a rerun impact analysis. | Make sure that the following conditions are true:
For more information, see
|