No asset created for scanned computer or device

Lansweeper can pull data from any device that has one or more of the following protocols enabled: Bonjour, FTP, HTTP, HTTPS, JetDirect, MOB (Managed Object Browser), SIP, SMTP, SNMP (SNMPv1, SNMPv2 or SNMPv3), SSH, Telnet or WMI. When Lansweeper scans a device that has one of these protocols enabled, an asset is automatically generated and added to the Lansweeper database and web console. Assets can also be generated for pingable machines that do not have any of the aforementioned protocols enabled, by ticking the Save Pinged IP option for the machines' IP ranges.

If no asset is generated for a scanned computer or device, this can have several possible explanations. The troubleshooting steps below help you determine why a particular device has no associated asset, as well as provide solutions for various causes. This article applies to all types of assets: Linux, Unix, Mac and Windows computers, VMware servers and other network devices like printers and switches.

If you've attempted to scan a computer or device, but cannot locate an asset for it in the web console, do the following:

  1. Perform searches for the machine's name, IP address and MAC address in the web console search bar, to double-check whether an asset exists.
    performing a search for an asset in the web console search bar
  2. If you have not already done so, update to the latest Lansweeper release by following the instructions in this knowledge base article. Lansweeper is regularly updated with enhancements and new features. You can verify whether you are on the latest release by hitting the Check for Updates now button in the following section of the web console: Configuration\Your Lansweeper License
  3. Start the Lansweeper Server service in Windows Services on your Lansweeper server, if not already started. The Lansweeper service is what scans your network and sends scanned data to your database. By default, the Lansweeper service is automatically started, but someone may have manually stopped it.
    starting the Lansweeper Server service
  4. Browse to the Configuration\Your Lansweeper License section of the web console and make sure the Licensed Assets count does not exceed the asset limit specified on the same page or in the terms of your Lansweeper license.
    checking Lansweeper license asset limit
    Most Lansweeper licenses limit the number of assets you can scan. Once you've reached your licensed asset limit, scanning of new and existing assets stops until you delete some assets or upgrade your license. Any non-monitor assets listed when you click the Assets link at the top of the web console count towards your asset limit. Your Licensed Assets count indicates how many non-monitor assets have already been scanned and have been counted towards your limit.
  5. Review the Scanning Status widget in the Main page of the Dashboard and make sure your database hasn't reached its size limit, if it has one. If you've reached your size limit, the scanning service cannot write additional assets to the database and you'll need to perform a database cleanup to continue scanning.
    checking Lansweeper database size limit
    Your Lansweeper database is hosted in either Microsoft SQL Compact or Microsoft SQL Server. SQL Compact databases are limited to 4GB of data by Microsoft. Express (freeware) editions of old SQL Server versions are also limited to 4GB, while Express editions of newer SQL Server versions (2008 R2 and beyond) are limited to 10GB. There are of course non-Express editions of SQL Server as well, which are not limited in size.
  6. Make sure the server hosting your Lansweeper database has sufficient disk space left.
    checking Lansweeper database server disk space
  7. Run Command Prompt on your Lansweeper server and ping the problem client machine to make sure it's online.
    pinging a machine in Command Prompt
  8. Hit the Add Scanning Target button in the Scanning\Scanning Targets section of the web console and submit the machine's IP range in the popup window, if the same range was not already submitted for scanning.
  9. Make sure Save Pinged IP is checked.
  10. If the machine is a Linux, Unix, Mac or Windows computer, make sure Ignore Windows and No SSH are *not* checked. Hit Ok to submit the range.
    submitting an IP range for scanning
  11. Make sure the machine has *not* been excluded from scanning in the Scanning Exclusions section of the same page. The machine could be excluded based on name, domain, IP address, IP range or asset type.
    checking scanning exclusions
    Pay attention to wildcards used in Windows Computer exclusions. In the example above, any Windows computer whose name contains the word "LAN" will not be scanned.
  12. If the machine is a Linux, Unix, Mac or Windows computer, VMware server or SNMP enabled network device, hit the Add new Credential button in the Scanning\Scanning Credentials section of the web console and submit an appropriate scanning credential. Information on rights required by each type of credential can be found in this knowledge base article.
    adding a scanning credential
  13. Hit the + Credential button next to the machine's IP range in the Credential Mapping section of the page, select the credential you created earlier and hit Add
    mapping a scanning credential
  14. Make sure the machine meets the other scanning requirements for machines of its type. Detailed requirements can be found in these knowledge base articles:
  15. Hit the Scan now button next to the machine's IP range under Scanning\Scanning Targets, wait for your queue to clear under Scanning\Scanning Queue and perform another search for the machine in the web console search bar.
    scanning an IP range

Related Articles