Is it correct your application originates from an older Mendix version (like 6)?
I think it does (noting the FileID attribute instead of the UUID attribute) and it appears the (old) files for some reason cannot be found anymore, causing the migration of these files (from old Mendix 6 files to modern files) to fail.
To solve this issue/these logs at startup, you can either put the
FileDocument's back, however, considering the name "Un-defined", I'm assuming these files are not used. Therefore, you can probably best remove those entities from the database (and then the issue should be solved).
If removal is unwanted, you can extract the id's from the logs and if you are sure that the
FileDocument's reported in the logs actually does not have content and there is no possibility of getting them updated, then setting
0 for those
FileDocument 's should fix these logs at the start of the application.
For example, if you can reproduce this locally, you can use the database viewer and find (likely) fileIDs (specifically, fileIDs 620 and 621) have no content, for example, like fileIDs 43 – 48 below:
As a side note: these logs are generally quite harmless, as they usually refer to files that are not used anymore.