HCL.iAutomate.iCrawler service is not starting

Table 1. iCrawler: Scenario 1
Issue Description HCL.iAutomate.iCrawler service is not starting
Modules Impacted iCrawler
Probable Root Cause Invalid “iknowledgeCrawler.conf” file content

Resolution Steps:

  1. Check for existence of the file iknowledgeCrawler.conf at location <Apache_Root_Folder_Path>/conf.
  2. For e.g. - “C:/Apache24/conf” has <Apache_Root_Folder_Path> as “C:/Apache24”.
  3. Ensure that paths are mentioned correctly in the iknowledgeCrawler.conf file.
  4. In the conf file, inside < VirtualHost *> tags, there are two lines that have path to the iCrawler directory as follows:
     WSGIScriptAlias /iKnowledge <<Path to Crawler>>/crawler_v5/main.wsgi
    <Directory <<Path to Crawler>>/crawler_v5>
  5. Ensure that these paths are correct.
      <VirtualHost *>
    WSGIScriptAlias /iKnowledge C:/HCL.iAutomate.Crawler/crawler_v5/main.wsgi
    SSLVerifyClient require
    SSLVerifyDepth 10
    <Directory C:/HCL.iAutomate.Crawler/crawler_v5 >
    WSGIApplicationGroup %{GLOBAL}
    Require all granted
    </Directory>
    </VirtualHost>
  6. Ensure that service was created through Service Account and not through the Local Account. Refer to the figure below to check the status.
    Figure 1. HCL.iAutomate.iCrawler
  7. If not, open Windows Command Prompt in Administrator mode and run the below command:
    sc config HCL.iAutomate.iCrawler obj= “ID” password= “PSWD”
    where ID is the [Domain\SA ID] and PSWD is the [Password of SA] and SA is
    [Service Account].
  8. Log On As’ field corresponding to the service HCL.iAutomate.iCrawler should be changed to ‘Service Account’.
  9. Click Start to start the service.