I am experiencing a strange issue while trying to configure an External File Source in M-Files to link to a shared network folder.
The Setup:
-
I have configured the full UNC path to the shared folder.
-
I am using a specific network account with full access permissions to this path (not the LocalSystem account).
-
Crucially, I am using this exact same account for both the 'Link' and 'Import' attempts.
The Problem:
-
When choosing 'Link': After selecting the Traditional Folder and clicking 'Apply', the process starts and stops almost immediately. No files appear in the M-Files client, and—most frustratingly—nothing is logged in the M-Files Server event logs or Windows Event Viewer, even when forcing a "Refresh Now". It is as if the process isn't even triggering.
-
When choosing 'Import': Using the same settings and the same account, the process runs perfectly. Files are imported into the Traditional Folder as expected.
Troubleshooting Request: Given that the 'Import' succeeds, I have ruled out permissions or path issues. I am struggling to understand why the 'Link' option fails silently without generating any warnings.
If you don't have a direct solution, could you point me toward where I might find more granular error reports? Since the standard Event Log is empty, are there specific M-Files Server trace logs, registry keys to enable verbose logging, or side-logs I should check to understand why the linking process is aborting?
Any guidance would be greatly appreciated.
