Help get this topic noticed by sharing it on Twitter, Facebook, or email.
I’m frustrated

Lightroom 3.6: Export error "An internal error has occurred: Win32 API error 2 ("The system cannot find the file specified."> when calling ShellExecuteExW from AgWorkspace.shellExecute"

Getting an export to .jpg and/or .dng after upgrading to LR 3.6. Reinstall LR last evening, all worked well for a few hours and now getting the same error.

"An internal error has occurred: Win32 API error 2 ("The system cannot find the file specified."> when calling ShellExecuteExW from AgWorkspace.shellExecute

after selecting "OK" to clear the error the file does export strangly.

System Info:
Lightroom version: 3.6 [795620]

Operating system: Windows 7 Business Edition

Version: 6.1 [7601]

Application architecture: x86

System architecture: x86

Physical processor count: 2

Processor speed: 2.1 GHz

Built-in memory: 3581.9 MB

Real memory available to Lightroom: 716.8 MB

Real memory used by Lightroom: 214.4 MB (29.9%)

Virtual memory used by Lightroom: 198.9 MB

Memory cache size: 61.2 MB

System DPI setting: 96 DPI

Desktop composition enabled: No

Displays: 1) 1280x800

Serial Number: 116040022787739424107632

Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 3.6

Library Path: D:\D630 PIXs\LR D630 PIX\LR D630 PIX.lrcat

Settings Folder: C:\Users\BStock\AppData\Roaming\Adobe\Lightroom
17 people have
this problem
+1
Reply
  • I received the same error when exporting an image. I'm running Windows 7 64-bit, Lightroom 3.6. Even though the error occurred, the image still exported.

    1. In the Exports screen, I removed the export setting I was using.
    2. Adding it back using a slightly different name (may be you can use the same name, I didn't test scenario).
    3. Error message no longer displays. Image exports successfully.

    I'm guessing the problem is the export file get corrupted for whatever reason and causes this error message.

    Good luck. Hope this helps.
    Ted
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Do you have a post processing action set up in the export dialog? The only place I can think of off hand where we'd use shell execute during export is in post processing or maybe some plugin/filter.

    That would also explain why the export produced a file as expected and the error seemed to have no negative effects.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • In my situation, I do have a simple post processing action I run after export. After the images (JPEG) are created from the Lightroom, I open them for viewing in ACDSeePro3.exe, which is a photo manager application. I use this to add metadata (caption text and keywords) to the image using tokens, something Lightroom currently doesn't support.

    Troubleshooting this issue, I discovered after the error occurred, if I exported the same image in Lightroom using a different Export preset, the error message did not display and everything worked as expected.

    By way of details, the error occurred after an incident on my computer. I was editing an image in Photoshop CS4 after launching it from Lightroom 3. When I tried to save it, Photoshop said, can't do that, file open. I looked everywhere and couldn't find the file open. I couldn't understand why Photoshop was saying this. Then I discovered CrashPlan, my offsite backup application, had the file open as it was processing it in the background. I was on a deadline for a job and I forced something (I can't remember the details what exactly I did) to make Photoshop save the edited image so I could finish processing it in Lightroom.

    It was after this interaction that the Lightroom 3 export error appeared. The image would export, but of course because of the error message, the post-processing action was not being triggered.

    Later, I uninstalled and reinstalled Lightroom 3 as the first troubleshooting step, and this didn't contribute to the resolution. I knew Lightroom was upset about something that had gone awry... but it apparently wasn't an issue within the kernel of the program.

    After giving it some thought, I recreate the Export Preset under a different filename (not sure that part mattered), and the error message no longer displayed and my export action was again working.

    I didn't spend the time to determine root cause, I just was happy to get the software to restore to normal operation again.

    Hope this helps.
    Ted
    • Interesting... I would have expected this error to indicate the target program to be executed could no longer be found at the original location.

      I was able to reproduce the same dialog by setting the post processing action to open with a particular executable and then renaming the executable so that the action points to a non-existent path for the program.

      Is there any chance that you've installed a new version of ACDSeePro that might have slightly changed the path to where its executable resides?

      If you have the old and new export presets, I could probably confirm by comparing them, but in any case I'm glad you got it sorted out. I may file a bug internally to make that error message more clear.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • In my case, no I hadn't recently installed a new version of ACDSeePro. Been use V3 for 2-3 years now. The only thing that "changed" between when LR was working and when the error message appeared was the situation where CrashPlan was backing up the file I was editing between PS and LR.

    Oh, there may have been another issue. I remember vaguely that I was trying to rename the image in Lightroom using the right panel to a more intuitive filename, and maybe I was trying to save the open image from PS to the previous filename.

    What I'm trying to say is between Lightroom trying to import the image that was just updated from PS and me trying to rename the image while in Lightroom... and also the fact I remember doing something unwise like trying to rename the image filename in LR while it was simultaneously open in PS. May be these elements played a factor in the error.

    I will say that while using LR2, I had this same error message occur once. I escalated to Adobe support. I never got it resolved. After upgrading to LR3, it went away.

    Sorry I don't have really "good data" in this reply help troubleshoot. I just needed to get my client job done and move on to the next one, so I'm afraid I'm a little sketchy on the details that could lead you to a solution... hopefully this info can play a role in help you put together the pieces in some way.

    I think it is wise to file a bug as this is not an intuitive error message... and doesn't help the User much in trying to resolve the issue. I was lucky.

    Thanks! Ted
    • As far as I know, the only path ShellExecuteExW would respond to with this error message is the path to the executable itself (it has no way of knowing how to properly interpret the rest of the arguments passed, so it won't check for their existence or attempt to even parse to see if the are paths) being invoked.

      I'm baffled. I'll just have to mull this one over a bit more and see if something comes to me.

      Thanks again for all the details you've provided!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I've also started seeing this error on exporting images - although it exports them anyway ok. It still is worrying.

    An internal error occurred: Win32 API32 error 2 ("The system cannot find the file specified.
    ") when calling ShellExecutreEXW from AgWorkspace.shellExecute

    Then a second warning saying the same thing and it was unable to export.

    Any more ideas please..?

    John
    • I've used code inspection and native breakpoints and the only way I can find to get shell execute to be invoked during an export is by having plugins involved or post processing actions set.

      If those do not seem to be in your export, I'd say that the best bet for diagnosing this is to either post a screenshot of the complete contents of the export dialog or the contents of an export preset created with the exact settings you're using. There may be a way of generating this error that I overlooked.

      DT
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • on another forum they suggested trashing preferences which I did. That worked.
    thanks.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I tried that too.... to no avail. It's a really terrible thing to get rid of. Tried repairing Lightroom (3.6), tried changing preferences, and so on.
    Is there really no simple method to get rid of this ugly bug?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Jeffrey Tranberry (Chief Customer Advocate) April 01, 2012 13:09
    Beat Gossweiler came up with this as a solution:

    Check the Post-Processing section of your Export dialog:
    In the dropdown of "After Export:", make sure you have a valid entry selected (choose "Do nothing" if you don't have special requirements).



    I've heard of several users where this dropdown was blank (which is NOT a valid choice) after upgrading to LR4, leading to the error you describe.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I’m frustrated
    Get the following error message when I try to Export to file a file on Desktop.
    An internal error has occurred: Win32 API error2 ("The system cannot find the file specified.") when calling ShellExecuteExW fromAgWorkspace.shellExecute.
    Window 7 64bit

    This reply was created from a merged topic originally titled
    Lightroom: Export Error to a file on desktop.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • In LightRoom 4, when exporting photos to my desktop or a subfolder I receive an Error message "Unable to Export: An internal error has occurred:Win32 API error 2 ("The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute
    It does export the file however and is on my drive as instructed on output.
    This never happened with Lightroom 3.5. I don't like seeing error messages and hope this can be resolved.
    I am running Windows 7 64bit AMD quad core, 8 gb RAM.
    Thanks

    This reply was created from a merged topic originally titled
    Error message upon exporting files in LR 4.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Lost ability to export images. Error message: Unable to export. Internal error- Win32API error 2 ("The system cannot find file specified when calling ShellExecuteExW from AgWorkspace.shellExecute)

    This reply was created from a merged topic originally titled
    Lightroom: Lost ability to export images..
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I’m frustrated
    Mine STILL does this when my choice is 'open folder after export'. And after using ONONE plug ins.
    win 7/64 bit
    dual quad
    12 gb RAM
    Onone Perfect Photo 6.1 Suite
    exporting to file on desktop doesnt matter if tiff/jpeg/psd - sometimes it exports, sometimes it doesnt. Same error.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I use the Lr 4.0 build 814577 x64 with Simp-Chinese Win7 x64(SP1).When I export the raw file to JPEG file(s) by Lr 4,there will be dialoge "Unable to Export:An internal error occured:Win32 API error 2 when calling ShellExecuteExW from AgWorkspace.shellExcecute"
    But in fact,most time it can export the files successfully.What's meaning of it?How Can fix it?Thanks

    This reply was created from a merged topic originally titled
    Unable to export by Lr 4.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Just downloaded and installed LR 4.1 as an upgrade to 4.0 today. Made a couple of adjustments to an image and went to File->Export (to the hard drive).

    Configured the export for a jpg to the desktop and got the following error:

    Unable to Export:

    An internal error has occurred: Win32 API error 2
    ("The system cannot find the file specified.")
    when calling ShellExecuteExW from AgWorkspace.shellExecute

    The export actually DID succeed and it looks fine. But it's disturbing to receive this error. I'm on an x64 Windows system and installed the x64 version of LR. Is this an x32 error? If so, why am I getting it?

    Thanks! Steve

    This reply was created from a merged topic originally titled
    Unable to Export error message in Lightroom 4.1.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • The "solution" is at the top in the "Official response" post. Worked for me.

    In the Export dialogue upon exporting files, check that the option for "after export" is not left blank. Select "do nothing" or whatever you like, but don't leave it blank.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I’m frustrated
    Hi,

    Using Lightroom 4.1, whne exporting pictures (to a dir on a USB drive), all the pictures get exported but I get an error telling that LR cannot export the picture as it can't find it... This problem happens for every export (as if some hidden / invisible file was in the export list and LR can't get rid of it)

    This reply was created from a merged topic originally titled
    Export photo OK but gives file not found error.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I've just installed Lightroom 4. For a few weeks it worked fine then it started giving me this message when I try to export. It does not matter what format I'm exporting in, the message is always the same: " UNABLE TO EXPORT. AN INTERNAL ERROR HAS OCCURED. WIN 32 API ERROR ("THE SYSTEM CANNOT FIND THE FILE SPECIFIED") WHEN CALLING THE SHELL EXECUTE EX W FROM AGWORKSPACE.SHELL EXECUTE.

    This reply was created from a merged topic originally titled
    Lightroom 4: unable to export Win32 API error cannot find file specified.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I’m frustrated
    1
    I am using LR4. After I export, I get an error message. I have a picture of the error message and I'm going to attach it to this report. I have already checked to see if I'm all up to date on my updates and yes I am. I can't seem to find anyone else having this issue. It just started about 2 weeks ago. Please help!

    This reply was created from a merged topic originally titled
    Error message after exporting from LR4.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • From the error and where it is happening in your workflow, I'd guess you have an Post Processing action that is ill-defined.

    Look at the end of the Export panel and open up the Post Processing section and check what it's trying to do. You can set it to Do Nothing just to make sure it's not trying to do anything. I usually have mine set to Show in Explorer because I usually want to do something with the files outside of LR after the export.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I think the root of this problem is that LR presents a drop-down list with a default selection that will automatically result in an error if it is not changed. This means that the user must change that selection in order to avoid the error.

    Bad programming practice that should have been dealt with before the product was released...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I've never seen this error under discussion, but I've usually upgraded LR from a previous version, so if the factory-default, new machine install of LR4 isn't Do Nothing then that is a problem. Less of a "programming" problem and more of whomever created the deployment package that didn't set the default as Do Nothing didn't do the right thing.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I have mine set to "Do Nothing" as I always have... and I didn't upgrade from any previous version. I've only used LR4. So changing it to "do nothing" is not the problem when I already have it set at that for after export.

    Any other ideas?
    • Have you tried the other PP options, e.g. Open in Explorer, to see if any others work?

      I don't have any inside knowledge of when the error message may be shown but in addition to not finding the post-processing program, perhaps there is something wrong with the path to the exported images, such as being close to the limit for length of file paths. This would be a good thing to check if you also have the option turned on to re-import into the LR catalog, because it'll need to find the files, again, to import them.

      Do you have any third-party plug-ins installed where maybe one of those has gone haywire. Check to make sure you are exporting to your hard drive and not some other destination, and make sure you either don't have any empty card readers plugged into your computer or that there is a card inserted. I've seen programs do weird things if a card read is plugged into a computer USB slot but there is no card.

      Another possibility when weird things start to happen is that the preferences file may be corrupted and it should be deleted and let LR recreate it.

      On my 32-bit Windows 7 computer, the LR preferences file is in the following location:
      C:\Users\YourUserName\AppData\Roaming\Adobe\Lightroom\Preferences

      The AppData folder is usually hidden so you'll need to type it into your Windows Explorer address bar and hit enter after clicking down into your username folder, and then you can continue clicking into into the Roaming folder and beyond.

      There will be preferences files for each version of LR you have had installed, which you indicate is only Lightroom 4 Preferences.agprefs

      If you feel uncomfortable deleting it, then move it to another location above the Preferences folder so LR cannot find it. You should exit LR before you try doing anything to the Preferences file.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I’m irritated
    Lightroom 4.2 and 4.3RC, running under Windows 8 (64 bit), report an error when exporting jpegs to hard disc (Win32 API 2 error, file not found, shell execute error). The export works correctly despite this error message. This error did not occur using Version 4.2 under Windows 7 on the same PC.

    This reply was created from a merged topic originally titled
    Lightroom file export error message since upgrade to Windows 8.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I’m frustrated
    Ever since the last update to Lightroom 4.3 the same error message appears whenever I export an image. The export goes through but the message says the system cannot find the file. This happens during every export. I've included a screenshot of the message. I'm using Windows 7.



    This reply was created from a merged topic originally titled
    Lightroom error message since latest update to 4.3.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • 1
    As it says further up in this thread your message was merged into, set your Post Processing action at the very bottom of the Export Panel to None.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I’m happy
    It was interesting and a bit comforting to discover that so many others had the same issue.
    I set the after export panel to none. It somehow got set to blank when I updated to the latest version. Now there's no more annoying message. So glad it was an easy fix. Thanks to all!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Just so you know... this is another Lightroom 4.3 bug!!!!!!!!!!!!!!!!!!

    I didn't upgrade from an previous version so this bug comes with the standard install. This is very buggy software!!!!!!!!!!!!

    I'm a long time user of Adobe products and this one takes the cake for having crazy frustrating bugs pop up. I've had troubles with importing photos, catalogs missing photos and then not letting me re-add them to the catalog without renaming the original file folder, errors trying to export like this one listed above.

    PLEASE QA the software before releasing it to us for sale!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • 1
    After I did what they said up above I don't have this problem any more.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • It did work, but my issues is this bug comes with the default install of Lightroom 4.3 I've had several other bugs and I'm totally frustrated having to google errors on software that is supposed to be GA.

    In other areas I've had a lot more issues - importing photos - total disaster. In one case, Lightroom started "greying" out new photos as if they were already in the database, BUT they were brand new. I had to create a new catalog and import everything from my previous catalog to reset this condition. Once a catalog gets messed up there is no way to recover it,etc.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • @RennSminkey - It sounds like you could benefit from a little training. Check out some of Matt Kloskowski's tutorials at the Photoshopuser.com. He's an expert and his work can definitely get you over this difficult spot in your learning curve and will certainly reduce your frustration. Once you learn the UI for Lightroom I think you'll love it.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I’m frustrated with the catalog features - photo processing is good.
    I don't need training! There are bugs in Lightroom that Adobe has not addressed properly. The bugs I'm talking about are not bugs with how exposure is calculated or tint,etc. The photo processing features work quite well. These errors are all database issues and install issues where default settings are not set correctly right from the install.

    Lightroom has database issues! Maybe most of your users don't experience them because they have 10K of photos in their database. I have over 30K in each one of my catalogs and I've had problems with them on/off. It's extremely frustrating when you build a large catalog and then it starts to act up a month later.

    Adobe should support their users by doing extra QA and testing on large databases. If anyone has any doubts about the integrity of the lightroom database - just google it - there are so many users complaining of issues with the database it's impossible to read through all of them. I've experienced most of the common issues with importing and exporting. At times Lightroom flags new photos as if they were already in the catalog- not sure what triggered it to happen, but it did happen. I had to rename the files to get them into the catalog correctly. That didn't start happening until I broke 35K photos in the catalog.

    Please look into issues with the database as they are reported at don't ask your users to get more education - it's very insulting.
    • I don't work for Adobe, so it's not they who are suggesting you get more education.

      And please don't be insulted by my recommendation that you consult with an expert on LR - such as Matt. I'm guessing that the size of his catalogs dwarf your, so he can probably give you some good ideas.

      I know (from experience) that it sometimes makes one feel good just to vent or maybe flame a little bit. But really, you can be proactive in trying to solve your problems.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • My LR catalog database has 46,859 photos and I don't have any problems.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • My database is incredibly complicated with 53,094 Files, 44,081 Folders. For a long time I had a problem with the back up and optimize feature taking hours to complete. There were a lot of old files that were empty and after I deleted them there was improvement but backing up the catalog is still very slow.

    I find that it is necessary to synchronize folders frequently because I prefer to use a different program to import and organize my photo files and folders. Also, when a photo is created in Photoshop it doesn't show up in Lightroom until you synchronize the folder you put it in.

    Frankly, I've never like the export feature. It was a huge learning curve and for what? Besides being able to add a watermark, it's not better than the old style "save as" "choose folder" system, but I have learned to adapt to it out of necessity. I always have "add to library" checked off when exporting in LR. Even still, I sometimes have problems.

    For the developers: It would really help my workflow if it was possible to export as a jpg and tiff at the same time with my own saved settings.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • If you really only have one file per folder and work on one file at a time then maybe LR isn't the tool for you.

    Why aren't you using Bridge and Camera-Raw? Is there something better about LR than Bridge/ACR; maybe upgrading LR is cheaper?

    A “normal” use case of LR is that a photographer offloads the results of a photo shoot which may contain dozens or hundreds or thousands of photos and these all go into one or at most a handful of folders, and when the photographer Exports they are doing a batch of possibly dozens if not 100s of photos at a time. It would be very time-consuming to do File / Save As individually for dozens or hundreds of chosen photos for each photo shoot.

    As far as backing up your LR catalog taking hours, how big is it? Mine is 645MB with 46.5K photos, mostly raw, and while it does take a few minutes to backup and optimize, including the previews database, the catalog is on a USB drive so it won't be as quick as an internal drive.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • For some reason, In the "export" dialog, my "what to do after export" was set to open with Illustrator, I changed it and the problem was solved, this is how the error alert looked like
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • This error occurs when post-processing action no longer exists (and hence menu is blank) - problem still happening in Lr5.3.



    This really should be fixed! (e.g. Lr5.4).
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I received this error today with LR 5.4 using the LR Presets. The files still exported with no problem. The error stopped when I changed the Export setting to Export Full-Sized JPEGs to the Hard Drive
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • This reply was created from a merged topic originally titled
    Lightroom 4.4 Toggle the After Export setting to fix - Win32 API error.


    When exporting to HD I get the following Warning after updating to the 4.4 release...
    [Window Title]
    Warning

    [Main Instruction]
    Unable to Export:

    [Content]
    An internal error has occurred: Win32 API error 2 ("The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute

    [OK]

    If I go and look in the directory the file is there so it did work but the warning continues to pop up with each export to HD. No warning pops when exporting via email and sending as an attachment.

    QUICK FIX: My after export was set to open explorer... if I set it to do nothing the error goes away, and after I set it back to open explorer it now works as expected. After reading the other entry on the same warning where the export was set to nothing I thought if I toggled the entry it may put it back in a good state. And it did so if other see this the same may fix their issue as well.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly sad, anxious, confused, frustrated