Troubleshooting: Inventory Not Uploading

FlexNet Manager Suite 2022 R2 (On-Premises)

Problem: Inventory from a target machine or from an inventory adapter does not upload.

Inventory failures may relate to:
  • Problems with the inventory adapter running for a particular connection
  • Issues related to the target discovered device
  • Problems with the inventory beacon, or its connection to the central application server
  • Inventory imports
  • Inventory with a date that is "out of band".

Initial Diagnosis

  1. Is your inventory beacon not working at all?

    If all the data sources from a particular inventory beacon are failing to appear in your central database, there may be a problem with the inventory beacon connecting to the central application server. For details, see Connection to FlexNet Manager Suite.

  2. Are you missing large volumes of expected data?

    If you have several data inputs that run in sequence, and one inventory adapter in the sequence loads bad data, the inventory import fails at that point. All subsequent inputs are blocked. Furthermore, the bad upload is left in the IntermediateData folder on the central application server, and will continue to block future inventory imports. For details, see Troubleshooting: Unblocking an Inventory Data Source.

  3. When you examine content from an inventory source, are many of the records very old?

    It is likely that this inventory adapter has loaded bad data which fails at import. For details, see Troubleshooting: Unblocking an Inventory Data Source.

  4. Is the date of the failed inventory out of band?
    Inventory data is considered out of band when either of the following conditions apply:
    • The date of the inventory is older than a more recent inventory from the same source that has already been processed
    • The date of the inventory is more than one day into the future (the one day margin allows for date variations when data is collected from different time zones around the world).
    In either of these cases, the intermediate inventory file is not resolved into the inventory database.
  5. Is the failed target device an application server for FlexNet Manager Suite?
    If you intend to collect inventory from your FlexNet Manager Suite application server(s), they must be treated as target device(s) in either of the following ways:
    • Install FlexNet inventory agent on each application server and configure it to transfer the inventory file(s) to a separate standalone server before uploading it back to the central application server.
    • Use remote inventory collection, known as zero-footprint, by targeting application server(s). This method temporarily installs an agent on the target device(s) and removes the agent afterward collecting and uploading inventory.
  6. Is there another specific target device from which the inventory is not being updated?

    There may be a failure in inventory gathering on that device, which therefore is not being included in your inventory uploads. For details, try Troubleshooting: Inventory Missing for a Target Device (and drill through to details of error messages on target devices).

  7. Is inventory failing to upload from the FlexNet inventory agent to the application server for UNIX-like platforms?

    The generated .ndi files will not upload to the application server if the user name of the account running contains a hash (#) character. Check and modify the user name if required.

FlexNet Manager Suite (On-Premises)

2022 R2