Mark Ferguson
New Member
- Joined
- Feb 20, 2017
- Messages
- 1
- Lightroom Experience
- Advanced
- Lightroom Version
Hello,
I know this has been "solved" countless times here but the problem keeps reoccurring for me and it's driving me crazy. I've deleted the "Lightroom Catalog Previews.lrdata" file and restart and everything works fine....for a few days or a week. Then the error comes back with a vengeance.
My set up is:
Windows 10
8GB RAM
Two interanl HD's
Catalog and Preview cache in same folder
The one thing that might be different than the typical user is that I store my LR folder on the local instance of Google Drive. When you have the Google Drive app installed it keeps a local folder on your PC in sync with your Google Drive folder in the cloud. My photography folder is on this folder on my PC that is kept in sync with the cloud version of it. This is my "disaster recovery" solution in case my HD fails.
My lingering doubt is that there is a conflict between the Google Drive app and Lightroom and they are both trying to put a "lock" on a folder or file causing the error. No evidence to support this, just grasping at straws.
Thanks!
I know this has been "solved" countless times here but the problem keeps reoccurring for me and it's driving me crazy. I've deleted the "Lightroom Catalog Previews.lrdata" file and restart and everything works fine....for a few days or a week. Then the error comes back with a vengeance.
My set up is:
Windows 10
8GB RAM
Two interanl HD's
Catalog and Preview cache in same folder
The one thing that might be different than the typical user is that I store my LR folder on the local instance of Google Drive. When you have the Google Drive app installed it keeps a local folder on your PC in sync with your Google Drive folder in the cloud. My photography folder is on this folder on my PC that is kept in sync with the cloud version of it. This is my "disaster recovery" solution in case my HD fails.
My lingering doubt is that there is a conflict between the Google Drive app and Lightroom and they are both trying to put a "lock" on a folder or file causing the error. No evidence to support this, just grasping at straws.
Thanks!