HCL.iAutomate.iScript service is not starting

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

Resolution Steps:

  1. Check for existence of the file iScript.conf at location <Apache_Root_Folder_Path>/conf.
  2. For e.g. - “C:/Apache24/conf” has <Apache_Root_Folder_Path> as “C:/Apache24”
  3. Verify the contents of file iScript.conf by checking the snippet with paths to << iScript_Directory>>. Verify and change the <VirtualHost *> tag with correct path entries to << iScript_Directory>> as shown below. Where << iScript_Directory>> is “C:/iAutomate/Comp/HCL.iAutomate.iScript” in the snippet from iScript.conf
    <VirtualHost *>
    WSGIScriptAlias /iAutomate C:/iAutomate/Comp/HCL.iAutomate.iScript/iScript/app.wsgi
    SSLVerifyClient require
    SSLVerifyDepth 10
    <Directory C:/iAutomate/Comp/HCL.iAutomate.iScript/ iScript>
    WSGIApplicationGroup %{GLOBAL}
    Require all granted
    </Directory>
    </VirtualHost>
  4. Ensure that service was created through Service Account and not through Local Account. Refer to the figure below to check the status.
    Figure 1. HCL.iAutomate.iScript service is not starting
    1
  5. If not, open Windows Command Prompt in Administrator mode and run the below command:
    sc config HCL.iAutomate.iScript obj= “ID” password= “PSWD”
    where ID is the [Domain\SA ID] and PSWD is the [Password of SA] and SA is
    [Service Account].

    Log On As’ field corresponding to the service HCL.iAutomate.iScript should be changed to ‘Service Account’. Click Start to start the service.