Skip to main content
Jason Abbott
Jason Abbott
Known Participant
August 27, 2011

P: 3.5RC can't publish hard drive collection

  • August 27, 2011
  • 6 replies
  • 434 views

Lightroom 3.5RC says "Can't update this collection: An internal error has occurred: assertion failed!" when I try to Publish a Hard Drive service that has modified photos. I use it regularly and have had no problems prior to 3.5RC.

    This topic has been closed for replies.

    6 replies

    F
    FeedbackCommunityMember
    Inspiring
    February 15, 2012
    Well, not exactly. Same issue with 3.6 version...
    I tried 500px plug in and Zenfolio....
    Lightroom version: 3.6 [795620]
    Version: 10.7 [3]

    I read that i have to create a new catalog and import all the pictures again, but with 65k+ pictures is not a cool project...
    any other idea?
    B
    Adobe Employee
    Bec Sowada
    Adobe Employee
    November 9, 2011
    This has been fixed in Lightroom 3.6 Public RC, available at http://labs.adobe.com/.
    Jason Abbott
    Jason AbbottAuthor
    Known Participant
    October 25, 2011
    Thank you, I appreciate the work-around.
    B
    Adobe Employee
    Bec Sowada
    Adobe Employee
    October 21, 2011
    I've been able to repro this, and have logged a bug. The problem exists with publish collections that were created in LR 3.3 or earlier. The only workarounds I've found for you to use in the interim is to either recreate the collection in LR 3.5 or (as Darren suggests in the case of a smart published folder), export the collection settings and re-import.
    F
    FeedbackCommunityMember
    Inspiring
    October 19, 2011
    I'm having the same issue.

    This seems to exist for smart collections that were created prior to upgrading to 3.5. The work-around seems to be to export the collection settings then import them again.
    Jason Abbott
    Jason AbbottAuthor
    Known Participant
    September 1, 2011
    A couple more observations:
    - Of the dozen or so images needing updated, the first ends up in a "tmp" folder within the export location before the process errors out.
    - To test for a security issue, I gave the "Everyone" user full control in my export folder. It didn't help. Along the same lines, I also temporarily removed the existing versions of the modified files to export. Again, didn't help.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices