I am seeing an error after syncing when I have a new record on the spoke (FileMaker DB) to be synced into a Microsoft SQL server table on the hub. The MirrorSync setup uses a custom primary key to do the insert into the SQL table.
According to the sync window as well as the sync log, the insert fails. However, when I review the table in SQL Server on the hub, the record has indeed been inserted properly. For some reason, MirrorSync is reporting this as an error. In addition, MirrorSync does not seem to remember the PK of the newly inserted hub record so if I do another sync on the spoke, it inserts it again. If I run the sync 3 times, I will have 3 new records inserted.
This is the error that I see in the log. No further information is available.
table Hub node MS SQL Server/KeyPhrases failed for source nodeId '275'
This also happens on another table as well.
Is this a bug in version 4 of MirrorSync or is there some configuration step that is missing?
Any help would be greatly appreciated, as this is preventing us from releasing this solution to production.
Thanks!