Lightroom 6: Does not export all selected images

  • 39
  • Problem
  • Updated 2 years ago
  • Solved
  • (Edited)
With Lightroom 6 on Windows 7 I have exactly the same problem as described at http://feedback.photoshop.com/photosh...
with Lightroom 5.4.

I select a number of images and use the Export dialog, exporting to JPEG. After the export is finished I get a dialog box saying "Some export operations were not performed. The file could not be opened ()", and then lists the file names of the images that were not exported.

If I delete the exported JPEGs and try again a different subset of the selected images gets exported. On average around 20 out of 70 selected images don't get exported.

Watching the directory where the images are being exported with a file viewer while the export is in progress I can see that the images that are later shown in the "not exported" dialog box list are in fact being created in the target directory but are quickly deleted.

I have had one example of exporting of a single image failing with exactly the same error message.

I have never had this problem with version 5. I just ran an export of 126 images using Lightroom 5.6 which completed successfully, as has always been the case with version 5 and before that with version 4.
Photo of Nick Gray

Nick Gray

  • 5 Posts
  • 1 Reply Like

Posted 4 years ago

  • 39
Photo of John R. Ellis

John R. Ellis, Champion

  • 4171 Posts
  • 1108 Reply Likes
Julie, I redid the traces of exports in LR 4.4.1, LR 5.7.1, and LR CC 2015.0.1, and Save Image in PS CC 2014 / ACR 9.0 (all on Windows 8.1). I observed the same things as in my previous report and confirmed some of my guesses about the metadata.

I've uploaded a folder of all my traces, detailed notes on how they were made, and Exiftool dumps:

https://dl.dropboxusercontent.com/u/2...

I encourage your engineers (and anyone else) to examine these in detail, and I'd be glad to confer with any interested party on- or off-line.

Observations

- LR 4, LR 5, and ACR 9 use a single pass to export a .jpg.

- LR 6 uses three passes: 1) write the .jpg, 2) read the .jpg back into memory, 3) write .jpg.swp and rename to .jpg.

- The first pass writes all of the metadata, using a typical layout for the EXIF IFDs (as used by LR 4 and 5).

- The second pass opens the file for read/write access even though it is just going to read the file into memory.

- The third pass rewrites all of the metadata, using the problematic atypical layout described in this bug report:

http://feedback.photoshop.com/photosh...

This pass changes the Region Area fields, the XMP History fields, and Instance ID field but no other metadata field.

The LR exports used the exact same export preset, with these options: Export To: Specific folder, Image Format: JPEG, Quality: 60, Color Space: sRGB, Metadata: Include All Metadata (no other options checked). The preset is included in the folder above.

Fixes

As I described above, there are three possible fixes that would guarantee no conflict with Bridge, other file viewers, backup programs, and utilities like Dropbox:

- Use a single pass to write the file, as LR 4 and 5 do, ACR 9 does, and nearly every other program does. Why were the additional passes added to LR 6? Architecturally, there is no need for the inefficiency of additional passes. (Perhaps the additional passes were added by the engineers implementing face recognition, since the only non-history fields changed on the third pass are the Region Area fields.)

- Keep the file open throughout all three passes. (Don't close the file at the end of the first and second passes, but instead seek back to the beginning.)

- In the second pass, open the file for read access rather than read/write access. Then there would be no sharing violation as the other programs and LR both read the file concurrently. This may be the easiest patch but is least desirable, since it still allows other programs to read stale metadata from the file (as they're doing now).

The latter two fixes are just very simple patches to the current inefficient multi-pass design, but at least they ensure a lack of conflict with other programs.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4171 Posts
  • 1108 Reply Likes
To further increase confidence in my observations, I traced LR 5.7.1 and LR 6.0.1 on OS X 10.10.3 using the "dtruss" tool. I added these traces and details to the Dropbox folder linked above.

As on Windows, Mac LR 5 writes exported .jpgs with a single pass, while Mac LR 6 uses three passes.
Photo of Patrick Fondanèche

Patrick Fondanèche

  • 13 Posts
  • 2 Reply Likes
Impressive!
Photo of Julie Kmoch

Julie Kmoch, Sr. Development Manager

  • 103 Posts
  • 40 Reply Likes
John, I'll file a bug to have someone take a closer look. Thank you for the depth of your research on this.
Photo of Sharon VL

Sharon VL

  • 8 Posts
  • 0 Reply Likes
I am having the same problem. Windows 7 pro 64 bit. I don't use bridge or an image viewer.

Sharon
Photo of Julie Kmoch

Julie Kmoch, Sr. Development Manager

  • 103 Posts
  • 40 Reply Likes
To update, we are able to reproduce this and are working on a fix. In the meantime, if you are exporting JPEGs, one workaround you can try is to check the "Limit File Size To:" option (and set the limit high assuming size is not actually a concern). This should avoid the path that's causing the second update.
Photo of Kaur I

Kaur I

  • 3 Posts
  • 0 Reply Likes
I can consistently make LR 6.1 fail on the photo export process. The procedure is as follows:

1. Start with reasonably large batch of files to export ~50+
2. Export all to jpg, with resize, sharpen applied
3. While the export is in progress, I use jpg viewer to browse in the same folder where the jpg files are exported trying to browse into the appearing files
4. The end result is almost always the LR throws up error message "Some export operations could not be completed", following the list of files which were not opened. See the screenshot below:

http://kaurilves.com/clients/LR_61_Ex...

I hope you guys are planning to release the fix asap because it is as critical error as it can be.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5183 Posts
  • 1051 Reply Likes
If you skip step three, does it work?
Photo of Kaur I

Kaur I

  • 3 Posts
  • 0 Reply Likes
Haven't had the time to test it. Also, first batch of export what I did with LR 6.1 without poking around in the same folder actually produced one completely white jpg image out of 70.

But limiting the file size to very large number in export module seems to avoid the issue.

BTW, for jpg browsing I am using FastPictureViewer 1.9

So far I will just keep on using LR 5.7, which works as it should.

Good luck with the bugfix and keep up the good work. I understand that sometimes the commercial pressure can introduce some unwanted side-effects in the development side, keep up the good work but please produce fix as soon as possible :)
Photo of Christian Lee

Christian Lee

  • 2 Posts
  • 0 Reply Likes
I get this error every time I export large batch since I upgraded to LR 6.

I have to wait until the export is complete before I leave or go to sleep.

What a waste of my time. I have large export to do at least 4-5 times a week.

It's a shame that this problem is still not fixed.
Photo of Andreas Schäfer

Andreas Schäfer

  • 4 Posts
  • 2 Reply Likes
Some notes to intermediary files: if the processing of export files is done in the destination folder it could happen that other processes, e.g. also indexing, interfere the processing by accessing the intermediate files.

Some suggestion: why don't do processing in a temp folder from the current user. There no indexing will be done and normally the only process accessing the file is Lightroom. If processing is finished the resulting file can savely moved to the destination folder.

This should avoid all access failures of Lightroom.

Best, Andreas.
Photo of Christian Lee

Christian Lee

  • 2 Posts
  • 0 Reply Likes
That did not worked.

Still no fix from Adobe.

Adobe Lightroom is waisting my time.
I have to do the export in 3 or 4 times.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4171 Posts
  • 1108 Reply Likes
Which method did not work?
Photo of Sharon VL

Sharon VL

  • 8 Posts
  • 0 Reply Likes
It doesn't help for my errors either. I always export to a different destination folder.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4171 Posts
  • 1108 Reply Likes
Which method did not work?
Photo of Sharon VL

Sharon VL

  • 8 Posts
  • 0 Reply Likes
Exporting to another folder.
Photo of Sharon VL

Sharon VL

  • 8 Posts
  • 0 Reply Likes
My problem now is that when I export several photos, some of the photos are blank. They will show a thumbnail but when I click on the thumbnail - the image is blank.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4171 Posts
  • 1108 Reply Likes
Try the workaround suggested by the Julie Kmoch (Adobe manager) above:

http://feedback.photoshop.com/photosh...

Set the Export option Limit File Size To: to be 30000K (30 MB). This won't affect the size of the exported JPEG, but it does trick LR into avoiding the bug.
Photo of Sharon VL

Sharon VL

  • 8 Posts
  • 0 Reply Likes
Thank you, John!
Photo of GpsM

GpsM

  • 2 Posts
  • 0 Reply Likes
Very bad problem. I need to get my job finished very fast. Just decided to change from LR 4 to 6 and run into this bug.
Needs such long time, an Intel I7 (4x4,0 GHZ) needs as long as my old Pentium IV dual core with LR4. Please fix it soon!
Photo of Roy Evans

Roy Evans

  • 2 Posts
  • 0 Reply Likes
i tried the 30 mb setting on the limit file size several times and an export of 27 pictures form DNG to jpeg at a reduced size of 1600 px long side . With these settings it would not let me set the Quality which is a problem in its self. I did this 3 times and the export was successful. Before I had to do 3 exports to get them all exported. before.

Because you can not set the quality with this setting, this is not a acceptable solution especial for picture going to the web.

While it appears that the problem is being worked on, this has been in the support blog for two months. which is about the same time the problems with the extension manager has been hanging.

We are not happy campers.
Photo of Sharon VL

Sharon VL

  • 8 Posts
  • 0 Reply Likes
Yes, Roy is right. If I set the limit file size to 30,000, it won't let me set quality and I end up with a file that is 759kb - way to big for a web gallery. So this doesn't work!
Photo of John R. Ellis

John R. Ellis, Champion

  • 4171 Posts
  • 1108 Reply Likes
If you set the limit to the desired maximum size, e.g. 250K, then that should also work around the bug.
Photo of Sharon VL

Sharon VL

  • 8 Posts
  • 0 Reply Likes
Unfortunately, that solution won't work for me as it forces some photos to be too small and others to be too large. I need quality to be the decider.
Photo of Eric Tischler

Eric Tischler

  • 2 Posts
  • 0 Reply Likes
I'm having this issue, too. The only solution I've found so far is to re-select the photos that did not export, and re-export. I never had this problem with LR5.
Photo of Michael MacDonald

Michael MacDonald

  • 2 Posts
  • 0 Reply Likes
I just edited a massive set of wedding photos only to notice 50% of the 400 wedding photos have the .swp files and deleting the .swp, of course, makes the jpeg unopenable. This is the 3rd week in a row i've dealt with this. I'm pretty sure the LR team doesn't have QA. How would something so ket to the feature workflow be missed? Are they outsourcing development and QA to 3rd grade kids in Africa? I only wish there were a viable competitor to LR as I'd jump ship in a heartbeat.
Photo of Michael MacDonald

Michael MacDonald

  • 2 Posts
  • 0 Reply Likes
And to throw gas on the fire now none of my photos will export if I attempt to export more than one at a time. This is pretty absurd.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2668 Posts
  • 344 Reply Likes
Presumably these JPGs are from your exports, not your master photos.

It sounds like some other process is grabbing ahold of the JPGs before LR can finish with them: time-machine, dropbox, virus scanner, idrive. What happens if you temporarily disable virus scanners and backups?

Does it matter where you export them to: internal drive, external drive, folder under User library or off the root of your hard-drive, etc?

If you scroll up a ways in this thread, a way to change how LR does the exporting is to set a larger-than-needed filesize limit, which I think will cause photos to be exported with maximum quality, that may or may not be what you're wanting.
Photo of Sharon VL

Sharon VL

  • 8 Posts
  • 0 Reply Likes
Steve, using the larger than needed file size doesn't work if you are exporting for your website. You end up with huge files or files that aren't big enough. Not being able to set file quality is very bad.

Sharon
Photo of Amy Johnson

Amy Johnson

  • 13 Posts
  • 2 Reply Likes
See if you can find any program at all that is viewing the export directory at the time of export - Windows Explorer, other picture editing software, Adobe Bridge, etc. Then either exit that software or move to a different directory. It's a temporary fix that works for me until Adobe fixes the problem.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4171 Posts
  • 1108 Reply Likes
This problem appears to be fixed in LR 6.1.1 / CC 2015.1.1.
Photo of William Dwyer

William Dwyer

  • 1 Post
  • 0 Reply Likes
I thought I was having this issue and it turned out that exporting my images to the c:\users\%user%\pictures\ folder structure was giving me access denied.

I got the same error

I believe this happened when I (using lightroomcc latest) upgraded from win 7 -> win10. I then associated my microsoft account @hotmail... with my user account from win 7. The lightroom app ran from that point on in the security context of my @hotmail user and this user while directly associated with my old win7 username didn't actually have permission to any of my 'personal' folders like my docs, my pictures, etc..

I resolved by using the file security and taking ownership of all files then replacing all permissions to include appropriate account.
Photo of MJ Klein

MJ Klein

  • 48 Posts
  • 16 Reply Likes
i've been getting the blank (white) jpeg malfunction occasionally. however, i can see thumbnails so they look perfectly normal until you try to view them. i discovered this after uploading to Flickr where a photo displayed white.
Photo of Melody Cook

Melody Cook

  • 2 Posts
  • 0 Reply Likes
Not sure if this is even related, however, when I try to export my images from LR 5.7 into PSE 13, I get the error "file DSC_1108.dng could not be written". What am I missing?
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5183 Posts
  • 1051 Reply Likes
Check in your OS and make sure that you have full write permissions for the location to where you are trying to export.
Photo of Melody Cook

Melody Cook

  • 2 Posts
  • 0 Reply Likes
I do. A tech from Adobe fixed that for me. But still having the issue.
Photo of Steve Struthers

Steve Struthers

  • 1 Post
  • 0 Reply Likes
Having a similar problem. I'm trying to export JPEG images I shot in a HDR sequence, and I keep getting the same error message, over and over again:

The file could not be written
DSC02041-HDR.dng

I didn't ask Lightroom CC 2015 to write it as a .DNG file, dammit!

Also getting the same problem with exporting plain old JPEGs. The only thing I might have done that might explain this, is changing file permissions to full control on my C:\Pictures as Windows 10 wasn't letting me write files to that folder without administrator privileges, and yet I am already set up as an administrator.

I wish there was an emoticon that would express how mad I am about this!
Photo of John R. Ellis

John R. Ellis, Champion

  • 4171 Posts
  • 1108 Reply Likes
Two troubleshooting steps:

1. Try exporting to C:\Users\username\Pictures. If that works, then it's likely you're still experiencing permission issues with C:\Pictures.

2. If exporting to to C:\Users\username\Pictures doesn't work either, then verify in Help > System Info that you are running LR CC 2015.1.1 or LR 6.1.1. That most recent release fixes the bug described in this topic. (The Adobe update process has fooled many people into thinking they've been getting the recent updates when in fact they haven't.)
Photo of jim doukakis

jim doukakis

  • 3 Posts
  • 0 Reply Likes
I upgraded to 6.2 today and after a few minutes of exporting the application fails again and I have to close it. Not solution found yet