MID Server Issue: Misleading FileNameComplianceInSync Attachment file errors, when ecc_agent_script_file attachments are missingDescriptionXanadu added a filename check for synched files. It generates MID Server issues records when there is a problem, but these can be misleading false positives that would be difficult to figure out if the record has Use Attachments but doesn't have the referenced attachment present. Note: This Problem is a supportability enhancement, not a root cause of issues.Steps to Reproduce Can be reproduced in a clone target instance, as at the Xanadu release timeframe there was a Clone problem that causes the attachments to be excluded.See PRB1797792 Clone are excluding attachments on MID Server Script files [ecc_agent_script_file], breaking Enhanced ADM Discovery To replicate that issue, create an attachment that has Use Attachment ticked, but has no attachment. It should be possible to create a new record with an attachment, Export as XML, delete the record and its attachment, strip out the attachment data from the XML, and import. In an Xanadu instance, on startup, the MID Server will sync all ecc_agent_sync_file extended tables.This MID Server issues record will be created for each MID Server: FileNameComplianceInSyncAttachment file with sys_id: e88f49a043032110c42154249ab8f24b 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. The reason is that e.g. MID Server Script File "ADMELauncherWinRM.psm1" has Use Attachment ticked, but uses the Script field, not an attachment/ecc_agent_script_file.do?sys_id=5b69ee96e701030058890a6103f6a9b9 The attachment is missing, so it can't know the file name, therefore the error message is wrong. It also does not indicate which table and record sys_id/name needs fixing for supportability.Workaround*** Don't link this problem to support cases. *** This problem was fixed in Yokohama release, to improve the error descriptions only. This does not fix any actual error and root causes with MID Server Script file Attachments. If the sys_ids relate to Discovery's ADME probes, see:KB2611107 / PRB1960340 Discovery's MID Server Script Files for Application Dependency Mapping are deleted during clones Related Problem: PRB1797811