Not able to reach the component

Table 1. iKnowledgeIndexer: Scenario 7
Issue Description Error message ‘Not able to reach the component’ appears in job log details - step remarks column for Indexer job in manage jobs page, also the status is in ‘failed’ state
Modules Impacted iKnowledge Indexer
Probable Root Cause Duplication of keys in .cfg files present in python files

Resolution Steps:

  1. Check for existence of the file iKnowledgeIndexer.conf at location <Apache_Root_Folder_Path>/conf.
  2. At the bottom of iKnowledgeIndexer.conf file you will find the path to the python files as highlighted in the below figure.
    Figure 1. HCL.iAutomate.iKnowledgeIndexer(cont.)
  3. Open the file INDEXER.cfg from the location <highlighted_path_in_fig_128> and search for any duplicate keys present in the file. You can refer to the keys below for reference:
    Figure 2. HCL.iAutomate.iKnowledgeIndexer (cont.)
  4. Remove the last entry that is duplicate for each key. In the above case delete the second entry of EncryptionAlgorithm = aesgcm. Similarly check for any other duplicate keys and remove the last entry and save the file.
  5. Finally restart the service named HCL.iAutomate.iKnowledgeIndexer
    Figure 3. HCL.iAutomate.iKnowledgeIndexer (cont.)