DEKSI Network Inventory vs. Competitors: Which Is Best for Your Business?

Troubleshooting DEKSI Network Inventory: Common Issues and Fixes

Overview

This guide covers frequent problems with DEKSI Network Inventory and step-by-step fixes to restore accurate discovery, reporting, and scanning. Assume a recent Windows Server or workstation environment and DEKSI Network Inventory 3.x–5.x; adapt steps to your version where necessary.

1. Scans fail to start or complete

• Symptom: Scheduled scans don’t run, or manual scans hang/stop.
• Causes: Service not running, corrupted schedule entry, network connectivity, or insufficient permissions.
• Fix:
  1. Restart DEKSI services: Open Services (services.msc) and restart any DEKSI-related services.
  2. Run scan manually: In the DEKSI Console, trigger a manual scan to capture immediate errors.
  3. Check credentials: Ensure the scanner uses an account with administrative privileges on target machines (local admin or equivalent domain credentials).
  4. Verify network access: Ping targets and ensure required ports (SMB/RPC, WMI) are open; test WMI with wbemtest or PowerShell:

     powershell
     Copy CodeCopied
     Test-WmiConnection -ComputerName TargetMachine 

  5. Recreate schedule: Delete and recreate the failing scheduled job in the Console.
  6. Review logs: Check DEKSI log files (Console and agent logs) for error codes and timestamps; correlate with Windows Event Viewer.

2. Targets not discovered or missing devices

• Symptom: Inventory misses hosts, shows incomplete subnet scans.
• Causes: Discovery scope misconfigured, DNS issues, firewalls, or agent deployment problems.
• Fix:
  1. Confirm discovery settings: Ensure correct IP ranges, subnets, and domain/workgroup settings are included.
  2. DNS and name resolution: Verify DNS entries and try discovery by IP instead of hostname.
  3. Firewall rules: Temporarily disable host firewalls or permit necessary protocols (ICMP, SMB/WMI).
  4. Agent deployment check: If using DEKSI agents, confirm they’re installed and reporting. Re-deploy to missing hosts.
  5. Use alternate discovery methods: Try SNMP, Active Directory import, or AD integration to add missing devices.
  6. Scan in smaller batches: Reduce concurrency to avoid network or scanner overload.

3. Incorrect or incomplete hardware/software data

• Symptom: Missing installed applications, wrong OS version, or incomplete hardware details.
• Causes: Limited scan permissions, WMI corruption, or outdated scanner/version.
• Fix:
  1. Update DEKSI: Ensure you run the latest DEKSI build/patch.
  2. Check account privileges: Use an account with permissions to query software/hardware (local admin or WMI-accessible account).
  3. Repair WMI on target: Rebuild WMI repository on affected machines:

     cmd
     Copy CodeCopied
     winmgmt /salvagerepository winmgmt /resetrepository 

  4. Verify Windows Update Agent & Remote Registry: Ensure Remote Registry service and Windows Management Instrumentation are running.
  5. Rescan affected hosts after repairs and compare before/after reports.

4. Agents not reporting or offline

• Symptom: Agents show as offline or last seen long ago.
• Causes: Agent service stopped, network path blocked, or license/activation issues.
• Fix:
  1. Restart agent service on target (e.g., DEKSI Agent Service).
  2. Check registration: Confirm agent is registered with the Console and license is valid.
  3. Network connectivity: Ensure agent can reach the Console server (test TCP connectivity to the Console port).
  4. Reinstall agent: Uninstall and reinstall the agent if persistent; preserve local config if needed.
  5. Logs: Inspect agent logs for authentication or communication errors.

5. Database performance issues or corruption

• Symptom: Slow Console, failed queries, or database errors.
• Causes: Large dataset, fragmented indexes, corrupted DB files, or insufficient resources.
• Fix:
  1. Backup DB: Immediately back up the DEKSI database files.
  2. Compact/Repair: Use DEKSI database maintenance tools or run DB engine repair (depending on DB type: SQL Server/SQLite).
  3. Index rebuilds and maintenance: Rebuild indexes and run integrity checks.
  4. Resource allocation: Move DB to faster storage, add CPU/RAM, or optimize retention settings to reduce size.
  5. Purge old data: Archive or delete outdated scan histories and logs. 6