When working in multi-platform environment, Connect Agents may face filename conflicts. This guide explains reasons and way to fix it in details.
Agent is capable to resolve the conflict only to the extent of adding a ".Conflict" to the file's name. Recheck and resolution of conflicts is a disk-costly operation. Thus it's disabled by default by "Resolve filename system conflicts" in Agent Profile. In this case Agent will just skip the conflicting entry.
As a side effect, the job won't reach its 100% completion, and the agent will give the error "There is unresolved file name conflict".
The error only gives information about the conflicted files. Fixing it will require to manually recheck the files and keep only the 'proper' one:
- Find the 'healthy' file among the conflicted (on the agent that has RW access in the job)
- Move it out of the folder. Not just copy, but move. Wait till its counterpart is moved from the folder on other agents.
- Delete all the conflicting remnants from all agents.
- Make sure that the conflicting factor is also eliminated and put the healthy file back to the directory.
For Distribution and Consolidation jobs the fix will take effect on nect job run. Sync job will continue from here automatically.