Error writing to Metadata - Bridge CS5.51

I see the long thread, and yet no answers, and I have the same problem. It is a Bridge CS5.5 issue as everything works fine in Bridge CS5.

Yammer P,
Adobe has many issues to work on, and from what I gather Bridge is s low priority.
The first part of last year we had some Adobe visitors giving much welcomed input to questions. Lately I have seen nothing, but then it does seem like there are no complex issues except this one.
If it was a burning issue for me I would find an avenue to Adobe, outside of this forum, to keep them aware that the problem is still there, and it is important to address.
It appears it is not easily repoducible, but once the condition is found it may take an Adobe tech to seize control of that compter remotely and see how this issue looks.
Your suspect at this time is the database I believe, perhaps they have other tools to see what is happening there.

Similar Messages

Error writing XMP metadata

I'm running version 1.4.1 under Vista Home Premium. I have imported several hundred jpegs from my HDD and some of these have a downward arrow at the top right of the thumbnail in Library view. On clicking this, a dialog tells me the metadata has changed in Lightroom and I need to save the changes to disk. On clicking "save"I get an error dialog stating "'Writing XMP metadata' did not complete successfully". I've also tried selecting a whole folder of jpegs, or a batch selected by Keyword, and updating them all at once using the "Metadata - Save metadata to files" menu option, but more often than not there are some photos in the batch that will not write the metadata successfully. I have been unable to detect any pattern to the images "chosen" for rejection. I think they are all pictures that were originally scanned from prints, but so were many others that update successfully. The metadata I am trying to update on them consists of Keywords and Capture dates.
Can anyone suggest how I might get these files to update?

I posted a similar query a little while ago, and judging from the response this was not widespread so I reasoned it was something peculiar to my catalogue.
After extensive testing of my set-up I could find nothing - indeed the XMP data APPEARED to be written fine to the XMP segment of the jpegs, etc. and to the XMP sidecar files for the RAW images - just Lightroom was sure it wasn't OK.
To cut a long story short, I found that I had a spurious and invisible control character in one of my metadata fields. I guess I inserted this character when I was fumbling round the keyboard trying to find the correct key combination for the '©' (copyright) character. Unfortunately I did this when setting my standard metadata template I use on all imports!
When Lightroom writes the XMP data it doesn't write this control character, however the character exists (invisibly to the Lightroom user) in the catalogue database. As a result the file-based and database versions will never match - with manual or automatic syncing - so you (nearly) always get the 'File Metadata needs updating' arrow icon.
To check this out you need to choose an image and remove metadata one field at a time - trying the save between each change. When it saves OK then you have found your culprit and can sort out the rest of the images.
Strictly speaking this is a bug. The interface should show all characters in the database and shouldn't store in the database anything that is invisible in the GUI...

Resolving " Writing XMP Metadata did not complete successfully " Errors

On certain files, when I try to save the metadata, I get this error - Writing XMP Metadata did not complete successfully
Does anybody know why and how to resolve the issue?
Thank you.

Check if your files are write protected! For RAW files, the xmp sidecar file must not be write protected. For JPG and other non-RAW files, the image file itself must not be write protected.

Problem using Bridge CS5

I have a photoshop CS5 and it works fine except Bridge CS5.
It works fine on my Mac OSX 10.5.8 but it does not work on my new Mac OS X 10.8.2.
When I try to open Bridge from photoshop CS5, error messeage appears and it says " Error2: photoshop is undefined.Line 1->photoshop invokeBridge(false,false,".
When I click Bridge icon, error messeage says " Adobe Bridge CS5 quit unexpectedly.
Thank you so much for your help.

Scroll-down the page you will finf legacy version.
BTW here is the direct page link.
http://prodesigntools.com/all-adobe-cs5-direct-download-links.html
Read the instruction to avoid the error.

Error 6 can not reinstall CS5 illustrator or indesign

This is what has happened the last dozen attempts. Support advisor was no help. Running OSX Lion Appreciate any assistance.
Exit Code: 6
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 37 error(s), 65 warning(s)
WARNING: DS013: Payload {0175676F-8C92-49F2-9131-D0D6AD654B41} AdobeHelp 3.4.0.0 is already installed and the session payload {298CF0B0-8B47-46DF-B726-8E4BFAD5432E} AdobeHelp 0.0.0.0 has no upgrade/conflict relationship with it.
WARNING: DS013: Payload {54D89F03-8EED-4FF9-BCDF-3B2E11D448A6} AdobeColorCommonSetCMYK 3.1.0.0 is already installed and the session payload {39CB2E53-5326-4939-8B5A-0402C6EFBFE3} AdobeColorCommonSetCMYK 3.0.0.0 has no upgrade/conflict relationship with it.
WARNING: DS013: Payload {45063C56-A2A2-4FD1-A56A-A964723EEE1E} AdobeColorCommonSetRGB 3.1.0.0 is already installed and the session payload {78A53622-CDBA-49D1-A3D0-D563FB398D0C} AdobeColorCommonSetRGB 3.0.0.0 has no upgrade/conflict relationship with it.
WARNING: DS013: Payload {AC003BC0-704F-4F02-A72E-AC8B7044DE24} AdobeOutputModule 3.1.0.0 is already installed and the session payload {925ED7E4-E1B6-4544-8141-1C98A18D2E2E} AdobeOutputModule 3.0.0.0 has no upgrade/conflict relationship with it.
WARNING: DS013: Payload {1A1E5FF9-D0FD-42A3-8E18-E5E7E95E1AB4} DynamiclinkSupport 5.5.0.0 is already installed and the session payload {A8798E04-96FF-4564-9157-0D4C89CB794C} DynamiclinkSupport 5.0.0.0 has no upgrade/conflict relationship with it.
WARNING: DS013: Payload {9FBC5BF9-5019-49D6-A1B3-6BB0E2A1FA54} Pixel Bender Toolkit 2.6.0.0 is already installed and the session payload {F8918124-1CFB-4AB9-9BC2-39B961DBBBEE} Pixel Bender Toolkit 2.0.0.0 has no upgrade/conflict relationship with it.
ERROR: DS013: Verifying payload integrity : Failed with code 1
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {C7BDD22E-AD27-4B06-BEB9-F97BC4D89671} Flash Player 10.1.52.15 as it is already upgraded by the payload {DEA79551-23E3-430A-9B15-B544479B7DB2} Flash Player 10.2.153.1
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {1EC2407F-6A7B-4A3C-9F46-C812EE3D44FD} HIL Help Search 1.0.0.0 as it is already upgraded by the payload {270C312D-7EC7-474C-BEB2-79CD398E02A3} HIL Help Search 1.0.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {C7BDD22E-AD27-4B06-BEB9-F97BC4D89671} Flash Player 10.1.52.15 as it is already upgraded by the payload {DEA79551-23E3-430A-9B15-B544479B7DB2} Flash Player 10.2.153.1
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {1EC2407F-6A7B-4A3C-9F46-C812EE3D44FD} HIL Help Search 1.0.0.0 as it is already upgraded by the payload {270C312D-7EC7-474C-BEB2-79CD398E02A3} HIL Help Search 1.0.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {1EC2407F-6A7B-4A3C-9F46-C812EE3D44FD} HIL Help Search 1.0.0.0 as it is already upgraded by the payload {270C312D-7EC7-474C-BEB2-79CD398E02A3} HIL Help Search 1.0.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {1EC2407F-6A7B-4A3C-9F46-C812EE3D44FD} HIL Help Search 1.0.0.0 as it is already upgraded by the payload {270C312D-7EC7-474C-BEB2-79CD398E02A3} HIL Help Search 1.0.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {C7BDD22E-AD27-4B06-BEB9-F97BC4D89671} Flash Player 10.1.52.15 as it is already upgraded by the payload {DEA79551-23E3-430A-9B15-B544479B7DB2} Flash Player 10.2.153.1
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {1EC2407F-6A7B-4A3C-9F46-C812EE3D44FD} HIL Help Search 1.0.0.0 as it is already upgraded by the payload {270C312D-7EC7-474C-BEB2-79CD398E02A3} HIL Help Search 1.0.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {1EC2407F-6A7B-4A3C-9F46-C812EE3D44FD} HIL Help Search 1.0.0.0 as it is already upgraded by the payload {270C312D-7EC7-474C-BEB2-79CD398E02A3} HIL Help Search 1.0.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {3423F36D-004F-4DFC-8BCE-07A20B8DFBDE} Suite Shared Configuration CS5 2.0.0.0 as it is already upgraded by the payload {ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 2.5.0.0
WARNING: DW016: NOTE: Cannot set action to the payload {1EC2407F-6A7B-4A3C-9F46-C812EE3D44FD} HIL Help Search 1.0.0.0 as it is already upgraded by the payload {270C312D-7EC7-474C-BEB2-79CD398E02A3} HIL Help Search 1.0.0.0
----------- Payload: {BAE5212B-6651-4AD8-B26A-1B284D2665C6} AdobePDFL CS5 9.9.0.0 -----------
ERROR: DF024: Unable to preserve original file at "/Library/Application Support/Adobe/PDFL/9.9/Fonts/AdobeFanHeitiStd-Bold.otf" Error 0(Seq 50)
ERROR: DW063: Command ARKDeleteFileCommand failed.(Seq 50)
----------- Payload: {298CF0B0-8B47-46DF-B726-8E4BFAD5432E} AdobeHelp 0.0.0.0 -----------
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
----------- Payload: {C0AA232E-BD1B-40B5-A176-A2BEB67FFAE1} Adobe After Effects CS5 Third Party Content 10.0.0.0 -----------
ERROR: DF024: Unable to preserve original file at "/Library/Application Support/Synthetic Aperture Adobe CS5 Bundle/Color Finesse 3 Plug-in User's Guide.pdf" Error 0(Seq 1)
ERROR: DW063: Command ARKDeleteFileCommand failed.(Seq 1)
----------- Payload: {D348C659-234A-497E-9E75-92D1AB019C8C} Creative Suite 5 Master Collection 5.0.0.0 -----------
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
WARNING: DW036: Payload cannot be installed due to dependent operation failure
ERROR: DW050: The following payload errors were found during install:
ERROR: DW050: - Adobe WinSoft Linguistics Plugin CS5: Install failed
ERROR: DW050: - SiteCatalyst NetAverages: Install failed
ERROR: DW050: - Adobe AIR: Install failed
ERROR: DW050: - AdobeColorCommonSetCMYK: Install failed
ERROR: DW050: - Adobe Mini Bridge CS5: Install failed
ERROR: DW050: - Adobe Media Player: Install failed
ERROR: DW050: - Adobe SING CS5: Install failed
ERROR: DW050: - AdobeColorJA CS5: Install failed
ERROR: DW050: - Adobe BrowserLab CS Live: Install failed
ERROR: DW050: - CSXS Story Extension: Install failed
ERROR: DW050: - Adobe InDesign CS5 Common Language Files_AdobeInDesign7CommonLang-en_US: Install failed
ERROR: DW050: - Adobe Illustrator CS5: Failed due to Language Pack installation failure
ERROR: DW050: - AdobeColorEU CS5: Install failed
ERROR: DW050: - AdobeColorCommonSetRGB: Install failed
ERROR: DW050: - Adobe CSXS Extensions CS5: Install failed
ERROR: DW050: - Adobe InDesign CS5 Application Language Files_AdobeInDesign7AppLang-en_US: Install failed
ERROR: DW050: - Adobe Toolhints CS5: Install failed
ERROR: DW050: - Adobe InDesign CS5 Application Feature Set Files: Install failed
ERROR: DW050: - Adobe InDesign CS5 Application Base Files2: Install failed
ERROR: DW050: - Adobe InDesign CS5 Application Base Files: Failed due to Language Pack installation failure
ERROR: DW050: - PDF Settings CS5: Install failed
ERROR: DW050: - Adobe Linguistics CS5: Install failed
ERROR: DW050: - Adobe InDesign CS5 Common Base Files: Install failed
ERROR: DW050: - Adobe Illustrator CS5_AdobeIllustrator15en_USLanguagePack: Install failed
ERROR: DW050: - AdobePDFL CS5: Install failed
ERROR: DW050: - Adobe After Effects CS5 Third Party Content: Install failed
ERROR: DW050: - Required Common Fonts Installation: Install failed
ERROR: DW050: - AdobeColorNA CS5: Install failed
ERROR: DW050: - Adobe Buzzword CS5: Install failed
ERROR: DW050: - Recommended Common Fonts Installation: Install failed
ERROR: DW050: - Adobe ReviewPanel CS5: Install failed

It could end up being related actually. Both the Adobe Support Advisor and portions of the Creative Suite utilize Adobe Air. I would recommend troubleshooting your installation of Adobe AIR utilizing document Troubleshoot AIR installation | Mac OS.
Without the Adobe Support Advisor you will either need to contact our support team to assist with reviewing your installation logs or proceed through Troubleshoot CS5 and CS5.5 installation with install logs. The document contains the same process which I would go through if I was able to obtain your token number. All of the error messaging is publically searchable as well at Adobe.com.

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.

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.

Bridge CS5 error in writing meta data - Can't Add Stars

In trying to rate an image file by adding a star, while viewing from Content window, I can't do it either by clicking on the dots below the expanded thumb or in the thumb view below. Nor does the Ctrl button + 1/2/3/4/5 work.
No matter the file format, jpg, psd, raw or tiff. No matter the folder.
Under Edit>Preferences>Thumbnails, there is no option for checking Show Stars.
Something I must have done, but can't recall how to undue.

Did You ever get a solution? I also cannot rate or apply labels in bridge CS5 with any of the described methods. The files are not locked, the problem is with all types of files (nef, psd, jpeg, tiff). I can modify them in PS without problems. All my files are on an external hard drive. My PS is fully updated. When I ***** on the dots below the file the stars show but immediately disappear when I leave the file. Rating or label do not appear in the filter list, but in edit I can undo rating. I have administrator rigths.
We are the only ones with this problem - I have, howver, failed to see anyone state that the problems is solved.It seems that your thread stopped suddenly. Therefore this message in the hope of reviving it.
GitAmager1

Bridge CS5 - Adding metadata to RAW files is hit and miss

Can someone help me??? Bridge CS5 will only add the metadata I enter to the files it feels like doing. It is hit and miss. Some files will add it, and other files will get the message "There was an error writing metadata to 100824_Banks_06.NEF". It will go through my whole folder of RAW files, then other times it will allow one or two of the files to get the information. I am going crazy! Is this a preference setting issue, or what?

Tai Lao wrote:
Bridge is the weakest of all Adobe applications I use. It suffers from the same issues since its first release, when we were told to forgive the teething problems of any version 1 application. Now it's in version 4.x.
I actually spent most of the last two days wrestling with Bridge, and getty pretty annoyed with it. The "Error writing metadata" bug caused me no end of problems in trying to reorganise my keywording of 20,000 photos, and turning the air blue in the process.
I agree that Bridge seems to be the poor relation in the Creative Suite. I call it the Less Glamourous Sister. It needs to be 64-bit to host 64-bit Camera Raw, and it needs to manage resources faster and more efficiently.
I've spent a fair amount of time watching Bridge's activity with a resources monitor utility, and it's a very busy lady. It seems to poll several drives every second or two, accessing the registry, disk-based settings and library files regularly too, even when it appears to be doing nothing. And, even though I had indexed and cached my whole 20,000 photo collection, Bridge insists on recreating some thumbnails and previews at random intervals.*
I decided that the anti-virus software suggestion was a red herring in my case (I now realise this is the Mac forum anyway). Photos which gave an error became subsequently locked for several minutes, and I had to edit the sidecar files by hand. In the end, I worked out that, even though there is no on-screen indication of activity, Bridge is quietly working its way through every item in the Content pane, and it is this action which seems to coincide with the Metadata Error. Wait for it to end, and chances are much reduced, but not fully removed.
Oh, and Adobe's customer treatment might be debatable, but that helpful customer you quoted was a regular abuser of other forum users, so I like to see a silver lining from that post.
* Prefer Embedded thumbnails was also selected.
Message was edited by: Yammer P

Yet another "There was an error writing metadata to..." post

I know there have been several posts like this one on the forums, but I thought I'd start a new thread due to the fact that I tried a bunch of fixes that didn't work.
Specifically, I get the above-mentioned error when trying to add keywords to DNG files in Bridge CS5 4.0.4.2. The DNG files were created from Canon .CR2 RAW files using DNG Converter (both the latest version and the second-to-the-latest version).
Here's what I've done so far: I just updated DNG converter yesterday. I just updated the full suite, including ACR yesterday (6.3, I think). I just compacted my Bridge cache yesterday. I just restarted the computer. I just restarted Bridge. I just ran a full virus-check on my system. Latest Windows updates. Latest video card updates.
I've tried adding the keyword to the same file multiple times, all attempts meeting with failure. I've tried this with multiple files. Jpegs seem to work fine, DNGs don't in most cases. And that's the caveat: Sometimes, it works, but most of the time it doesn't. For example, I just added keywords to about 24 DNG files with no problem. When I tried doing the same to another batch, blammo. Problem. It seems really arbitrary, especially considering that all the DNG files were created with the same DNG converter version on approximately the same day.
Since this error is coming up only one day after updating, I'm thinking the update has something to do with it.
Should I submit this to Tech Support or does anyone have a nice fix he/she would like to suggest?
Thanks!
-Greg (Win 7, 64-bit)

Yammer P wrote:
Don't bother, I already tried it.
Besides, we're not talking about the cache, we're talking about metadata.
I know you were talking about metadata
Nevertheless, metadata are also stored in different files on our computer, not only written to the images and XMP-files. Amongs others this is in Bridge's cache and the ACR database.
As I suggested in my former post, have a look to the files in Bridge cache folder, there in "..\data\BridgeStore", with a hex-editor, especially to "FileSystem_NodesMeta.MYD", "Keywords.MYD" or "FileSystem_Nodes.MYD".
Simplified: when you f.e. click an RAW, Bridge queries if there is embedded XMP and/or a XMP file and it also checks in ACR database and the files mentioned in Bridge's cache for XMP data.
I believe Bridge queries all this locations/files every time, means when creating previews but also when adding metadata. But when it was asked to add metadata, it also would have to merge metadata and rewrite the metadata blocks in all the "cache-files" (ACR database, XMP sidecar, Bridge's cache) and of course to the images, if possible.
This is a pretty old error message (bridge V1?) and even when there is a big chance that it might be related to other things, f.e. when images are located on network drives, there also is a chance that some of those files are locked.

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 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 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.

Video metadata in Bridge CS5.1

If I add keywords to a video file in Bridge CS5.1, does it add it to the file or keep it in a separate database (i.e. like Lightroom's default behaviour)? I'm looking for a good way to manage my home videos.
Thanks for the help.

I mean is there a better program for this sort of thing or is Bridge in fact writing the Metadata to the file (is so, how can I verify...I don't see an XMP sidecar)?
Basically, I'd like to be able to accurately catalog my videos from my Handycam (.h2ts) and DSLR (.mov) as easily and permanently as I do with my photos in Lightroom. Specifically, I want to update metadata like "Date Taken" and "Keywords" so that I can sort and filter as needed.
...yes, bewildering puts it mildly

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!

Error writing to Metadata - Bridge CS5.51

Similar Messages

Maybe you are looking for