Overview

Some of your Agent scans are stuck on "importing scan" status in the Activity Monitor.

Solution

This isn't a scanning error as the scan results are already gathered and are being transferred to the server and imported to the SQL database, where the process is stuck.

Please do the following on the machine where the SQL server with LanGuard backend database is installed:

1. Open the SQL Server Configuration Manager on the SQL Server.
2. Expand SQL Server Network Configuration > Protocols for [Instance name] .
3. Make sure that Shared Memory, Named Pipes, and TCP/IP are enabled.
4. If any of the above was disabled, enable them and restart the SQL Server Services to apply the changes.

If the problem persists, other possible factors can cause the issue:

1. Antivirus scanning or Firewall blocking the process of importing the scan results to the database. Ensure protection engines and firewall exceptions are set according to the KB article Recommended Settings for Best Performance in GFI LanGuard.
2. Corrupted installation leading to the lnsscorollary process taking up excessive CPU. If you see the heavy CPU consumption, follow our guide Fixing GFI LanGuard broken installation or failed upgrade.
3. Installation not meeting system requirements for the number of computers being scanned. Review the minimum system requirements from our guide GFI LanGuard system requirements.
4. Agents not updated correctly. Try purging your update folder.

Testing

Rerun the scan(s). If the issue persists, contact GFI LanGuard Support.