Unexpected file extension

Posts: 2 · lhighland 22 Feb 2023, 01:56

The batch file that runs every day at midnight has been working for a long time. It stopped a couple weeks ago. Upgrading to V12.1 did not change the symptom.

The message says "Cannot open file "C/Users/Owner..."
Unexpected file extension
Expected: ffs_gui, ffs_batch, xml

The properties of the file show that it has a ffs_batch file extension.

The first two lines of the file are:
<?xml version="1.0" encoding="utf-8"?>
<FreeFileSync XmlType="BATCH" XmlFormat="17">

What now?
Thanks

Posts: 7212 · Zenju 22 Feb 2023, 09:16

FreeFileSync 11.24 [2022-08-28]
-------------------------------
Require config type and file extension to match

Posts: 4055 · xCSxXenon 23 Feb 2023, 15:37

viewtopic.php?t=9788

Posts: 2 · lhighland 24 Feb 2023, 20:10

Thanks for the suggestions.

It's fixed now. The problem was the spaces (blanks) in the file name argument passed to FFS by the W10 task scheduler. The entire file name was properly enclosed in quotes ("). This had been working for a long time but stopped a couple weeks ago -- likely due to a Windows update.

I took the blanks out of the argument (the file name of the FFS batch job) and all is well.

Thanks again.