Skip to main content
Adobe Photoshop Family

5 Messages

 • 

400 Points

Sun, Apr 26, 2015 6:07 PM

Solved

Lightroom 6: Does not export all selected images

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.

Responses

5 Messages

 • 

400 Points

6 years ago

I have been getting a lot more failures, including two or three failures in succession trying to export a single image. This is unworkable so I'm going to have to revert to version 5.6.

3 Messages

 • 

80 Points

6 years ago

I got yesterday random error of one totally blank (white) picture when exporting batch of canon raws to jpg.

13 Messages

 • 

224 Points

6 years ago

I am having the same problem. It is causing the export to completely give up and not run the portraiture that I have set up to run after the export.

It appears to be completely random. The first time I try the export, 3 files "could not be opened". The second time, 6 files (which are different from the 3 that failed the first time) "could not be opened". It happens to both my raw file and my psd files.

Until this gets fixed, I can't use Lightroom because I need portraiture to be run. I am going to have to revert to an old version.

2 Messages

 • 

72 Points

6 years ago

With Lightroom 6 and Windows 8.1 exporting single RAW images to 8-bit TIFF on a specific drive/folder/subfolder I have the same problem SPORADICALLY. I get the error message: "Some export operations were not performed. The file could not be opened ()". But re-doing the export (with no changes) works after several tries. Needlessly to say, this is tremendously frustrating. Re-importing the images doesn't help. Starting a new LR Catalog doesn't help. Temporarily exporting to a folder on the Desktop doesn't help. And, yes, I did install the latest update to LR6.

13 Messages

 • 

224 Points

6 years ago

I may have found a workaround. Try closing Bridge before exporting from Lightroom.

3 Messages

 • 

82 Points

I don't have Bridge installed, even, yet I have this problem :-/

2 Messages

 • 

72 Points

6 years ago

I tried Amy Johnson's suggestion with 4 example exports and this did work for me. Instead of Bridge, I'm now toggling between Lightroom 6 and Windows Explorer to verify that my export has shown up with a thumbnail in the desired drive/folder/subfolder. Thanks Amy!

Of course that means there is an incompatibility between Bridge (I'm using the CS5 version) and Lightroom 6. Wonderful!

5 Messages

 • 

400 Points

6 years ago

"I may have found a workaround. Try closing Bridge before exporting from Lightroom. "

I'm glad you've found a workaround. Unfortunately this won't work for me as I don't use Bridge.

5 Messages

 • 

400 Points

6 years ago

Following up on Amy Johnson's discovery I have found that if I have Faststone Image Viewer open at the directory the exported images are going into then I get the problem. If Faststone is not running, or is open at another directory, then I don't get the problem.

I don't get the problem with XnView open at the export directory

I do get the problem if Bridge is running (this is an old, CS2, version of Bridge).

3 Messages

 • 

82 Points

I confirm that. I tried to change Faststone for XnView and problem is solved.

Champion

 • 

5.3K Messages

 • 

95.7K Points

"I confirm that. I tried to change Faststone for XnView and problem is solved."

Have you upgraded to CC 2015.1.1 / 6.1.1 or later? This problem was fixed in that release. Do Help > System Info to verify.

3 Messages

 • 

82 Points

You're right. Problem was actual for 6.0 version. Sorry for my out-of-date/vague comment.

3 Messages

 • 

82 Points

I have 6.1.1 and during a large export Lightroom still shits down. In fact sometimes I get a blue screen of death

Champion

 • 

5.3K Messages

 • 

95.7K Points

"Problem was actual for 6.0 version."

If you decide to upgrade, do not upgrade to 2015.2.1 / 6.2.1 -- it's plagued with problems, and even Adobe suggests downgrading to 2015.1.1 / 6.1.1 if you encounter serious problems. See here for how to install 2015.1.1: http://www.lightroomqueen.com/how-do-...

Champion

 • 

5.3K Messages

 • 

95.7K Points

"I have 6.1.1 and during a large export Lightroom still shuts down. In fact sometimes I get a blue screen of death"

Those are much different symptoms than the problem reported and solved in this thread, in which the export completes with a dialog box saying "Some export operations were not performed."

This topic discusses the a more general problem of LR actually crashing (exiting abnormally) when exporting: http://feedback.photoshop.com/photosh.... Adobe is actively working on a next release to fix all the serious issues reported with CC 2015.2 / 6.2.

3 Messages

 • 

82 Points

Sorry about that

Champion

 • 

5.3K Messages

 • 

95.7K Points

No need to apologize -- this forum isn't the easiest in which to find things, to say the least.

3 Messages

 • 

82 Points

Thanks for your warning and information.

13 Messages

 • 

224 Points

6 years ago

Following up some more. Similar to Faststone Image Viewer as Nick Gray reported, I can keep Bridge open but have to move out of the directory that I am exporting to. If I stay in the export directory then the problem occurs.

4 Messages

 • 

100 Points

6 years ago

This same thing has been happening to me since installing LR 6 about a week ago.

I normally export master edits as tiff files. Problem is exactly described by original poster.

Bridge seems to be involved as well. Will try closing bridge or moving to another directory when I export.

LR 6 is not done cooking, that's for sure.

4 Messages

 • 

100 Points

6 years ago

Yes, with Adobe CS6 Bridge opened in another window, when an export is done to the directory Bridge is monitoring, LR 6 vomits on a few of the file exports. Very consistently, no matter which drive, or directory or file type I'm converting to. Close Bridge, the problem goes away for me.

3 Messages

 • 

90 Points

6 years ago

I do not have Bridge. Having the same problem as everyone else. It is very annoying.

3 Messages

 • 

90 Points

6 years ago

export not working for jpeg, or tiff, all the time, may export correctly one out of several tries. This is very annoying. I have un-installed and re installed LR at least three times with the same results. I Do Not have Bridge. The problem with the touch keyboard opening when trying to add keywords has been solved. Did not have this export problem with LR4 or LR5. Now some times when I export , it says cannot open the raw file , I go to where I export them and it is there, This has happened once out of a dozen exports???

12 Messages

 • 

326 Points

6 years ago

Finally had this happen to me. Win7, LR CC. Attempted to export 40-45 images, 1 did not export.
Bridge not installed.
No image viewers running, nothing monitoring the directory except File Explorer open and showing the output directory.
Never had this problem with LR5.

1 Message

 • 

60 Points

6 years ago

Same here. I didn't find any correlation between the number of the files to be exported and the frequency of this error occurrence: sometimes 100+ will export fine, sometimes one in a group of 10 will fail. Didn't tried yet the suggested above workaround with restarting the application prior to exporting.