We have been sending images out to contractors, and sometimes when they come back the files are having this error:
the file contains file info data which cannot be read and has been ignored
When I then try to Photoshop Script the file info it throws errors. Does anyone know what causes this error to happen?
They're probably using older versions of Photoshop that can't read some part of the newer file.
And that's a warning, not an error -- just informing you that some part of the file was not recognized and could not be read in the older software.
I'm seeing this with CS5 and CS6 recently with every Getty image that I open. It happens each time open the psd I created from the file. The only way to get rid of it is to cut and paste the background into a new file and then drag all of the edits to the new file. Just started happening a few weeks ago. I get a lot of Getty files and it never happened before. I wonder what they are doing to the files?
ok, Thanks!, BUT here's the bigger issue:
We use a lot of Photoshop Scripting, and the file info is how we direct all of our workflows. when a file comes back with "the file contains file info data which cannot be read and has been ignored" error, the scripts are unable to read/write to any of the file info ever again. So not only did we lose all the info already in the file, but we can't use the file at all after this.
Additonally, we tried copying and pasting to new blank documents, but realized we needed all the paths, channels, and sampler points too.
Is there anything anyone can think of to get around this probelm? A setting, or a program to fix the metadata, etc?
The file turns out to contain XMP metadata with bad formatting for a date variable (IPTC Photoshop DateCreated).
The file should still work, and FileInfo should work, but that one field will be ignored.
The one problem you have with scripting is that the error/warning could stop the script unless you told Photoshop to run the script silently.
A metadata editor could probably fix the date value (or they might complain, too).
You do need to figure out what applicaiton is writing this bad date format, and get that fixed.