Troubleshooting Active Directory Inspector Errors

Occasionally, the Active Directory Inspector may fail with the following error:

The inspector job exited with a non-zero exit code. | Error: Error occurred running the inspector. Exit code was 1 and signal was null (node:5824) ExperimentalWarning: Policies are experimental.

(Use `node --trace-warnings ...` to show where the warning was created)

If you encounter this error, there are a few steps you can take to resolve it.

1. Check the Agent Machine

The first step is to check the agent machine where the Active Directory Inspector is running. To do this, follow these steps:

a. Open the inspector configuration page by navigating to Admin > Inspector > Active Directory > Select your system > Click on the three dot buttons beside the same > Edit.

b. Take note of the Agent name.

c. Log on to the agent machine and open Powershell with Admin Privileges.

d. Run the following command:

This will check the Execution Policy of the local machine.

If the Execution Policy is restricted, run the following command to change it to RemoteSigned:

e. Restart the Liongard agent service by accessing services.msc.

2. Run the Inspector in Debug and Clear Cache Mode

Once you have checked and potentially changed the Execution Policy on the agent machine, the next step is to run the Active Directory Inspector in debug and clear cache mode. This will help to identify any specific issues that may be causing the error.

To do this, follow the steps outlined in our Inspectors: How to Run in Debug and Clear Cache article.

If you continue to experience issues with the Active Directory Inspector, please reach out to our support team for further assistance.