MID Server FileNameComplianceInSync Error

[Derek Jones]

We're facing a recurring issue on a MID server of ours that is proving to be quite challenging. Despite our efforts, we haven't been able to pinpoint the cause. The issue record has a source of FileNameComplianceInSync and the following short description:

Attachment file with sys_id: XXXX was not synchronized, as the file's absolute path is outside the target directory. Please rename the file appropriately. If deleting this file instead of renaming, please manually resolve this MID Server Issue record.

Of course, we searched for that sys_id in both the sys_attachment and looking in a number of the ECC tables but not found out anything, nor using SN Utils' search; The MID is fine otherwise, but we'd like to get rid of that error message all the same. 

Has anyone seen this error before and found a way to clear it? 

[chrisboylan]

I got a new error - there are two more files that needed fixing after that - ADMELauncherWMI.psm1 and CollectConnectionsAndProcessesInfo.ps1.     You can find the files by looking in here /ecc_agent_script_file_list.do?sysparm_query=use_attachment%3Dtrue.    I just unchecked the file attachment on them all. 

Here is the complete list of mid server issues related to this -

[mike_brown]

I found this and they do not seem to have a resolution at this time.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1702039#:~:text=Attachment%20....

[davidpiper]

Things have moved on a bit now. Attempting a fix of this in the clone engine doesn't seems to have worked.
So I'm trying to get this done 'properly' with this:
PRB1960340 Discovery's MID Server Script Files for Application Dependency Mapping are deleted during clones
which will be first dependent on getting this fixed:
PRB1963685 MID Server File Sync doesn't sync attachments when the sys_attachment table name is prefixed with ZZ_YY to prevent clones deleting the OOTB attachments