Error writing metadata to photo files

I am using CS6 and have moved to a new computer with a clean install of CS6 under Windows 8.1.  In the past I had no problem using Bridge to append my personal metadata file to photos (RAW files, NEF).  With the new installation I am getting the repeated message " Error writing data to...."  even after trying all the " fixes"  suggested by the help files.
Can anyone help me to resolve this issue?
Thanks.

I found an answer, somewhat different.  I did more search and found that you need to be administrator and for Adobe to see you as administrator, for many functions to work, such as writing metadata to files or putting stars on photos to rank them.  I could do neither.
THEN, I tried opening Bridge by right clicking on the icon, and opening the file as administrator (a choice).  Everything worked.  So, why was Adobe not seeing me as administrator.  My user account was the only account on the computer and has administrator privileges.
I started doing searches on that, and stumbled, yes stumbled, on what I think is a solution to that situation.
I set up my account so that I needed a password to log in.  Once I did that, Bridge worked fine.  But, I still did not want that additional startup step.  You can then back to change password and leave the password entries blank.  Then, the computer starts up with blank passwords, zips past the welcome screen directly to the desktop, and Windows now sees me as the administrator, and so does Adobe.
Keep you fingers crossed folks, this seems to be working.

Similar Messages

  • Error writing metadata to any file except jpegs

    Hi all,
    A coworker and I have been assigned the job of keywording all the photos in our database. We aren't photographers and are only messing with the keyword metadata on the photos.
    But we've been having a consistent problem with Bridge CS4. When I attempt to add keywords to any file format except jpeg, it gives me an error message "Error writing metadata to " and the filename. Then to make matters even worse, Bridge continues trying to add the metadata to the same images over and over again until I do a forced shutdown.
    We're running Bridge on a network with exported cache. The only thing I have found as a possible solution is a permissions setting problem, but I can't find any way to check on that.
    Any help you can offer would be great. Thanks!

    I had this same problem. This was the solution for me in my CS4.
    Go to Bridge
    Go to Preferences
    Go to Metadata
    Make sure IPTC and Keywords are checked.
    This will allow you to add keywords to your metadata in bridge.
    Here it is not checked:
    Here it is checked:

  • Error writing metadata to file

    I am getting constant error messages from Bridge CS4 when trying to add keywords to my images "Error Writing Metadata to file "XXXX". It's very annoying and destroying my workflow. I have tried resetting original preferences, and using purge cashe. Finally I reorganized my entire folder structure which seemed to make the problem less frequent.
    The circumstance that makes this error pop up most frequently is when I add keywords to a handful of files that already have another keyword assigned. Quitting the folder and then re-entering it solves the problem for the photos with the current error, but then 20 or so photos later I get the error message again.
    Any Fixes?

    A new suspicion was that the read/write data might be different for the images files themselves than it was for the folder holding them. So I applied the read/write permission to the image files themselves. No luck though. Still getting "Error writing metadata to file xxxx" Errors. Would love to be spending all this time editing photos instead of chasing down bugs. Brand new MacBook Pro and I'm spending more time trying to fix errors than using the software. ::sigh::

  • Error Writing Metadata thumbnail icon, why is this?

    When I take a layered TIFF file from my Lightroom 3 photo library and make creative changes  to the file in Photoshop CS5, when I save the file, close it and return to Lightroom, the image thumbnail in the Library Grid mode displays a warning exclamation point.  Hovering over the icon displays the tooltip Error Writing Metadata.  Can anyone tell me why this is happening and how to remedy the situation the right way?
    Clicking the warning (exclamation point) icon present two options:  "Import Settings from Disc" or "Overwrite Settings"
    Thanks in advance
    Doug

    I found a pattern, this happens when I open and edit the file with gedit. Even when I am very carefully just push the del button. Mabe gedit add some inviseble chars when it saves.

  • Error writing metadata when Importing Lr 2.7 catalog in Lr 3 final

    Hi,
    I imported (and sucessfully converted) my Lr 2.7 Catalog in Lr3 final but now, all my photos have  this little icon that says " Error writing metadata "
    Why?
    Thx!

    According to Martin Evening in his Lightroom 2 book p. 178, "If you see the icon shown in Figure 4.74 [the !], click to open the dialog box where you can either choose Import Setting from Disk if you think the external settings are right, or choose Overwrite Settings if you think the Lightroom catalog settings are the most up to date."
    If you did not edit these images in another program like Camera Raw some unknown event caused Lightroom to indicate that the files were edited in another program.  In this case you probably do not want to include this edit.  It will probably work out if you choose Overwrite Settings which will keep the settings that you have in the LR database, disregard the changes from outside LR, and remove the !.
    If you edited these images in another program and you want to keep those changes, choose Import Settings from Disk to bring the external settings into the LR database.
    If you want to write the LR settings to the DNG files go to Metadata > Save Metadata to File or (Ctrl-S).  I strongly recommend saving LR settings to the file.  Others disagree.  In the Catalog Settings under Metadata, check Automatically Write Changes to XMP, if you prefer this to be done automatically.
    Whatever you do, be sure to backup your LR database, at least two or three times, and be sure that all of you images are backed up.
    Follow the above procedures by doing a few files at a time, and check that you are getting what you want before doing them all.

  • Cs4 error writing metadata?

    When I tried to add a keyword to a bunch of photos under a smart collection,
    I encountered this problem "There was an error writing metadata to XXX.cr2."
    Thank you for your help.

    Nobody can tell you anything without proper system info or other technical details, including specific details about your Raw files, where they are stored, what data fields you use and so on. Either way, ask in the respective product forum.
    Mylenium

  • Bridge 4.1.0.54: Error writing Metadata to some [....].jpg

    I am sorting my files (.JPG) with bridge. Some files just can't get rated (bridge fails without giving me an error), and if I try to set other metadata (like keywords), bridge tells me "There was an error writing metadata to ".....JPG".
    I have full access to the folder, it is an internal disk, the files are not locked. It affects about 5% of all files - this is the second shooting (&folder) where I have this problem. I don't see any differences between the files I can change and the ones where I can't.
    I can rename the file with bridge, but that does change nothing. I tried purging the cache, it changed nothing.
    I just found out: I can change the tags with Windows Explorer, Bridge does show them, and afterwards I can change them with bridge too. Someone got an Idea how I can avoid this step?
    [Win7Pro x64, i7]

    Jingshu Li wrote:
     I tested your issue but haven't reproduced yet. Could you please provide more info? 
    1. You mentioned usually you will select tens of images (in the smart collection or search result) and apply metadata, and then you get the error. I'm wondering can you apply metadata successfully if you only select one image and then apply metadata?
    2. Before you apply metadata, do you wait for the images thumbnails genaration complete?
    3. Can you apply metadata successfully if you selete the images at their real location (not in the smart collection or search result?)
    4. Your OS info, mac or win, and version?
    I just set up a quick test, and it failed immediately. I haven't even been using Bridge today...
    The computer runs CS5 on Windows 7 Professional 64-bit. I used to run CS3/CS4 on a different computer loaded with Windows XP Professional. I'm always up-to-date with OS/driver/application updates. Both systems exhibited the same problem.
    The raw image 3-tier folder hierarcy is on a separate internal drive: P:\Camera\2011\08-15 Location\, P:\Camera\2011\08-16 Location\, etc.
    The Bridge cache is on a separate internal drive: T:\BridgeCS5\, Camera Raw's cache is in T:\CameraRaw\.
    The images are mostly Nikon NEF (D300), and ACR saves settings to 'sidecar' files. Most of the images have settings, and many have crops.
    I created a new Collection, and dragged the contents of 7 image folders into it - a total of 407 images. None of these files have had keywords applied, but most had been worked in Camera Raw already. After waiting for thumbnail/preview generation to finish, I selected the collection, created a new sub-keyword, selected all images in the collection, and ticked the new keyword (automatically ticking the parent keyword). Within a few seconds, I started getting the "Error writing metadata..." warnings, and had to OK 15 images.
    The failed images were spread across 3 of the 7 selected directories. Trying the same thing 30 minutes later resulted in the same errors. Trying each failed image individually gave the same error (either as part of the collection, or from it's own folder).
    I opened one of the problem images in Camera Raw, and adjusted Blacks, clicking Done to save the settings. I then tried to apply the keywords again. This time it worked.
    To answer your questions directly:
    1. I have never experienced this problem keywording files individually (apart from after the errors, as mentioned above), but then I wouldn't usually be selecting lots of images to keyword individual images.
    2. Yes, I always wait for the spinning circles to disappear, sometimes even longer!
    3. I just tried applying keywords to a single folder of 102 images, and 2 failed to update. So the answer is No, it fails at real locations too.
    4. Windows 7 Professional 64-bit, running on Intel Core2 Duo and 4GB RAM. Same thing happened before on a Windows XP Professional PC, running on an Intel Pentium 4 and 2GB RAM and a single hard drive.
    I hope that helps.

  • CS6 "There was an error writing metadata" message PC and Mac

    I have seen this in the forums but looks like no one has an answer yet. Adobe chat support was totally not helpful.
    I am getting an error message when trying to apply keywords to some images in Bridge. The error is very non-specific, all it says is "There was an error writing metadata to "filename.ext"".  This happens when trying to apply keywords to a batch or single images.  If not all images in the batch are error-prone, keywords are applied to those images and I get the error message for each image that had a problem.
    My version is CS6 5.0.2.4 x32, but my co-worker downloaded a free trial today for her PC and is having the same problem.  Another co-worker downloaded to his Mac and has the same issue. I am on a windows machine. 
    Sometimes one co-worker get the error message on an image, and I am able to tag thje image without error.  Other times, none of us are able to tag the image.  The images were not made by the same camera and come from different sources.
    We are all administrators on our computer and have tried opening Bridge with "run as administrator".  We still get the error. 
    The images are on our local machine, not a shared network drive.  Some of the images did live on a shared network drive at one point, but not all.  We can't seem to find a pattern between the files this is happening with.

    That sounds like a problem with your machine, perhaps not enough Ram, a hard drive going south, a permissions issue, etc.
    BOILERPLATE TEXT:
    Note that because this is boilerplate text, not all points may apply to any given, specific poster.
    If you give complete and detailed information about your setup and the issue at hand,
    such as your platform (Mac or Win),
    exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
    your settings in Photoshop > Preference > Performance
    the type of file you were working on,
    machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
    what troubleshooting steps you have taken so far,
    what error message(s) you receive,
    if having issues opening raw files also the exact camera make and model that generated them,
    if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
    etc.,
    someone may be able to help you (not necessarily this poster).
    a screen shot of your settings or of the image could be very helpful too.
    Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
    http://forums.adobe.com/thread/419981?tstart=0
    Thanks!

  • Bridge error "there was an error writing metadata"

    If I want to add keywords to my RAW files in PS adobe Bridge I get regularly (usually) a message as follows "there was an error writing metadata nr img 1326 CR2". How can this be resolved ? iMac
    grts
    ingridMG

    How can this be resolved ?
    It might have several reasons but my best first guess is that you want to much at the same time?
    When adding keywords Bridge is not capable on multitasking. When the activity bar starts to spin (bottom left in bridge window) you best wait until the first bunch has finished.
    My second guess is about XMP files, Bridge does not write metadata in the Raw file itself but to a separate XMP file with the same file name but different extension (.xmp). By default the XMP files are hidden in Bridge (you can see them in the Finder folder structure, the moment you make changes in ACR, add rating and or labeling as well as metadata and keywords the XMP files get's created) and using the menu view/ show hidden files/ they will show in the content window.
    It might be you have a locked file or not the correct permission. So also use your Apple Disk Utility to check and repair permissions.

  • Writing metadata to media-file

    Hello everybody,
    I'm developing an application for viewing/editing metadata of media files (mainly MP3). Therefore I'm using JavaFX 2.2.
    Viewing works like a charm, but I'm currently stuck at the editing part.
    I've tried media.getmetadata().put("string", object) but this throws only an UnsupportedOperationException.
    Am I doing anything wrong? Or is there any other way writing metadata to media files without using external libraries?
    Thank you in advance

    is there any other way writing metadata to media files without using external libraries? No.
    JavaFX media libraries are currently only support playback and not editing (even for metadata).

  • Error Writing Metadata

    I recently upgraded from LR 2 to LR 3.2, the thumbnails at the bottom of the bottom of the Library screen have an ! imposed over them along with the message "Error Writing Metadata".
    What did I do wrong & how do I fix it?

    Dorin,
    Your solution woked pefectly, my problem is resolved!
    Thanks for your help.
    David

  • Unknown Error Writing Metadata

    Scenario: After editing photos in Lightroom I select a bunch to be edited in Photoshop CS3 beta, editing a copy with Lightroom adjustments. In Photoshop the only thing I do is run a batch that runs Noiseware then saves and closes each file. After doing this, about 70-80% of the completed files have an exclamation in the upper right hand corner of the photo in the Lightroom thumbnail. Clicking on the exclamation point displays this error message - "There was an unknown error while writing metadata to this photo - retry?" Comparing metadata between the raw photo and the tiff reveals no difference in metadata. The only difference is that the affected tiffs are not rotated for display properly. If I click on the "Retry Metadata Export" button the exclamation point goes away, but the thumbnail still needs to me rotated manually. Anybody seen this one?

    Yep, LR see a discrepancy and wants to know how to fix it instead of asuming an overwrite. Otherwise edits elsewhere may be inadvertantly overode before you ask Lr to read them.
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core, Pentax *ist D
    http://donricklin.blogspot.com/

  • PSE5 not writing tags to photo files

    Having invested hours, weeks, and months in the process of tagging my many thousands of family photographs within PSE5, I am dismayed to find that having taken the manual step of writing the tags to the files, that only some of them have indeed done so. Quite a few of my photo files are showing up in Windows Explorer with the tags I have given them safely in place - great. However, twice as many appear to not be tagged at all. Can anyone explain to me what has happened and how I can rectify it, please? The prospect of having to tag them all again leaves me wanting to go and stick my head in a blender.
    A second problem is that, inexplicably, PSE5 recently started creating duplicate photo files with a "edTMP" suffix - they recreate the exact same file with the exact same file size. The only difference is that, where tags have been saved to a photo, the "edTMP" version does not include the tags. So, I just delete these files, but with the number that PSE is creating, it is a very time consuming job. Does anyone have any idea why this is happening and how I can stop it, please?
    Many, many thanks in advance to anyone who can help me rectify these really maddening issues. Thanks! And best wishes.

    First problem - It might be possible that while using 'Write keyword tag and properties info to photos' option, Organizer may have shown some errors (saying like 'Skipping invalid files'). As a result write operation may not be applied on some files. This may happen if there are some permissions issues with images. Please check that all your files are writable.
    Second option - This is an extension of first problem. Whenever Organizer fails to do any file operation (in your case 'Write keyword tag..' option), it creates a temp file. There is no way of deleting these files from withing Organizer (you need to delete them manually).
    ~Andromeda

  • "Error writing metadata to" message and extended attributes

    After being frustrated by this error message in Bridge while trying to apply keywords to various image files I finally took the time to investigate, and I think I found the cause of the issue. In a nutshell, if the extend attribute "com.apple.FinderInfo" has not yet been created for a given file, then this message appears.
    The start of the puzzle was that some files would take the keyword and others would not. After observing identical permissions on files that worked and files that did not, I noticed that in a terminal listing of the files in question, some files had extended attributes and some did not (extended attributes are identified by an @ symbol when running ls -la in a terminal window. For example:
    -rw-rw-rw-@   1 mike  staff  26131946 21 Jan 23:56 120114-133059-4612.cr2
    -rw-rw-rw-    1 mike  staff      5710 21 Jan 22:42 120114-133059-4612.xmp
    -rw-rw-rw-@   1 mike  staff  27200794 17 Jan 17:52 120114-133145-4613.cr2
    -rw-rw-rw-    1 mike  staff      5702 21 Jan 22:42 120114-133145-4613.xmp
    -rw-rw-rw-@   1 mike  staff  26973498 21 Jan 23:07 120114-133149-4614.cr2
    -rw-rw-rw-@   1 mike  staff      6648 21 Jan 23:19 120114-133149-4614.xmp
    As you can see, the file called 120114-133145-4613.xmp has not extended attribute, but the file 120114-133149-4614.xmp does. The former throws an error when applying a keyword, the latter does not.
    So I dug a bit further and it appears that when the file attribute called com.apple.FileInfo is missing from an xmp file, metadata cannot be witten. The contents of this extended attribute for a working XMP file look like this
    $ xattr -l 120114-133058-4611.xmp
    com.apple.FinderInfo:
    00000000  54 45 58 54 43 52 61 77 00 00 00 00 00 00 00 00  |TEXTCRaw........|
    00000010  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |................|
    00000020
    According to specs I found googling, the first 4 bits identify the file type (TEXT), and the next four identify the file creator (CRaw). IOW no file-specific info seems to be present.
    So as a test, I simply copied the contents of com.apple.FinderInfo from a file that had it to a file that didn't. Once the file that didn't received the new attribute, metadata writes worked. The command I used for the copy was
    xattr -wx com.apple.FinderInfo "`xattr -px com.apple.FinderInfo 120114-133534-4633.xmp`" 120114-133041-4602.xmp
    It also appears that this metadata is written by Bridge based on some unknown trigger, because occasionally during my investigation a file that previously would not take metadata suddenly did, and once I knew to look for extended attributes, in every case the file in question suddenly had com.apple.FinderInfo extended attribute.
    So...I'm not sure if this is a bug in finder or in bridge, but it is definitely a bug and needs to be addressed.
    ...Mike

    I have tried purging the cache, and also deleting it entirely and starting over, to no effect.
    Mike
    just did a quick try and don't know if it is the right way.
    Using Lightroom 3.6 (not very familiar with Lightroom) and Bridge 4.0.5.11 on MacOSX 10.6.8
    I randomly choose some CR2 files that where somewhere on my system and copied them to a new folder. Imported them in Lightroom and added some rating and a few keywords. (with setting metadata to XMP file active)
    Then went to Bridge and opened the same folder. After caching Bridge showed the info as filed in Lightroom. Added some keywords to all files without problem. Went back to Lightroom (restarted it and had to choose read metadata menu. After this no problem to read new keywords form Bridge. But they only show in Italic because the have not been made persistent in the Bridge keyword list, however this is as expected behavior.
    Tried a develop setting and that was also showing in Bridge correctly. Went a few times back and fort (files in Lightroom showing a memo with Exclamation sign top right of the in Bridge changed thumbnail asking for reading metadata).
    Is this about the way you mean to describe?
    And when having set Automatically export changes to XMP have you set this option in both Lightroom and Bridge (this s to be found in the Camera Raw preferences 'save image settings in: sidecar XMP')
    And there are a few things to refresh also in Bridge besides the deleting of the cache file, you can also delete the Bridge plist file from the user library preferences and restart Bridge holding down option key and chose reset preferences. And did you run the check and repair permissions for your system also?
    I tried to look in terminal but could not find a way to use the ls -la command on the folder with changed files so no comparing on that side I'm afraid.

  • Lighroom 3 writing metadata to image files?

    Hi,
    I have been wondering why my backups (differential) weregetting larger than they should, and I noticed that some of the files (.psd and .jpg, and mayde few .tiff) were modified. Interestingly, I do not see this happening to cr2-files, that I mostly use. After trying to figure out what's going on I noticed that corresponding xmp-files were modified also. This is not the issue due to their small size, but still I had not edited images that were changed for quite a while.
    Change that I see in xmp-files is rather large, and presumably related to Adobe's change in xmp-data structure. Eg.
    <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.3-c007 1.136881, 2010/06/10-18:11:35   
    ">
    <x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 4.2-c020 1.124078, Tue Sep 11 2007 23:21:40   
    ">
    In addition to the sample above, whole xmp structure is changed. So I presume that maybe LR is writing metadata chages to xmp in the background?
    What I find disturbing is that when checking changed jpg files, I saw the similar data written into the jpg files also (files were created with oldish Canon 20D, and not edited for quite a while). These are examples from changed jpg-files (not the same from which the abone xmp-data change was taken, but similar change is visible in the corresponding XMP):
    Also jpg-file from offset 0x04 was changed from "50 60" to "51 18". Also offset 0x10 was changed (16 bits).
    I have Lightroom configuration option "Include develope settings in Metadata Inside JPEG, TIFF and PSD Files" not selected. The option "Automatically write changes to XMP" is selected. To my understanding neither of these should not have impact to the issue. Is there something else I should check?
    Change is made most likely by Lightroom 3.5 version, and has not occurred with previous versions. I have not notices this happening with 3.6, but I have been using it only few weeks. Is this known issue with previous version 3.5, or am I missing something obvious?
    System running is Windows 7 pro 64bit. I have not have any issues with LR lately, except crashes that I white about a week ago.
    Any advice on what's going on?

    So I was missing something. Thank you Hal.
    I had not realised that XMP goes inside of actual image files with those file types. Obviously my new backup routine spotted that, as I was on backuping only modified/new files.
    I would much prefer that also with above mentioned file types XMP-data would be stored in sidecar files instead of modifying the original file. To support this there are two arguments that I think are valid:
    1) modification of the file is always risky (and spesifically, with image originals I prefer to avoid that),
    2) modification leads to the fact that "smarter" backup strategies relying on "full backup" supported with differential or incremental backups lead to unnecessary long backuptimes and media consumption.
    That said, I prefer to have XMP-data also outside of the catalog so that other tools can also utilise it  (further, in addition to the catalog with sidecars I have sort of failover approach, and some of you may now say "belt and syspenders" after mentioning backups...).
    Is there a way to have all file types to utilise sidecars rather that modifying original file?

Maybe you are looking for