Lightroom: Sidecar file has conflict (but there is no sidecar file...)

  • 1
  • Problem
  • Updated 7 years ago
Misc jpegs have a "sidecar" conflict. They are not sidecars, nor do they or have they ever had a sidecar. There seems to be no way to clear this condition (saving or reading metadata does not illicit an error, but does not help either). I assume the problem is due to some xmp issue, but the images seem OK to me (and otherwise to Lightroom too)...

UPDATE @2011-11-09: Most recent problem was caused by an older version of ImageMagick's mogrify that was incompatible with Lightroom-written metadata.

I would like to suggest a better error message, as a minimum, and if saving metadata fails, that fact should be clearly expressed.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes

Posted 7 years ago

  • 1
Photo of Anita Dennis

Anita Dennis

  • 75 Posts
  • 24 Reply Likes
What was the error message that you received?
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Anita,

I've fixed all the cases I knew of so hard to re-check - there is no way to round up a collection of photos having metadata conflicts... But, I have re-created the problem to provide more info:

1. the "error message" popup associated with the thumbnail icon is "Sidecar file has conflict".

2. When attempting to save metadata, there is no error message whatsoever - it just silently ignores that metadata was not saved.

3. When Lightroom has a problem reading an image, it says "Lightroom has encountered problems reading this photo" - no indication of what the nature of the problem was.

Thanks,
Rob
Photo of Linda David

Linda David

  • 2 Posts
  • 0 Reply Likes
I am having a very similar problem. In Lightroom3 I've exported a JPEG to NIK HDR Efex and when I save it and it comes back into LR it is okay. But when I do some Develop adjustments to this image I get the message "There was an unknown error while writing metadata to this photo" and get the choice to retry or use metadata from file which then wipes out the LR changes I made. It says "sidecar file has conflict" but I'm not using sidecars. HELP!!!
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
I think sometimes when Lightroom says "sidecar" it really means xmp, even when its embedded.

My guess: HDR Efex wrote the jpg (metadata block(s)) in a fashion that Lightroom was not happy with.

That's what all my similar problems were. I corrected them using ExifTool and a considerable amount of "Sherlock Holmes" effort - not for the squeamish...

I assume you have auto-write xmp on, which is why the problem happened upon develop adjustment.

I'd report problem to Nik too.

Rob
Photo of Linda David

Linda David

  • 2 Posts
  • 0 Reply Likes
I've been using HDR Efex in Lightroom3 for 8 months with no problem. I just started getting this error about the sidecar on 12/17/11. I don't have the auto-write xmp turned on but since this problem started, I've tried it both turned on and turned off and it doesn't help. The problem started right after I ran my registry cleaner program which also created problems in other programs.

Thanks for responding.
Linda
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
The root of the problem may be due to a change in Lightroom - it went through some significant changes around 3.5-ish, dunno 'bout 3.6. Dunno if there were any HDR Efex changes recently...

Anyway, I'm assuming "relatively normal" operation, such that develop setting changes would not illicit a sidecar complaint unless you saved xmp.

If your system or Lightroom or registry is all whack-o then I suppose all bets are off... - maybe time for the big guns to chime in (Adobe)...
Photo of Ron Bearry

Ron Bearry

  • 2 Posts
  • 0 Reply Likes
I am having the same problem. I just purchased the Nik software today. I ordered the Compete Collection for Lightroom and I have to say I am a little annoyed. Yes, software has bugs but there are other annoyances like the fact that I cannot open as a PSD in Silver or Color Efex even though it's in the Lightroom menu as an option. This is kind of sloppy.