Not able to reach the component

Table 1. Data Collector: Scenario 4
Issue Description Error message ‘Not able to reach the component’ appears
Modules Impacted Data collector, Recommendation, iParse, Generic, RBA, Release
Probable Root Cause

‘CollectIncidents’ job is enabled, and status of job is Failed – Issue with Data Collector Service

Figure 1. Error Message “Not Able to Reach the Component”
Figure 2. Error message ‘Not able to reach the component’ (cont.)

Resolution Steps:

Open the job log for CollectIncidents job. If the job log reads ‘Not able to reach the component’, check the status of DataCollector service by performing the following steps:

  1. Press Win+R and type services.msc.
    Figure 3. Error message ‘Not able to reach the component’ (cont.)
  2. Click OK to open Windows Services.
    Figure 4. Error message ‘Not able to reach the component’ (cont.)
  3. Search for HCL.iAutomate.DC.
  4. Right-click HCL.iAutomate.DC service and click on Properties.
    Figure 5. Error message ‘Not able to reach the component’ (cont.)
  5. Copy the value mentioned in Path to executable as shown in the image below.
    Figure 6. Error message ‘Not able to reach the component’ (cont.)
  6. Open File Explorer, then paste the copied path and press Enter to open the desired folder.
  7. Search for HCL.iAutomate.DataCollector.Service.Host.exe config file and open it in Notepad.
    Figure 7. Error Message ‘Not able to reach the component’ (cont.)
  8. Search for key ServiceHostURL. The value corresponding to this key is the heartbeat URL. Copy it and paste it in browser.
  9. If the flowing page appears, it implies that either service is not running or there is some issue with datacollector.
    Figure 8. Error message ‘Not able to reach the component’ (cont.)
  10. If the following WSDL loads successfully, it implies that service is running fine.
    Figure 9. Error message ‘Not able to reach the component’ (cont.)