Validating Imports to the Inventory Beacon

FlexNet Manager Suite (Cloud)
This process traces the path of data imported from Tanium through an inventory beacon, to the central application server of FlexNet Manager Suite. You may start this process at whichever stage is suitable to your needs.

To validate imports to the inventory beacon:

  1. On the inventory beacon that connects to Tanium, log into FlexNet Beacon using an account with administrator privileges.
  2. On the Inventory Systems page, select your connection to Tanium, and click Execute Now.
    A confirmation shows that the extract has started.
  3. In the top-left corner of the FlexNet Beacon interface, right-click the menu icon, and select Open log file folder.
    Windows File Explorer opens.
  4. Ensure that you are viewing ProgramData\Flexera Software\Compliance\Logging\ and then navigate to the ComplianceReader folder.
  5. In the text editor of your choice, open the text document importer-[nnnn] that was modified on today's date, and scroll to the bottom to determine whether data reading is complete. If not, exit the text editor, and try again in a few minutes.

    A successful process shows the following at the end of the log file (with each line prefixed with the date and time):

    [INFO] 0 source data warnings
    [INFO] 0 errors, 0 warnings
    [INFO] Import has been completed successfully

    If there are warnings or errors in the log file, try to correct the issues. If you are unable to correct the error, save the log file and attach it to a support ticket. Typical issues at this stage may include:

    • Proxy or firewall settings preventing access to the Internet
    • Intermittent issues with the Tanium server
    • Incorrect details for the account name or password accessing Tanium
    • The connection has not been regularly scheduled and so succeeds only when executed manually.
    Note: Immediately after a successful import is completed, the inventory beacon attempts to upload the archive of imported data to its parent (the parent may be another inventory beacon in the hierarchy, or the application server):
    • When the upload succeeds, the inventory beacon saves a copy in your default drive at <Drive>:\ProgramData\Flexera Software\Beacon\IntermediateData\Uploaded and preserves this copy for 14 days
    • If the upload fails, the imported archive stays in <Drive>:\ProgramData\Flexera Software\Beacon\IntermediateData.
    Tip: If you are working on a disconnected inventory beacon (one that cannot access the application server), this IntermediateData folder contains the data files that you must transfer to another location where uploads are possible.
    You may now want to review or debug the imported data. To review the data imported from Tanium:
    1. Navigate to <Drive>:\ProgramData\Flexera Software\Beacon\IntermediateData\Uploaded, and inspect the most recent relevant .zip file there. If the zip archive remains in the IntermediateData folder (on a connected inventory beacon), there is an upload problem, as discussed below.
    To debug uploads from this inventory beacon to its parent:
    • Review C:\ProgramData\Flexera Software\Compliance\Logging\ComplianceUpload\upload.log for details of any networking issues and note the URL of the next server in the upload chain. If this is another inventory beacon, repeat these reviews there, and so on until you exhaust the hierarchy of inventory beacons.

    The upload URL is in a log line that starts with dateTime [Upload.UploadProcess ] [INFO] Uploading to http

    If you are unable to resolve problems, collect your logs together in a zip archive. Ask your registered support contact (a designated person within your enterprise who has access rights and login details) to open a new support case at https://community.flexera.com/t5/forums/postpage/board-id/@support, including a clear description of the issue.

FlexNet Manager Suite (Cloud)

Current