Copier le lien dans le Presse-papiers
Copié
I import my files from my camera's always to the same location. Then I edit them and when they are ready I move them fron that location to a location that suited for them. So al bird files go to the bird file location.
About 50% of the time it goes alright but in the other 50% of the time lightroom moves the files to the right location on the harddisk but tells that it was not possible and according Lightroom the files weren't moved at all but gives a location error.
I know how to correct it but it is annoying as hell and takes alot of time to correct it. Am I the only one who has this problem or an more people have this?
I never see that Adobe mentioned this problem let alone they solved it.
I have an other question. Is there a way in Lightroom to check the health of the libary so you can files other misplaced or mismoved files.
Hope that somebody can give me a satisfying answer to solve this. Regards Han
Copier le lien dans le Presse-papiers
Copié
Are you using Windows 10 or 11? Where are the files starting and where are you moving them to? External disk, server, internal drive, etc? Can you post a screenshot of the errors? Have you tried turing off your security software to see if that is the cause?
Copier le lien dans le Presse-papiers
Copié
Better solution ... avoid the problem entirely. Don't import to one location and then move them to a 2nd location. Import the photos to the final location directly. Then you don't have the move step, and so it can't go wrong.
Copier le lien dans le Presse-papiers
Copié
I import my files from my camera's always to the same location. Then I edit them and when they are ready I move them fron that location to a location that suited for them. So al bird files go to the bird file location.
About 50% of the time it goes alright but in the other 50% of the time lightroom moves the files to the right location on the harddisk but tells that it was not possible and according Lightroom the files weren't moved at all but gives a location error.
I know how to correct it but it is annoying as hell and takes alot of time to correct it. Am I the only one who has this problem or an more people have this?
I never see that Adobe mentioned this problem let alone they solved it.
I have an other question. Is there a way in Lightroom to check the health of the libary so you can files other misplaced or mismoved files.
Hope that somebody can give me a satisfying answer to solve this. Regards Han
Copier le lien dans le Presse-papiers
Copié
Please do the command Help > System Info and copy/paste the first ten lines here. That will make subsequent advice more likely to be helpful.
Copier le lien dans le Presse-papiers
Copié
Lightroom Classic version: 11.4.1 [ 202206241800-b406ce4c ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.19044
Application architecture: x64
System architecture: x64
Logical processor count: 16
Processor speed: 4,2GHz
SqLite Version: 3.36.0
Copier le lien dans le Presse-papiers
Copié
Please don't double post the same issue. MODERATOR can you merge this with https://community.adobe.com/t5/lightroom-classic-discussions/massive-errors-in-lightroom-classic-v11...
@positive_yogi98A4Please consider my answer in your other thread.
Copier le lien dans le Presse-papiers
Copié
I came here for the same issue; encountered with a Synology NAS connected folder. However, I noticed that I have the same error message when moving the file in the Windows explorer between some of the folders, but not with others. In my case, it seems to be a Windows or NAS issue rather than a Lightroom issue.
@dj_paige your suggestion does not help; my flow is to import all, tag with Lightroom, then move according to tags
Copier le lien dans le Presse-papiers
Copié
Just so I can understand, why is there a need to move according to tags? Why not just tag only, without moving? (and then use the Lightroom Classic tools to find photos with specific tags)
Copier le lien dans le Presse-papiers
Copié
I know this is an old topic, but I also saw a lot of errors when I was moving files or folders within Lightroom. And I came a bit close to a workaround. I use the same workflow as original poster: Import files from my cameras (Nikon DSLRs and iPhones) to a temporary import location - so some initial editing - then move them to the location in my library that suits them. When moving multiple files or folders with multiple files, I would then get frequent errors that Lightroom failed to move some files. It would move some of them, but leave some files in the original location leaving a lot of manual cleanup.
I then noticed a pattern where this would happen more frequently with some filetypes, namely Raw files from my Nikons (NEF) and HEIC files from my iPhone - less frequently wig DNG and JPG files. I also notíced that Lightroom works slower on NEF and HEIC.
What appears to be the underlying issue is that the file move fails if Lighthroom is also doing other file operations on the same image file while trying to move it (reading the file to build an image preview, writing metadata, etc.). This seems plausible. I'm using Lightroom on Windows, and Windows has always been poor at handling parallel file operations. Since the other file operations take longer on Raw and HEIC, the issue happens more often with these files.
So I tried to build 1:1 previews for all the images right after importing from the camera and before moving to the target locations in my library. This seemed to solve the issue. I'm no longer experiencing frequent issues with errors during move. Again, this makes sense since Lightroom will perform fewer other file operations on the image when there is a 1:1 preview to work on.
Of course it takes some time and disk space to build 1:1 previews for all files. But I can just have the build run in the background or while I'm not at the computer. It doesn't disrupt my workflow while I'm actually editing and sorting images. And the 1:1 previews can be set for automatic discard after 7 or 30 days leaving me enough time for editing and sorting without having to worry about piling up too many previews.
I have not looked at the second part of the original question - the one about checking the library for misplaced or missing files.
Peter