Dear Sir or Madam,
since the last Mac OS upgrade High Sierra 10.13 to Mojave 10.14.6 my Freefile Sync version 12.2. does not work correctly anymore. The batch files cannot be executed anymore because of an XML error. (see attachment) Is there a solution for this problem?
Thanks
Moritzbock
The configuration file "/Users/self/Desktop/LUMINAR_images.ffs_batch" is incomplete. The missing elements are set to their default values.
The following XML elements could not be read:
<FreeFileSync> <MainConfig> <Comparison> <Variant>
<FreeFileSync> <MainConfig> <Comparison> <TimeShift>
<FreeFileSync> <MainConfig> <Comparison> <Symlinks>
<FreeFileSync> <MainConfig> <SyncConfig> <Variant>
<FreeFileSync> <MainConfig> <SyncConfig> <CustomDirections> <LeftOnly>
<FreeFileSync> <MainConfig> <SyncConfig> <CustomDirections> <RightOnly>
<FreeFileSync> <MainConfig> <SyncConfig> <CustomDirections> <LeftNewer>
<FreeFileSync> <MainConfig> <SyncConfig> <CustomDirections> <RightNewer>
<FreeFileSync> <MainConfig> <SyncConfig> <CustomDirections> <Different>
<FreeFileSync> <MainConfig> <SyncConfig> <CustomDirections> <Conflict>
<FreeFileSync> <MainConfig> <SyncConfig> <DetectMovedFiles>
<FreeFileSync> <MainConfig> <SyncConfig> <DeletionPolicy>
<FreeFileSync> <MainConfig> <SyncConfig> <VersioningFolder>
<FreeFileSync> <MainConfig> <GlobalFilter> <Include>
<FreeFileSync> <MainConfig> <GlobalFilter> <Exclude>
<FreeFileSync> <MainConfig> <GlobalFilter> <TimeSpan>
<FreeFileSync> <MainConfig> <GlobalFilter> <SizeMin>
<FreeFileSync> <MainConfig> <GlobalFilter> <SizeMax>
<FreeFileSync> <MainConfig> <OnCompletion>
<FreeFileSync> <BatchConfig> <HandleError>
<FreeFileSync> <BatchConfig> <RunMinimized>
<FreeFileSync> <BatchConfig> <LogfileFolder>
XML elements could not be read
- Posts: 3
- Joined: 16 Apr 2023
- Posts: 1202
- Joined: 8 May 2006
My suggestion (to try) is to...
backup your .ffs_batch .ffs_real .ffs_gui & the like
load your .ffs_batch into FFS
make a slight change to it, perhaps add an 'X' to the end of a directory name
(so /mydir/ -> /mydir.X/)
save that .ffs_batch
load it again, & revert the 'X'-change
save that .ffs_batch
Now see if it works correctly.
Likewise you may want to compare the backed up copy with the newly changed copy.
XML files, while "text", have a "header" to them & are "interpreted", & I'm suspecting going from the old to the new, a new header is expected, & that by re-saving your batch, that will fix things?
backup your .ffs_batch .ffs_real .ffs_gui & the like
load your .ffs_batch into FFS
make a slight change to it, perhaps add an 'X' to the end of a directory name
(so /mydir/ -> /mydir.X/)
save that .ffs_batch
load it again, & revert the 'X'-change
save that .ffs_batch
Now see if it works correctly.
Likewise you may want to compare the backed up copy with the newly changed copy.
XML files, while "text", have a "header" to them & are "interpreted", & I'm suspecting going from the old to the new, a new header is expected, & that by re-saving your batch, that will fix things?
<?xml version="1.0" encoding="utf-8"?>
<FreeFileSync XmlType="BATCH" XmlFormat="17">
- Posts: 3
- Joined: 16 Apr 2023
Hi therube,
I have installed the latest version (12.2) again, created a batch file with it.
Nevertheless the known error message appears.
In the header are these lines with the newly created batch file.
Which possibility still exists?
I have installed the latest version (12.2) again, created a batch file with it.
Nevertheless the known error message appears.
In the header are these lines with the newly created batch file.
<?xml version="1.0" encoding="utf-8"?>
<FreeFileSync XmlType="BATCH" XmlFormat="17">
-
- Site Admin
- Posts: 7506
- Joined: 9 Dec 2007
Most likely, /Users/self/Desktop/LUMINAR_images.ffs_batch has been corrupted outside of FFS. The file format is XML, so you can check this manually yourself.
- Posts: 3
- Joined: 16 Apr 2023
I have found the last option:
1. delete the data from the library
"/Users/xxxxx/Library/Application Support/FreeFileSync".
2. reinstallation
3. runs!
1. delete the data from the library
"/Users/xxxxx/Library/Application Support/FreeFileSync".
2. reinstallation
3. runs!
-
- Posts: 4867
- Joined: 11 Jun 2019
Yeah this sounds like the OS upgrade either failed to migrate the "AppData" or there may have been a permissions issue that reinstallation fixed