https://forums.autodesk.com/t5/vault-forum/vault-2014-professional-sql-data-conflicts-in-replicated/m-p/5476967#M45008 <P>Hi Travis</P><P>after analyzing the dependencies to and from the MasterChanges table I found out that is has just 1 dependency to the Master table.&nbsp;</P><P>I saw that NONE of the failing MasterChanges entries has a correspondig entry in the Master table. So this row does not make sense in the vault database - you can´t find out what this "thing" is (a folder, file,...) - it is just a useless entry.&nbsp;</P><P>Additionally as you also found out this is true for all the subscribers.</P><P>&nbsp;</P><P>So I made a backup of my publisher database, stopped the database replication and deleted all those entries per sql delete script from the MasterChanges table in the database. Then I removed all the conflicts with the conflict viewer from SQL studio and activated the replication again.</P><P>All conflicts are gone since then and did not come back.</P><P>&nbsp;</P><P>No problems so far.</P><P>Unfortunately there is no official statement from Autodesk until now if this can lead to problems...but as replication was extremly slow this was the only solution to get everything up and running again...</P><P>&nbsp;</P><P>klaus</P> Wed, 21 Jan 2015 13:18:55 GMT Anonymous 2015-01-21T13:18:55Z