Conflict - when files have same timestamp

[achan_cc]

Hello,

I am running into an error where periodically sync'ing is failing due to a conflict, but the timestamps of the files in question (in the logs) are the same?

2018-10-23 14:47:33 : ** Conflict - C:\ivr\ccm\MTO-511\prompt\fr-CA\9915935.wav (CHANGED) (162.61KB) (2018-10-23 2:46:53 PM) <-> \\gscpigdcapivr14\c$\ivr\ccm\MTO-511\prompt\fr-CA\9915935.wav (CHANGED) (162.61KB) (2018-10-23 2:46:53 PM)

Thanks,
AC

[TGRMN Software]

Hi,

what version / build of ViceVersa are you using?
Is the file size exactly the same?
Looks like both files on both sides have changed since last sync.

thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[achan_cc]

VVEngine v2.1 Server Premium (Build 2106)
ViceVersa Pro 2.5 (Build 2517)

According to the log both files are the same size and same timestamp.

The setup I have is as follows:
On Machine 1
Profile 1 syncs Source to Machine A
Profile 2 syncs Source to Machine B
Profile 3 syncs Source to Machine C
Profile 4 syncs Source to Machine 2
On Machine 2
Profile 1 syncs Source to Machine A
Profile 2 syncs Source to Machine B
Profile 3 syncs Source to Machine C
Profile 4 syncs Source to Machine 1

I believe that Machine 2 is sync'ing the file to Machine A, B, and C, and Machine 1. Then Machine 1 sees the file change, and attempts to sync the same file to Machine A, B, and C ... they the updated file are already on Machine A, B, and C.

However, I'm not sure why the sync would fail if the details are the same? And is there anyway to keep this from happening/affecting subsequent syncs/changes to this file?

thanks,
AC

[achan_cc]

Hello,

Was wondering if there is a way to avoid these conflicts errors? Because I believe it messes up subsequent sync'ing.

Thanks,
AC

[TGRMN Software]

Hi, I will check if this has changed in the latest version 3... thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[TGRMN Software]

Hi, using version 3 I can not recreate this issue, i.e. if I have 2 folders synchronized (source and target) and then I change a file in source and copy that file to target outside ViceVersa and then re-run the sync in ViceVersa, ViceVersa will not see this as a conflict as the two new files are both changed but identical. I think you should be able to test this too in version 2.5? The conflict must happen for some other reason.