Troubleshooting Microsoft Office 365 (Deprecated) Connector Imports from Office 365

FlexNet Manager Suite (Cloud)
Important: The troubleshooting in this section applies to connections to Microsoft Office 365 using the Microsoft Office 365 (deprecated) connector. For help with troubleshooting connections using the Microsoft Office 365 connector, see Troubleshooting Microsoft 365 Connector Imports from Microsoft 365.

This process traces the path of data imported from Microsoft 365 Online Service through an inventory beacon to the central application server of FlexNet Manager Suite. You may pick up at any stage of the process as needed for your particular symptoms.

To troubleshoot imports from Microsoft 365 Online Service:

  1. Validate that you have licensed the FlexNet Manager for Datacenters product:
    1. Navigate to the system menu ( in the top right corner) in the web interface for FlexNet Manager Suite, and click FlexNet Manager Suite License.
    2. In the Licensed products section, scroll down to see the card for FlexNet Manager for Datacenters.
    Inventory from a connection to Microsoft 365 Online Service cannot be imported or uploaded by an inventory beacon without this license term being registered on the central application server. If it is missing, please contact your Flexera representative for assistance.
  2. Validate imports to the inventory beacon:
    1. On the inventory beacon that connects to Microsoft 365, log into FlexNet Beacon using an account with administrator privileges.
    2. On the Inventory Systems page, select your connection to Microsoft 365, and click Execute Now
      A confirmation shows that the extract has started. A typical import may take 2-3 minutes.
    3. In the very top-left corner of the FlexNet Beacon interface, right-click the menu icon, and select Open log file folder.
      File Explorer opens.
    4. Ensure that you are viewing the ProgramData\Flexera Software\Compliance\Logging\ComplianceReader folder.
    5. In Notepad, open the text document importer-[nnnn] that was modified on today's date, and scroll to the bottom.
      If the reading of data is still in progress, exit from Notepad, and try again in a few minutes.
    6. 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, instead, there are warnings or errors in the log file, try to correct the issues. If all else fails, save the log file to include with a Support ticket for Flexera. Typical issues at this stage may include:
      • Proxy or firewall settings preventing access to the Internet
      • Intermittent issues with the Internet or access to the Microsoft 365 portal
      • Incorrect details for the account name or password accessing the portal (see Creating Connections Using the Microsoft Office 365 (Deprecated) Connector for details of configuring this account)
      • The connection has not been regularly scheduled (see the same topic), and so succeeds only when executed manually.
      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 central application server):
      • When the upload succeeds, the inventory beacon also saves a copy in C:\ProgramData\Flexera Software\Beacon\IntermediateData\Uploaded, and preserves this copy for 14 days
      • If the upload fails, the imported archive stays in C:\ProgramData\Flexera Software\Beacon\IntermediateData.
        Tip: If you are working on a disconnected inventory beacon (one that cannot access the central application server), this IntermediateData folder contains the data files that you must transfer to another location where uploads are possible.
    7. To review the data imported from Microsoft 365, navigate to C:\ProgramData\Flexera Software\Beacon\IntermediateData\Uploaded, and inspect the most recent relevant .zip file there.
      Tip: If the zip archive remains in the IntermediateData folder (on a connected inventory beacon), there is an upload problem, as discussed below.
  3. 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:
    dateTime [Upload.UploadProcess  ] [INFO] Uploading to http...
  4. 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. Once the case has been saved, your support contact can use the Upload button (in the Attachments section at the bottom) to attach your prepared zip archive of logs.

FlexNet Manager Suite (Cloud)

Current