Attempts to upload and import .actdir files containing data extracted from Active Directory may take a long time, or even timeout and fail. If a timeout occurs, data that would otherwise be imported from Active Directory (such as user & computer details, group details, and subnet details) may not be up to date.
This issue can occur if importing Active Directory data results in many records being changed, particularly if many computer or organizational unit records need to be removed. In such a scenario, the substantial updates that need to be done in the database may not be able to be completed before a database timeout occurs.
When database timeouts occur importing Active Directory data, files with an extension of .actdir.gz are likely to accumulate under the following folder on the inventory server of a FlexNet Manager Suite system: C:\ProgramData\Flexera Software\Incoming\ActiveDirectory\BadLogs. An environment where Active Directory data is successfully being imported should have no accumulation of files under the Incoming\ActiveDirectory directory.
Database timeouts that occur when attempting to import Active Directory data files that are uploaded will often be noted in the dispatcher.log file on the inventory server with logging like the following:
[ERROR 2020-08-20 01:39:53,866 26901384ms Dispatcher ] Failed to run importer System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Reconciling Organizations in DC=acme,DC=com Reconciling Computers in DC=acme,DC=com
The primary symptom that this issue is occurring with Flexera One ITAM is that data imported from Active Directory is not up to date.
See the following article for guidance on activities that can be performed to mitigate this issue: Mitigating slow or timing out imports of Active Directory .actdir files
See the following page for information about data that is imported from Active Directory: What Active Directory data elements are imported by FlexNet Manager Suite?
This issue has been fixed in the following FlexNet Manager Suite releases: 2022 R2.1 / Jan 2023 (Cloud), 2023 R1 (On Premises)
Affected components: Integration: Active Directory, Uploaded file importers
Master issue ID: IOJ-2250105
Also known as: FNML-75762
Oct 14, 2022 02:37 AM - edited Nov 20, 2023 01:28 PM
The link for "Mitigating slow or timing out imports of Active Directory .actdir files " under "Additional Information" is wrong. It should go here: https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/What-Active-Directory-data-elements-are-imported-by-FlexNet/ta-p/6030
--Mark
Is this a known issue across all releases? All currently supported releases? It might be helpful to clarify scope.
Best,
David
NTT DATA Services
Thanks @mfeinman - we'll get that link corrected.
@dmathias - I expect this issue has the potential to affect any versions of FlexNet Manager Suite (up to the fixed version).