You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
Trying to do a full export from docspell using the command
D:\docspell_export>dsc-0.11.0.exe export --target D:\docspell_export
but get the following error after 5 items have sucessfully exported:
"Export - Error creating a file: Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch. (os error 123)"
The german part says "incorrect syntax wrong for filename, directoryname or volume".
I'm running docspell 0.40.0 on windows docker desktop. I really need a full export and cannot use "download all documents" because there are over 4000 of them.
Is there maybe a bug in the export when using umlauts / other non-english characters?
Thanks a lot!
The text was updated successfully, but these errors were encountered:
Hi @ekafaton thanks for the report. Unfortunately, I'm not sure how to diagnose this further. I don't have Windows and can't try it out. I assume indeed some character in the filename that triggers this. Can you perhaps find out which item it is and possibly even what name it is? Can you run this with -vvv so it perhaps puts out more information about the error?
Hi
Trying to do a full export from docspell using the command
D:\docspell_export>dsc-0.11.0.exe export --target D:\docspell_export
but get the following error after 5 items have sucessfully exported:
"Export - Error creating a file: Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch. (os error 123)"
The german part says "incorrect syntax wrong for filename, directoryname or volume".
I'm running docspell 0.40.0 on windows docker desktop. I really need a full export and cannot use "download all documents" because there are over 4000 of them.
Is there maybe a bug in the export when using umlauts / other non-english characters?
Thanks a lot!
The text was updated successfully, but these errors were encountered: