Errors with Synchronisation

[lek@startex]

We've recently experienced an error with Viceversa not synchronising updated versions of files on the source disk to the target disk.

Platform is MS Windows Server 2003 on HP Proliant, file system is NTFS, data volume is about 70GB, with >400GB+ free space on both disks, Viceversa was registered 26/3/06, profile used is as follows:

Folders
- Source: "F:\"
- Target: "G:\"
- Include Subfolders: Yes
- Create sources/targets that do not exist
Comparison
- Comparison Type: Size and Timestamp
Execution
- Method: Synchronization
- No overwrite / read-only / error confirmations
- Tracking Datababase: "../vvdb1.tdb"
- No archive for deleted/replaced source files
- No archive for deleted/replaced target files
- Copy files even if timestamp changes after initial comparison
- Copy directly to destination file (do not use a temporary file)
- Use 'Volume Shadow Copy' to copy open files for source

Only certain file types have been affected, including .xls, .dat and Solidworks part files (related Solidworks assembly files have been synched to updated versions).

.doc and other file types appear largely unaffected and have apparently been synched with more recent versions.

It appears that most of the affected files may have been initially created prior to 21/3/06, and that some more recently created files with .xls extensions appear to have been synched without any issues (though we are still in the process of confirming).

The data volumes do contain some directory structures that exceed 255 characters, but a large proportion of the impacted files were not contained within directories that exceeded 255 characters.

Tracking database is available, but is over 50mb is size.

A response, explanation, indication of any similar issues being experienced and/or potential workarounds is requested.
_________________
Regards

Lek@startex

[TGRMN Software]

A log file will be needed to better analyse the situation. You can setup a log file in the profile settings, under execution.

Another test you can do now is to run the profile "manually", opening it in Viceversa, clicking on compare and then execute and see if you get any error messages.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com