cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Description

This error indicates that the asset was successfully scanned using SNMP in the past, but the most recent scan was unable to establish an SNMP connection. As a result, Lansweeper could not update the existing SNMP data for the asset.

Primary Causes

This issue typically occurs when:

  • SNMP credentials are missing, incorrect, or no longer valid
  • SNMP credentials are not properly mapped to the asset or its IP range
  • SNMP access is no longer available on the device (configuration or network change)

Resolution Steps

1. Verify SNMP Credentials

Ensure that an SNMP community string has been configured and has sufficient access to the target device.

  • Confirm the SNMP credential is added under Scanning > Scanning Credentials
  • Verify that the credential is either:
    • Set as a global credential, or
    • Mapped to an IP range scanning target that includes the device

Create or update credentials as needed:
https://community.lansweeper.com/t5/scanning-your-network/create-and-map-scanning-credentials/ta-p/6...

2. Validate Credential Accuracy

Double-check that the configured SNMP community string (and SNMP version, if applicable) exactly matches the configuration on the target device.

3. Test SNMP Connectivity with DeviceTester

Run a manual SNMP test from the Lansweeper server to help identify the root cause.

  • Launch Devicetester.exe from:
    Program Files (x86)\Lansweeper\Actions\Devicetester.exe
  • Test the connection using the configured SNMP scanning credentials

The output can provide additional details on why the SNMP connection is failing.

More information on using DeviceTester:
https://community.lansweeper.com/t5/troubleshooting-scanning-issues/troubleshoot-device-scanning-iss...

4. Review SNMP Scanning Requirements

Confirm that the device and network meet all requirements for SNMP scanning:

Summary

To resolve the “Scan Incomplete – SNMP was not scanned, but existing record has SNMP info” error:

  1. Verify that valid SNMP credentials exist and are correctly mapped.
  2. Confirm the accuracy of the SNMP community string and related settings.
  3. Use DeviceTester to diagnose connectivity or authentication issues.
  4. Review SNMP scanning requirements and configuration.
Was this article helpful? Yes No
No ratings

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now
Version history
Last update:
2 hours ago
Updated by: