Author Topic: Strange (new) warning: Open '' failed  (Read 831 times)

Mac2

  • Sr. Member
  • ****
  • Posts: 237
Strange (new) warning: Open '' failed
« on: March 08, 2015, 09:57:03 AM »
I today wanted to try out the new CHARSET FileName option, using the new 9.89 ExifTool release.

So I've created an UTF-8 encoded arg file:

-overwrite_original
-charset
FILENAME=UTF8
-tagsfromfile
c:\images\Czech\VLETEV~1\200x320.jpg
-all:all
-api
struct=2
-use
MWG
f:\temp\et_temp.xmp


When running this file, ExifTool displays this warning message:


Warning: Open '' failed - f:/temp/et_temp.xmp
    1 image files created


1. The output XMP file is created and contains valid data.
2. When I run the ARGS file again (with the now existing XMP output file), the file is updated and no error message is issued.
3. It also happens when I leave out the -charset FILENAME= arguments!

What is the problem here? I don't recall seeing this warning message ever before.

Phil Harvey

  • ExifTool Author
  • Administrator
  • ExifTool Freak
  • *****
  • Posts: 14896
    • ExifTool Home Page
Re: Strange (new) warning: Open '' failed
« Reply #1 on: March 08, 2015, 10:30:24 AM »
Thank you very much for bringing this to my attention.

This is a bug introduced in a recent change to the Windows version of ExifTool.  It will be fixed in ExifTool 9.90.

You may safely ignore this warning.  ExifTool was trying to preserve the creation date of a file that didn't yet exist.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

Mac2

  • Sr. Member
  • ****
  • Posts: 237
Re: Strange (new) warning: Open '' failed
« Reply #2 on: March 09, 2015, 11:17:24 AM »
Thanks, Phil!

I thought as much because everything worked nicely as before - except for the strange warning.

The cool new CHARSET FILENAME=UTF8 (Thanks!) option should help solving the problems when users work with file names which cannot be represented in the current or a supported code page, and the Windows GetShortPathName() trick I use also does not work (e.g. files with names shorter than 8.3, on removable media (USB sticks), some network systems).