Troubleshooting for BigFix Runbook AI Installer

This text provides troubleshooting steps for various scenarios related to the BigFix Runbook AI Installer, including issues with the installer not running, database connection failures, and component installation failures. It also includes specific steps to resolve each issue.

Installer exe is not running

Table 1. Table 2 – BigFix Runbook AI Installer: Scenario 1
Issue Description Installer exe is not running
Modules Impacted BigFix Runbook AI Installer

Steps to resolve

  1. Check if antivirus is not stopping the exe from running.
  2. Ensure that the installer file has been unzipped as per the defined procedure and all contents have been extracted successfully.
  3. Refer to the log and exception files (available where the installer has been unzipped) for more information.

“No file found to merge for iAutomateDB/iCustomerDB/ASPState”

Table 2. Table 3 - BigFix Runbook AI Installer: Scenario 2
Issue Description A message appears as “No file found to merge for iAutomateDB/iCustomerDB/ASPState” during the installation
Modules Impacted BigFix Runbook AI Installer

Steps to resolve

  1. Check if antivirus is not stopping the exe from running.
  1. Ensure that the installer zipped file has been unzipped as per the defined procedure and all the contents have been extracted successfully.
  2. Refer to the log and exception files (available where the installer has been unzipped) for more information.

Database Details - Check Connection failure

Table 3. Table 4 - BigFix Runbook AI Installer: Scenario 3
Issue Description Database Details - Check Connection failure
Modules Impacted BigFix Runbook AI Installer

Steps to resolve

  1. Check the connectivity to the database server.
  1. Ensure that the DB port (1443) is open for communication.
  2. Ensure that the username and password are entered correctly.
  3. Refer to the log and exception files (available where the installer has been unzipped) for more information.

Server Configuration – Check User Validity failure

Table 4. Table 5 - BigFix Runbook AI Installer: Scenario 4
Issue Description Server Configuration – Check User Validity failure
Modules Impacted BigFix Runbook AI Installer

Steps to resolve

  1. Check if all the details have been entered correctly.
  1. Ensure that the user has administrator privileges.
  2. Refer to the log and exception files (available where the installer has been unzipped) for more information.

Pre-requisite software checking failure

Table 5. Table 6 - BigFix Runbook AI Installer: Scenario 5
Issue Description Pre-Requisite Checker – Pre-requisite software checking failure
Modules Impacted BigFix Runbook AI Installer

Steps to resolve

  1. Ensure that all the pre-requisite software are installed under the Local System under Registry.
  1. Click Win+R and type regedit.msc to open Registry.
  2. To check the exact path in Registry, refer to installer logs under log folder inside installer. If the user doesn’t have access to Registry, then check in installed programs.

BigFix Runbook AI component installation failure

Table 6. Table 7 - BigFix Runbook AI Installer: Scenario 6
Issue Description Installation (Final Submission) – BigFix Runbook AI component installation failure
Modules Impacted BigFix Runbook AI Installer

Steps to resolve

  1. If the failure is due to database, resolve the issue as per the error message suggests.
  1. If the error is “No module named ‘pip’”, then it could be an issue related with Python installation. Please uninstall python and follow the installation steps again as mentioned in pre-requisite document and ensure that the installation is correct.
  2. If the failure is due to components, ensure that all the pre-requisites are completed. To check the exact error, find the complete command in the installer logs available in the log folder inside the installer.
  3. Run the command in Command Prompt.
  4. For e.g.: -"C:\IAUTOMATE\DATACOLLECTION\SRServices.bat" HCL.iAutomate.DC "C:\IAUTOMATE\DataCollection\DataCollection\HCL.iAutomate.DataCollector.Service.Host.exe"
  5. Repeat steps 3 & 4 for all the respective components.
  6. LISTENER: - <path of bat file> <service name> <path till service folder> <admin email ID> <password>
  7. E.g.: - "C:\IAUTOMATE\LISTNER\SRServices.bat" HCL.iAutomate.Listener "C:\IAUTOMATE\Listner\Listner\HCL.iAutomate.Listner.Service.Host.exe" test@hcl.com 123456
  8. DATACOLLECTOR: - <path of bat file> <service name> <path till service folder> <admin email ID> <password>
  9. E.g.: - "C:\IAUTOMATE\DATACOLLECTION\SRServices.bat"HCL.iAutomate.DC "C:\IAUTOMATE\DataCollection\DataCollection\HCL.iAutomate.DataCollector.Service.Host.exe" test@hcl.com 123456
  10. IRECOMMEND: - <path of bat file> <path till iRecommend folder> <drive letter>: <port> <admin email ID> <password>
  11. E.g.: - "C:\IAUTOMATE\iRecommend\recommendBatch\irecommend_batch.bat" "C:\IAUTOMATE\iRecommend\recommendBatch" C: 9000 test@hcl.com 123456
  12. Entity: - <path of bat file> <path till entity folder> <drive letter>: <port> <admin email ID> <password>
  13. E.g.: - "C:\IAUTOMATE\iRecommend\batchFile\entity_batch.bat" "C:\IAUTOMATE\iRecommend\batchFile" C: 9003 test@hcl.com 123456
  14. IPARSE: - <path of bat file> <path till iparse folder> <drive letter>: <port> <admin email ID> <password>
  15. E.g.: - "C:\IAUTOMATE\iParse\iparse_batch.bat" "C:\IAUTOMATE\iParse\\" C: 8006 test@hcl.com 123456
  16. GENERIC SERVICE: - <path of bat file> <service name> <path till service folder> <admin email ID> <password>
  17. E.g.: - "C:\IAUTOMATE\GENERICSERVICE\SRServices.bat" HCL.iAutomate.GenericExecutor "C:\IAUTOMATE\GenericService\GenericService\HCL.iAutomate.Generic.Host.exe" test@hcl.com 123456
  18. RBA SERVICE: - <path of bat file> <service name> <path till service folder> <admin email ID> <password>
  19. E.g.: - "C:\IAUTOMATE\RBA\SRServices.bat" HCL.iAutomate.RBAComponent "C:\IAUTOMATE\RBA\RBA\Hcl.RbaService.Component.Host.exe" test@hcl.com 123456
  20. IRELEASE: - <path of bat file> <service name> <path till service folder> <admin email ID> <password>
  21. E.g.: - "C:\IAUTOMATE\RELEASESERVICE\SRServices.bat" HCL.iAutomate.ReleaseService "C:\IAUTOMATE\ReleaseService\ReleaseService\HCL.iAutomate.Release.Host.exe" test@hcl.com 123456
  22. IUNIQUE: - <path of bat file> <path till iUnique folder> <drive letter>: <port> <admin email ID> <password>
  23. E.g.: - "C:\IAUTOMATE\iUnique\iUnique\iunique_batch.bat" "C:\IAUTOMATE\iUnique\iUnique" C: 8009 test@hcl.com 123456
  24. ISCRIPT: - <path of bat file> <path till iScript folder> <drive letter>: <port> <admin email ID> <password>
  25. E.g.: - "C:\IAUTOMATE\iScript\iScript\iscript_batch.bat" "C:\IAUTOMATE\iScript\iScript\" C: 8030 test@hcl.com 123456
  26. IKOWLEDGE BASIC: - <path of bat file> <path till iKnowledge folder> <drive letter>: <port> <admin email ID> <password>
  27. E.g.: - "C:\IAUTOMATE\iKnowledge\iKnowledge\iknowledge_batch.bat" "C:\IAUTOMATE\iKnowledge\iKnowledge" C: 8024 test@hcl.com 123456
  28. IKNOWLEDGERATING: - <path of bat file> <path till crawler folder> <drive letter>: <port> <admin email ID> <password>
  29. E.g.: - "C:\IAUTOMATE\KnowledgeRating\KnowledgeRating\Rating.bat" "C:\IAUTOMATE\KnowledgeRating\KnowledgeRating\\" C: 8027 test@hcl.com 123456
  30. ICRAWLER: - <path of bat file> <path till crawler folder> <drive letter>: <port> <admin email ID> <password>
  31. E.g.: - "C:\IAUTOMATE\ADVANCEKNOWLEDGE\Crawler\crawler_install.bat" "C:\IAUTOMATE\ADVANCEKNOWLEDGE\Crawler\" C: 9019 test@hcl.com 123456
  32. Batch script to install IKNOWLEDGEINDEXER, IKNOWLEDGESCREENS, IKNOWLEDGESEARCH
  33. <path of bat file> <path till crawler folder> <drive letter>: <port> <admin email ID> <password>
  34. E.g.:- "C:\IAUTOMATE\ADVANCEKNOWLEDGE\\iKnowledge_batch.bat" "C:\IAUTOMATE\ADVANCEKNOWLEDGE\” C: 9009 9013 9016 test@hcl.com 123456

Database execution failure

Table 7. Table 8 - Product Installer: Scenario 6
Issue Description Installation (Final Submission) – Database execution failure
Modules Impacted Product Installer

Steps to resolve

  1. If the failure is due to database, check the error.
  1. If the error reads - “Violation of UNIQUE KEY constraint 'IX_CodeMaster'. Cannot insert duplicate key in object 'dbo.CodeMaster'. The duplicate key value is (secret manager).”, then the issue is due to multiple times of execution of DB scripts.
  2. To resolve this error, go to iAutomateDB database, and run the below command.

    IF EXISTS (SELECT 1 FROM CodeMaster WHERE Code='secret manager')

    BEGIN

    DELETE FROM CodeMaster WHERE Code='secret manager'

    END

    GO

  3. After executing the above script, run the installer again.
  4. If the same issue persists, then perform above steps again.