Production of mgr files by script

[JCourt]

Bonjour,
We use the attached script "S1-Fait_mgr_objets_et_liens_plus_de_100_obj.vbs" to produce mgr files for exporting a list of objects.
For the export of around 600 objects, a first version of this script showed saturation/blocking problems. The attached script is the second version, which splits the objects into packets of a hundred to optimize execution. This script works well on a development server.
However, on a pre-production server, it remained blocked when generating the mgr file of links for the 2nd hundred objects.
This is the line on which the block seems to have occurred:

collObj.Extract("ALLDIRECTASSOCIATIONS").SaveAs chDossierTravail & "\Export_liens_" & iNb & ".mgr"

collObj is the collection of objects to be exported.

Would you have an idea on how to use the functions in this line, or equivalent functions, without causing a block?

Would adding functions to the "MacroCreateObjectWhitelist.json" file, or an equivalent file, solve the problem?
Probable location of this file :
C:\ProgramData\MEGA\Hopex Application Server\[Instance_number]\.shadowFiles\has.custom\[Version]\hopex.core\Mega_Std\MacroCreateObjectWhitelist.json

For your information, I'm currently using this version of HOPEX: Aquila 6.1 SP2 CU3

Thank you very much in advance for your help.
Yours respectfully

[JCourt]

Bonsoir,
I still haven't found a solution.
Since then, I've noticed that when the script is running, logs are recorded in the sspsprvs[yyyymmdd].txt file.
These include the following messages:
"MultiReader":"Excessive recursive multi reader invoke frequency","Count":"10000","Duration":"0.31","Frequency alert threshold":"10000"
The presence of these messages does not mean that the script is going to crash, because in the development environment these messages are found, but the script works. It may, however, be a clue explaining why the script crashes on our pre-production server.
So if you have any ideas for tests or other solutions, I'm always interested!
Thanks again.

[JCourt]

Bonjour,
Since my last message, I've been able to compare the "MacroCreateObjectWhitelist.json" files for the two environments, development and pre-production. They are identical. So that doesn't seem to be where the problem lies.
The block seen in pre-production hasn't left any log in the "megaerr[yyyymmdd].txt" file either.
If you have any leads, I'm always interested, as the blocking hasn't been resolved yet.
Many thanks again in advance!