Error:
NATIVEFILEDESC and NATIVEFILESIZE were not being updated for a native import using a .DLF. During troubleshooting we tried setting HASNATIVEFILE to null to force re-population during validation. Upon this failing to work we found errors in the Eclipse Admin log file indicating that DLLs were missing. Michael Delgado was able to find the same error messages on his testrack. We found that Eclipse.Domain.dll, Nucleus.Cryptography.dll, and Nucleus.Cryptography.Interfaces.dll were missing from the C:\Program Files\Ipro Tech\Eclipse\Admin\File Identification directory.

Resolution:
We added DLLs sourced from a testrack running 2017.3.4 to the client's File Identification directory. We then had to set HASNATIVEFILE to null for the affected documents in order for the fields to be properly populated during validation. The issue was then resolved.

Errors pointing to missing DLLs:

2017-08-28 15:39:52.9802 [1] ERROR EclipseFileIdentification.Program - Main Could not load file or assembly 'Eclipse.Domain, Version=17.3.20110.4, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.* at EclipseFileIdentification.Program.InitializeSession(CommandInfo info)
at EclipseFileIdentification.Program.Main(String[] args)

2017-08-28 15:51:33.4292 [1] INFO EclipseFileIdentification.Program - UserLogin error: Could not load file or assembly 'Nucleus.Cryptography, Version=17.4.17816.4355, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

2017-08-28 15:53:20.4934 [1] INFO EclipseFileIdentification.Program - UserLogin error: Could not load file or assembly 'Nucleus.Cryptography.Interfaces, Version=17.4.8011.2800, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.