can not export file list

[gumbo]

Hi,

I suddenly ran and keep running into an error when I try to export a file list in FFS/Excel which I have done so many times and I use it a lot.
The error that I encounter is quite persistent, I have reinstalled FFS and Office365 but to no success, the error keeps coming (attachment).

How can this error be solved?

[xCSxXenon]

Does that "temp" directory actually exist if you try to browse for it in File Explorer?
Open File Explorer and enter "%TEMP%" into the address bar on top

[gumbo]

It exists, after %TEMP% File Explorer opens ...\AppData\Local\Temp and shows all the content (folders, files).
The folder that is mentioned in the error also exist and contains csv files that obviously are created when trying to export a file list (attachment). When I try to open a csv file with Excel the same error occurs ("file not found, moved or deleted etc").

[xCSxXenon]

You could try moving/renaming the files and trying to open them again. This would be testing if there is an issue with the path or name, for some reason.

[gumbo]

By renaming the generated csv file in the temp folder I was able to open it in Excel. The file contains a regular file list, I can't see anything wrong with it.

[xCSxXenon]

If you rename it back to its original name, does it still work?

[therube]

It looks like Excel is trying to open, "Laatste sessie.xlsx" - an .xlsx file,
rather then an 'Export file list', .csv file.

You do have .csv files in that (now named differently, cause you've restarted FFS) directory, but not .xlsx (at least from what is shown).

[xCSxXenon]

It looks like Excel is trying to open, "Laatste sessie.xlsx" - an .xlsx file,
rather then an 'Export file list', .csv file.

You do have .csv files in that (now named differently, cause you've restarted FFS) directory, but not .xlsx (at least from what is shown).

Good catch! OP, are you using the latest version of FFS? Mine exports as a csv and opens fine in Excel. It seems weird that it would export a csv file and then try to open an xlsx file with a completely different name.

[gumbo]

Renaming the csv file back to its original name does not work, reverts back to the error.

[gumbo]

Version 14.3.
When I place an empty "Laatste sessie.xslx" in the temp folder, Excel opens this empty file after generating a file list export in FFS, without an error. A csv file is also placed in the temp folder but is not opened.

[xCSxXenon]

Where did you obtain the FFS installation executable? From this website directly, or a third-party host?

Read here: viewtopic.php?t=10932
A year and a half ago, the dev was mentioning removing this feature altogether. I don't know what his stance is today, but if it is the same, seems unlikely to get looked into ¯\_(ツ)_/¯

Here's another thread from 2017 stating similar thoughts: viewtopic.php?t=4709&hilit=export+csv#p15781

I can't imagine it's an issue with FFS, because then it would be happening to everybody. Try moving the csv file out of %TEMP% and to another folder. Do you have another computer that you can copy the "FFS-xxxxxx" temp folder to for testing?
Or, you could zip up that "FFS-xxxxxx" folder and upload it. I could download and see if the same happens with my Office installation. This will, of course, show the files inside. Maybe you can rename it, open it, replace the content with fluff, save it, rename it back to original, and if it still errors, zip it up and upload it.

[Plerry]

From gumbo's picture it seems FFS does create the csv-file when exporting the file-list.
Do those csv files look like normal csv-files when opened with a text editor, e.g. Notepad++?
If so, it is not an FFS problem, but rather an Excel problem.

Gumbo, try restarting your computer.
I frequently get notified that Window needs to update.
If it is not convenient to run the update (including restarting) at that moment, I postpone the update.
I then often experience that one or more (locally installed) Office 365 applications start to behave weirdly. After running the update (including restarting) everything works normal again.
(It almost seems a built-in nuisance to stimulate the user to run the update ...)
Perhaps something similar is the case for you.

[gumbo]

I did some tests on 3 different systems. Two run W10, a desktop and laptop. The third desktop system runs W11. Both W10 systems show the exact same error behavior, as described before. The W11 system works flawlessly, no problem generating a file list in FFS/Excel. The W11 system looks like it has a newer Excel version. I would say the problem is in the Excel version running in W10 since both systems show the exact same behavior (error). I have installed Office365 on all systems, all coming from the only source that I have access to (portal.office.com).

[Plerry]

Just verified. For me exactly the same problem (Win10, Excel365)

The problem is that although the file is written as a *.csv-file, Excel tries to open (it as) an *.xslx-file, which is not there.
Even double-clicking the *.csv file FFS created generates the same problem.
However, if from within Excel you select to Open a file, then Browse to all files (*.*) or Text files (*.prn,*.txt,*.csv) and then select the csv-file FFS created, it open without a problem.
So, it is clearly an Excel problem!

[gumbo]

Thanks so much, Plerry, for veryfing and good to see you reproduced the same problem!
Yes, double-clicking the csv won't help but renaming does. So a workaround is available and until an update resolves the problem or after migrating my W10 systems to W11 (ultimately by mid Oct), whichever comes first, I can live with the workaround.

[Zenju]

Apparently an Excel bug when the file name contains brackets: https://www.reddit.com/r/excel/comments/1k7qmrx/brackets_are_breaking_filenames/

[Plerry]

In Office version 2509 (perhaps already from 2505 onwards) the problem seems to have been solved.
A file named [Test] Book.csv now opened just fine by double clicking.

However, if from Excel you try to save a file as [Test] Book.csv it fails:

ExcelFilenameNotification.png (9.66 KiB) Viewed 206 times

So, instead of really solving the problem, Microsoft now simply also disallows the use of brackets when saving a file ... .
This in conflict with their own list of reserved characters.
Remarkable is also that the use of brackets is no longer allowed when saving from Excel, but still works fine when saving from Word (did not test other apps that are part of the Office suit) .

[gumbo]

I confirm "Export file list" works just fine in version 2509 that I currently use.