mfeinman asked a question.
Trying to Extend Active Directory Import Timeout Value But It Doesn't Seem to Have an Effect
Hi all ...
I'm running into the Active Directory import issue described here .
I have repeatedly tried to create the CommandTimeout registry entry and have adjusted the timeout setting, but after I create it and try to run the mgsimport command locally (so I can see the errors, which I can), it still times out after an hour.
Have I created the registry entry correctly? Here's exactly what it looks like:
Here's the command I am running to try and perform the import manually:
- mgsimport -t activedirectory -e c:\temp\myfile.actdir.gz
Here's the ending output where it times out after an hour:
- File c:\temp\myfile.actdir.gz: Unexpected exception in importerFile saved to c:\temp\BadLogs\failureAll tasks are completeFinished importing 1 files in 3640.3sC:\Program Files (x86)\Flexera Software\FlexNet Manager Platform\Importers\bin>
What am I doing incorrectly? I defined CommandTimeout as a string value; should it be something else?
--Mark
@mfeinman
It's difficult for forum members to provide guidance on environment specific issues, you may be better off contacting Flexera Support .
However, maybe you're running into other timeout settings, e.g., did you run a SQL Profiler during the process?
Thanks,
The decimal value should be of type REG_DWORD .
I tried changing the type to REG_DWORD but the AD import is still failing at an hour. I'll open a support ticket.
--Mark
@mfeinman
In the first screen shot it seems your changing the Compliance CommandTimeout, according to documentation FlexNet Manager Suite Online Help - Registry Keys for Inventory Beacon (flexera.com) you have to set the timeouts for an Active Directory import under [Registry]\ActiveDirectoryImporter\CurrentVersionDid you try this already?
I did not try this because the settings you linked to refer to the inventory beacon, but the issue is occurring during the reconciliation process on the FNMS server.
--Mark
To close the loop on this one, I recently upgraded my on-prem instance of FNMS from 2022R1 to 2023R1 (plus the two hotfixes) and this issue appears to have resolved itself without adjusting the timeout value.
--Mark