1.2.0.0 Version kicks certain AD Groups out

[Den]

So far, the 1.2 works great. Thanks so much!

I've found only one issue however:

When the file has been converted and moved to a destination (output) folder, the file doesn't keep the same Active Directory groups as the original file. The only workaround was to deactivate the "Move source instead of copy" option inside the Delivery node.

Info: the original file has 14 AD Groups on it, after the conversion the FFastrans kicks 4 groups out.

Thanks once again for your work!

Keep well

[emcodem]

Hi Den,

thanks for the report!
The deliver node tries different move methods in certain cases.
Is it possible for you to share the full_log.json of some an affected log with us, best with log level debug turned on? This is just to sure which of the tried methods was applied for you.

Thanks!

[Den]

Hi!

Thanks for the reply and for looking into it! Please find enclosed the log files.

Cheers

[emcodem]

Great, thanks a lot for this!

So you move from here:
\\%IP_ADDRESS%\root\Transcoding\

To here:
T:\Transcoding\Transcoding_Beta\

From the time that the move needs (like NO time), i interpret that it is the same volume which implies that the file permissions should be kept normally. Could you try to specify the full unc path for both, source and target please?
Just a sidenote, it is not good practice to use "mapped network drives" in general for any automation stuff as you cannot run it as windows service later if you wish to. Better always use full UNC paths everywhere.

Thanks!