LsPush scan files failing to import

Lansweeper includes several scanning methods to scan the assets in your network. You can scan the Linux, Unix, Mac and Windows computers, VMware servers and other devices in your network without installing any Lansweeper software on the machines you're scanning. For computers, you can optionally choose to perform your scans with a scanning agent, however. Lansweeper has two scanning agents for Windows computers, LsPush and LsAgent.

LsPush is a small executable that, when run on a Windows computer, scans the computer locally. LsPush scan results can be sent directly to your Lansweeper server for automatic processing or stored in a file, which can be imported into your Lansweeper installation later on. If you choose to store LsPush results in files, these files must be placed in the import folder on your Lansweeper server, where they are automatically processed. When the files have disappeared from the import folder, the import process has completed and the machines can be found in the web console. However, import may fail if for instance changes are made to the scan files prior to import. This article explains how to troubleshoot in cases where you place an LsPush file in the import folder and no data or feedback appears in your Lansweeper web console at all.

If you've placed LsPush scan files in the import folder but the files fail to disappear or disappear without visual feedback in the web console, do the following:

  1. 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
  2. Grab the latest LsPush executable from the folder below on your Lansweeper server and make sure you are using this LsPush version in your scripts, policies or other LsPush processes.
    Program Files (x86)\Lansweeper\Client
  3. Start the Lansweeper Server service in Windows Services on your Lansweeper server, if not already started. The Lansweeper service is what processes LsPush files. If this service isn't started, no LsPush files can be imported. By default, the Lansweeper service is automatically started, but someone may have manually stopped it.
    starting the Lansweeper Server service
  4. Make sure you are placing the LsPush files in the import folder below on your Lansweeper server.
    Program Files (x86)\Lansweeper\Service\import
    LsPush import folder
  5. 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. 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.
    checking Lansweeper license asset limit
  6. Make sure your Windows computers have *not* been excluded from scanning in the Scanning Exclusions section of the Scanning\Scanning Targets menu. The machines could be excluded based on name, domain, IP address, IP range or asset type. Pay attention to wildcards used in Windows Computer exclusions. In the example below, any Windows computer whose name contains the word "LAN" will not be scanned or imported.
    checking scanning exclusions
  7. Make sure no changes are made to the extension or contents of the LsPush files prior to them being placed in the import folder. File changes can cause import failures.
    Keep in mind that LsPush files are compressed and hence not human-readable in their raw form. The Lansweeper scanning service decompresses and reads the data when the files are imported. The contents of LsPush files not being human-readable is not in itself a sign of file corruption.
  8. If they are being sent via email, make sure no changes are made to the LsPush files by anti-virus scanners you may be using. Anti-virus software may scan your LsPush files and add a line to them indicating that they're safe. If this happens, the files have changed and will fail to import. You can try excluding LsPush files from anti-virus scanning or send them to your Lansweeper server in a different way.
  9. Perform a search for a problem Windows computer's name in the log file below, which can be found on your Lansweeper server. This log may contain errors similar to the ones listed below. If so, your LsPush files are likely corrupt due to one of the reasons previously mentioned.
    Program Files (x86)\Lansweeper\Service\Errorlog.txt
    Cannot import file
    Cannot import: Data at the root level is invalid. Line 1, position 1.
    Could not retrieve AssetID from Assetunique
    Failed to construct a huffman tree using the length array. The stream might be corrupted.
    Found invalid data while decoding.
    The CRC in GZip footer does not match the CRC calculated from the decompressed data.
    The magic number in GZip header is not correct. Make sure you are passing in a GZip stream.
  10. Rescan the Windows computers with LsPush to generate new scan files, and place them in the import folder again.

Related Articles