Skip to main content

NIM Troubleshooting

Support guide

Start with the symptom you see in NIM. Each path explains the likely cause and the next action to take.

Permissions and Microsoft Defender allow-listing are common sources of setup issues. Review the installation guidance before investigating a system-specific problem.

Troubleshooting​

A system collection remains in a Busy state​

Problem

A system collection remains in a Busy state

Likely cause

An incomplete or stalled import is still recorded in the system's collection history.

Resolution

  1. Open the system's collection history using the icon.
  2. Locate the latest import with a Busy status.
  3. Delete that import using the icon.
  4. Return to the system overview and refresh it to confirm the status has cleared.

A filter is marked invalid​

Problem

A filter is marked invalid

Likely cause

Filters become invalid when referenced configuration, system data, relations, validation settings, or licensing changes.

Invalid filters show a red underline and No in the Valid column.

Resolution

  1. Check the filter configuration and its selected columns.
  2. Check the systems and collected source data.
  3. Check intra- and inter-system relations.
  4. Open the Validation screen for configuration errors.
  5. Verify the installed license is valid.

If a correction is not reflected, refresh the browser, choose Reload all in Systems Overview, or restart the NIM service.

The filter has missing selections or column errors​

Problem

The filter has missing selections or column errors

Likely cause

A referenced relation, column, table name, or display name has changed or been removed.

Resolution

  • Missing relation: Recreate the relation named in the error. Missing relations typically leave blank selections in the filter.
  • Missing ordering or selection column: Select a replacement column, restore the data column, or recreate the removed script column.
  • Duplicate table name: Rename one table, preferably the newest, to avoid disrupting existing assignments.
  • Duplicate display name: Give one column a distinct display name. This does not affect other NIM processes, but it changes the name shown in exports.

Filter errors point to a system, table, or source column​

Problem

Filter errors point to a system, table, or source column

Likely cause

The system, table, or column may have been removed; the system may have no current data; collection may have failed; or relation keys may use incompatible data types.

Resolution

  1. In Systems Overview, select Reload all.
  2. After reload, review the system's Status column. Select the icon to inspect errors.
  3. Open the affected table and resolve any load errors, such as unavailable columns, inconsistent CSV rows, empty trailing rows, or invalid script columns.

A required relation is missing or no longer works​

Problem

A required relation is missing or no longer works

Likely cause

An intra-system or inter-system relation was deleted, or the columns used by it were renamed.

Resolution

  1. For an intra-system relation, open the affected table and recreate the missing relation.
  2. For an inter-system relation, open Relations and search for it.
  3. If it is absent, create the relation. If it exists but still fails, delete it, save, and create it again after verifying the linked columns.

NIM reports a configuration or validation error​

Problem

NIM reports a configuration or validation error

Likely cause

A NIM item is configured incorrectly even though the filter or system itself appears valid.

Resolution

  1. Open the Validation screen.
  2. Select the item description to open the configuration item directly.
  3. Correct the reported configuration and validate again.

All filters suddenly become invalid​

Problem

All filters suddenly become invalid

Likely cause

The NIM license key is invalid or has expired.

Resolution

  1. Review the installed license and confirm its validity.
  2. If it is invalid or expired, contact Tools4ever for help resolving the issue.

NIM needs to be restarted after a correction​

Problem

NIM needs to be restarted after a correction

Likely cause

A configuration or data change has not yet been picked up by the NIM service.

Resolution

  1. Open the Windows Services console.
  2. Find and select NIM Service.
  3. Select Restart, then retry the affected action.