Lightroom cache files permanently written to alternate drive

I've encountered an unusual problem using LR version 1.4.1 under Windows XP. Whenever I preview a RAW file in LR, a cache file is being written to an alternate drive, named Cache0000000001.dat, with each additional preview increasing the last digit in the file name by 1, Cache0000000002.dat, etc., and an Index.dat file. Each cache file is 2532kb or 8607kb depending on the size of the original RAW file. After closing Lightroom, these files remain on the disk and have to be manually deleted.
This has only begun to happen in the past couple of days. I therefore assume it's due to some change I've made recently. The change began after I removed Photoshop CS2 after having both CS2 and CS3 installed for several weeks. I don't know how the particular disk for writing these cache files is being selected other than the fact that my CS3 scratch disk is the same disk. The Lightroom files are on a separate disk.
This is not a major problem except that the cache files add up very quickly, taking up a lot of disk space and must be deleted manually after closing LR.
There is probably no simple explanation for this anomaly but if anyone has any ideas, I certainly would appreciate the input.

Ian,
Thanks for the reply. Yes, you are correct. The preferences in Camera Raw determine where these cache files go and does limit the size of the total cache. The default is 10 GB which suits me fine. Where these files have been going in the past is a mystery to me.
It does seem surprising to me that the location for the Lightroom cache is
determined in Photoshop Camera Raw but so be it.
Again, thanks for solving this problem for me.
george

Similar Messages

Bridge cache files for different bridge versions

Bridge with CS2 and now CS3 is a superb image browsing tool - particularly when the cache files are within the directory containing the images. It would be very very useful if new versions of bridge could read older version cache files.
If a user creates cache files in a disk directory and then backs up the directory to a DVD for archival purposes, it would be very valuable to allow the "current version" of bridge to properly read the "old version" DVD archived bridge files. This would add greatly to the browsing speed of the DVD archive - since a new cache file will not be needed (or desired).
In addition, if previous versions of the cache files are on a hard drive, the ability to process the old version files would allow bridge to work more rapidly when browsing images. Of course, there are problems if the user attempts to update information that is version specific, however I am sure there are sane solutions to the problem.
tony

Not having to use a centralised cache was one of Bridge 1.0's strengths.
Not sure about the current versions insistence on centralising with the option of distributed as well or why the cache type as changed. A pain from an archival point of view as I used distibuted cache, which is now a waste of bytes.

How can I get rid of cache files?

Premiere Pro, can't find cache files on Mac, not in the common folder, clean doesn't work, I know there are Gigs of them on my drive. How can I get rid of them?
I started a premiere project I had worked on before using an external drive but forgot to hook up the external drive. In a few minutes, Premiere loaded 5 gigs of cache files onto my macbook pro drive OSX 10.8.6. I tried the following to free up the space:
Tried to "clean" the cache folder before switch it to the external drive - this only removed a small amount of the 5 gigs created
Tried to find files in the Application Support/Adobe/common folder - no cache files found
Tried searching the web for answers - no new info
Tried searching my drive for the files - can't find them
Tried restarting the MacBook and Premiere with and without the external drive - no luck
Now what?
Message was edited by: Kevin Monahan
Reason: please make a shorter and more concise title next time. Thanks.

First off, exactly which version of Premiere are you running? Not simply PPro CC or CC2014 but the version number shown in the About box.
I'm not clear whether you're saying that Premiere can't find the cache files or that you can't find them.
I gather that you're referring to the Clean button on the Media tab of the Preferences dialog, which is also where you set the path for the cache files.
Are you sure you're looking in the correct Library--not the one that's readily accessible under Macintosh HD but the one that Apple, in it's infinite wisdom, hides from users. To access it, open the Go menu and press Option.

Lightroom 5.3 Media Cache Files

Hello,
I want to save in Lightroom 5.3, the Media Cache files in a different directory. I have Lightroom and PS CS6 installed on a 60 GB SSD and the media cache files quickly take 10 or more gigabytes.
In the registry as DatabasePath and FolderPath is set:
[HKEY_CURRENT_USER \ Software \ Adobe \ Common LR5 \ Media Cache]
"DatabasePath" = "C: \ Users \ Username \ AppData \ Local \ Adobe \ Lightroom \ cache \ Video \"
"FolderPath" = "C: \ Users \ username \ AppData \ Local \ Adobe \ Lightroom \ cache \ Video \"
If I change the path in the registry is Lightroom the path when playing the first video unfortunately always come back.
How can I change the path permanently.

Leider kann man in den Voreinstellungen nur die Video Cache Größe bestimmen aber nicht den Speicherort. Somit könnte ich die Video Cashegröße auf 1 GB "minimieren" und habe für Videos immer lange Wartezeiten wenn ich sie abspielen / bearbeiten will. Das hilft mir also leider nicht weiter.
Den Speicherort kann ich in den Voreinstellungen leider nur für die Cache Dateien von Bildern freiwählen und das funktioniert auch prima.
Im übrigen habe ich die Einstellungen für die Media Cache Dateien für PS CS6 auch in der Registry geändert und das Auto fährt noch prima und ohne Probleme.

Is anything written permanently to the Fusion Drive's SSD?

Is anything written permanently to the Fusion Drive's SSD or is it just a very large cache for the HD component?
I'm wondering, because I'd like to know, mostly out of curiosity, if the mechanical portion of the Fusion Drive were to fail, might the computer still boot from information on the SSD?

(I back it up with Carbon Copy Cloner AND Time Machine.)
So, if either part fails, the machine is quite dead until the internal drive is replaced? I ask because these two drives are detected separately in utilities such as TechTools Pro, where their S.M.A.R.T. data can be retrieved and tested independently.
If a failure of either portion of the drive totally disables the whole drive, would this sort of double the chance of a Fusion drive's failure?

Why is this massive media cache file on my C drive?

Running Adobe CS5 (NOT 6) on a Windows 7 PC.
I thought I had made sure that everything was on my D or E drives since my C drive is an SSD and I don't want anything but the basics on it.
Well, I have nearly 4GB of Media Cache eating up SSD space and no way to know if I can delete it, how to delete it, how to move that directory, etc.
Whenever I start a project I have my source files on my E drive and I list my D drive as my scratch drive.
Here is a screenshot showing the exact location of this huge Media Cashe folder.
Gents, I'd greatly appreciate some assistance. My SSD is being eaten alive.
Can this stuff be deleted? If so, how? What exactly IS that stuff and why is it on the C drive?

Hi msp1518,
Thanks for the posting adobe forums,
These are the files for conforming audio, generating peak files for audio.
Yes, you can delete these files once you have completed the project in premiere pro.
Just, close the premiere pro : Just delete the files inside the Media cache files and Media Cache folder.
Regards,
Sandeep

ESE - Event Log Warning: 906 - A significant portion of the database buffer cache has been written out to the system paging file...

Hello -
We have 3 x EX2010 SP3 RU5 nodes in a cross-site DAG.
Multi-role servers with 18 GB RAM [increased from 16 GB in an attempt to clear this warning without success].
We run nightly backups on both nodes at the Primary Site.
Node 1 backup covers all mailbox databases [active & passive].
Node 2 backup covers the Public Folders database.
The backups for each database are timed so they do not overlap.
During each backup we get several of these event log warnings:
Log Name:      Application
Source:        ESE
Date:          23/04/2014 00:47:22
Event ID:      906
Task Category: Performance
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      EX1.xxx.com
Description:
Information Store (5012) A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe performance degradation.
See help link for complete details of possible causes.
Resident cache has fallen by 42523 buffers (or 27%) in the last 903 seconds.
Current Total Percent Resident: 26% (110122 of 421303 buffers)
We've rescheduled the backups and the warning message occurences just move with the backup schedules.
We're not aware of perceived end-user performance degradation, overnight backups in this time zone coincide with the business day for mailbox users in SEA.
I raised a call with the Microsoft Enterprise Support folks, they had a look at BPA output and from their diagnostics tool. We have enough RAM and no major issues detected.
They suggested McAfee AV could be the root of our problems, but we have v8.8 with EX2010 exceptions configured.
Backup software is Asigra V12.2 with latest hotfixes.
We're trying to clear up these warnings as they're throwing SCOM alerts and making a mess of availability reporting.
Any suggestions please?
Thanks in advance

Having said all that, a colleague has suggested we just limit the amount of RAM available for the EX2010 DB cache
Then it won't have to start releasing RAM when the backup runs, and won't throw SCOM alerts
This attribute should do it...
msExchESEParamCacheSizeMax
http://technet.microsoft.com/en-us/library/ee832793.aspx
Give me a shout if this is a bad idea
Thanks

Alternate drives in Jar file Class-Path attribute

Hello, all. I am working on a project that I would like to package into a single jar file for simple execution. At my place of work classes from EJB are stored on a different drive from where I am doing the development. I am having trouble accessing those classes from the Jars I am creating. When I try the following manifest:
Main-Class: MyPackage.MyClass
Class-Path: U:\someFolder
the application will not start, saying that MyPackage.MyClass cannot be found. This is despite MyPackage.MyClass being properly packaged into the Jar file, as verified by a jar t operation. When I leave off the drive letter in the Class-Path attribute:
Main-Class: MyPackage.MyClass
Class-Path: someFolder
the application starts and executes properly right up until a class from someFolder is needed, at which point exceptions begin to be thrown.
Any ideas will be much appreciated!
John Todd

I was eventually able to find the answer to my own question: Jars do not accept absolute paths at all, only relative paths. Thus, the alternate drive approach will not work. Fortunately I was able to find an alternate solution.
John Todd

Lightroom loses files on a Network Attached Storage (NAS) drive

I am using Lightroom 5.7 on a PC in Windows 7 64-bit.
A couple of weeks ago I installed a Network Attached Storage (NAS) system as I was running out of internal hard disk space. I set up a logical drive on the NAS for Photos. In Lightroom, I dragged the photo files over onto the new drive. The catalogue and backup files remained on the internal hard drive.
My photos are arranged chronologically, in directories (years) and subdirectories (days, named using the format "2014_12_31").
Since moving the files to the NAS, Lightroom has been giving me error messages when in the Develop module that it cannot find files. The previews view fine in the Library module, and the files are still there when I look for them in Windows Explorer. The errors do not occur within entire directories (years) subdirectories (days) - only some files within individual subdirectories are affected. And, only files from 2015 seem to have the problem. And, when I drag the directories back to my internal hard drive (again, within Lightroom), the errors disappear and everything works fine.

Yes, right clicking on the problem folders and showing in explorer does show the connection is to the correct folder location.
A couple more points that may be worth mentioning:
When I was having this problem earlier this week, the missing photos seemed to be spread randomly within different folders and subfolders (folders are year, with subfolders for each day I have photos). I followed the advice in the document you referenced yesterday, and went back through each main folder (there are about a dozen of them, one for each year plus a few miscellaneous folders) and used the "update folder location" function. This worked well I thought - except I realized later on that one year (2014) still had the photos missing - but this time, it seems to be all photos within that year folder, not just a few random ones. There is no "?" on the folder, or "!" on the individual photos, they show fine in preview, but clicking on the develop module every photo has the message "cannot find file". When I right click on the folder, or individual files to follow the location of the file in explorer, the location is correct - and as far as I can tell the locations and structure is consistent with the folders for all the other years which Lightroom has no problem finding. That is, I can see nothing "unusual" about the folder for 2014 in the way it sits within my filing structure.
And here's the kicker - last night I made a copy of the entire 2014 folder that was on the NAS external drive (where Lightroom can't seem to locate the files) back on to my internal drive (this took a couple of hours). This morning, I forced Lightroom to lose the link to the folder on the network drive by simply changing the name of the folder from within windows explorer, and then the "?" and "!" warnings popped up in Lightroom indicating it could not find the folder and files. I then used "update folder location" to point Lightroom at the copies that were now on the internal drive, and the problem disappeared (all files were located).
Finally, I then broke the link to the folder on the internal drive by changing the name of the folder on the internal drive from within explorer, renamed the folder on the NAS drive back to "2014", then opened up Lightroom again (and of course it indicated the files were missing) and used the update feature again to point Lightroom back to the folder on the NAS. And, again, the missing files errors pop up for every photo within that folder - but no "?" or "!" warnings are shown (recall these are an exact copy of the files that it had no trouble finding on the internal drive).
I tried playing various games with Lightroom last night, forcing it to break linkages by renaming folders, etc, and every time when I use the update file location feature it has no trouble reconnecting, whether the folders are on my internal drive or the NAS. So, this functionality seems to be working within Lightroom and I know how to use and abuse it. BUT, it steadfastly refuses to reconnect with the 2014 folder when it's on the NAS, but has no trouble reconnecting when pointed to an exact copy of the same folder on my internal drive.
I'm kind of at my wits end here. There seems to be some sort of bug in Lightroom that makes it lose it's wits when connecting to photos on a NAS drive. Or, I'm doing something really wrong that isn't obvious......

A significant portion of the database buffer cache has been written out to the system paging file.

Hi,
We seem to get this error through SCOM every couple of weeks. It doesn't correlate with the AV updates, so I'm not sure what's eating up the memory. The server has been patched to the latest roll up and service pack. The mailbox servers
have been provisioned sufficiently with more than enough memory. Currently they just slow down until the databases activate on another mailbox server.
A significant portion of the database buffer cache has been written out to the system paging file.
Any ideas?

I've seen this with properly sized servers with very little Exchange load running. It could be a number of different things. Here are some items to check:
Confirm that the server hardware has the latest BIOS, drivers, firmware, etc
Confirm that the Windows OS is running the recommended hotfixes. Here is an older post that might still apply to you
http://blogs.technet.com/b/dblanch/archive/2012/02/27/a-few-hotfixes-to-consider.aspx
http://support.microsoft.com/kb/2699780/en-us
Setup a perfmon to capture data from the server. Look for disk performance, excessive paging, CPU/Processor spikes, and more. Use the PAL tool to collect and analyze the perf data -
http://pal.codeplex.com/
Include looking for other applications or processes that might be consuming system resources (AV, Backup, security, etc)
Be sure that the disk are properly aligned -
http://blogs.technet.com/b/mikelag/archive/2011/02/09/how-fragmentation-on-incorrectly-formatted-ntfs-volumes-affects-exchange.aspx
Check that the network is properly configured for Exchange server. You might be surprise how the network config can cause perf & scom alerts.
Make sure that you did not (improperly) statically set msExchESEParamCacheSizeMax and msExchESEParamCacheSizeMin attributes in Active Directory -
http://technet.microsoft.com/en-us/library/ee832793(v=exchg.141).aspx
Be sure that hyperthreading is NOT enabled -
http://technet.microsoft.com/en-us/library/dd346699(v=exchg.141).aspx#Hyper
Check that there are no hardware issues on the server (RAM, CPU, etc). You might need to run some vendor specific utilities/tools to validate.
Proper paging file configuration should be considered for Exchange servers. You can use the perfmon to see just how much paging is occurring.
These will usually lead you in the right direction. Good Luck!

SCOM reports "A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe performance degradation"

This was discussed here, with no resolution
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/bb073c59-b88f-471b-a209-d7b5d9e5aa28?prof=required
I have the same issue. This is a single-purpose physical mailbox server with 320 users and 72GB of RAM. That should be plenty. I've checked and there are no manual settings for the database cache. There are no other problems with
the server, nothing reported in the logs, except for the aforementioned error (see below).
The server is sluggish. A reboot will clear up the problem temporarily. The only processes using any significant amount of memory are store.exe (using 53GB), regsvc (using 5) and W3 and Monitoringhost.exe using 1 GB each. Does anyone have
any ideas on this?
Warning ESE Event ID 906.
Information Store (1497076) A significant portion of the database buffer cache has been written out to the system paging file. This may result in severe performance degradation. See help link for complete details of possible causes. Resident cache
has fallen by 213107 buffers (or 11%) in the last 207168 seconds. Current Total Percent Resident: 79% (1574197 of 1969409 buffers)

Brian,
We had this event log entry as well which SCOM picked up on, and 10 seconds before it the Forefront Protection 2010 for Exchange updated all of its engines.
We are running Exchange 2010 SP2 RU3 with no file system antivirus (the boxes are restricted and have UAC turned on as mitigations). We are running the servers primarily as Hub Transport servers with 16GB of RAM, but they do have the mailbox role installed
for the sole purpose of serving as our public folder servers.
So we theroized the STORE process was just grabbing a ton of RAM, and occasionally it was told to dump the memory so the other processes could grab some - thus generating the alert. Up until last night we thought nothing of it, but ~25 seconds after the
cache flush to paging file, we got the following alert:
Log Name:      Application
Source:        MSExchangeTransport
Date:          8/2/2012 2:08:14 AM
Event ID:      17012
Task Category: Storage
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HTS1.company.com
Description:
Transport Mail Database: The database could not allocate memory. Please close some applications to make sure you have enough memory for Exchange Server. The exception is Microsoft.Exchange.Isam.IsamOutOfMemoryException: Out of Memory (-1011)
   at Microsoft.Exchange.Isam.JetInterop.CallW(Int32 errFn)
   at Microsoft.Exchange.Isam.JetInterop.MJetOpenDatabase(MJET_SESID sesid, String file, String connect, MJET_GRBIT grbit, MJET_WRN& wrn)
   at Microsoft.Exchange.Isam.JetInterop.MJetOpenDatabase(MJET_SESID sesid, String file, MJET_GRBIT grbit)
   at Microsoft.Exchange.Isam.JetInterop.MJetOpenDatabase(MJET_SESID sesid, String file)
   at Microsoft.Exchange.Isam.Interop.MJetOpenDatabase(MJET_SESID sesid, String file)
   at Microsoft.Exchange.Transport.Storage.DataConnection..ctor(MJET_INSTANCE instance, DataSource source).
Followed by:
Log Name:      Application
Source:        MSExchangeTransport
Date:          8/2/2012 2:08:15 AM
Event ID:      17106
Task Category: Storage
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      HTS1.company.com
Description:
Transport Mail Database: MSExchangeTransport has detected a critical storage error, updated the registry key (SOFTWARE\Microsoft\ExchangeServer\v14\Transport\QueueDatabase) and as a result, will attempt self-healing after process restart.
Log Name:      Application
Source:        MSExchangeTransport
Date:          8/2/2012 2:13:50 AM
Event ID:      17102
Task Category: Storage
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      HTS1.company.com
Description:
Transport Mail Database: MSExchangeTransport has detected a critical storage error and has taken an automated recovery action. This recovery action will not be repeated until the target folders are renamed or deleted. Directory path:E:\EXCHSRVR\TransportRoles\Data\Queue
is moved to directory path:E:\EXCHSRVR\TransportRoles\Data\Queue\Queue.old.
So it seems as if the Forefront Protection 2010 for Exchange inadvertently trigger the cache flush which didn't appear to happen quick or thuroughly enough for the transport service to do what it needed to do, so it freaked out and performed the subsequent
actions.
Do you have any ideas on how to prevent this 906 warning, which cascaded into a transport service outage?
Thanks!

I keep accumulating Cache files on my C drive. This never happenned before. How do I stop it.

I have noticed that I keep accumulating cache files on my C drive. This just started happening and I have to keep deleting them. How do I stop this?
Robert

hello, you can limit the size of your disk cache in firefox > options > advanced > network!

LR 3 will not link to external drive since install of Cache file for another program?

Thumb nails link to the new Cache file on the external hard not the original catalog location on the drive. I can find the files on the drive doing a search in LR but each has to be located individually and confirmed and I have thousands. I deleted the Nikon Capture NX 2 Cache file and its contents but the LR file search still comes up (General> Capture NX Cache). General is the name of the HD with the catalog links. 2 Generals show in both program browsers even though the new Cache file was deleted and does not show when you scan the General HD. Beware LR users keep HD dedicated to LR files only!
Can anyone tell me how to get LR 3 to recognize the original General HD?

Error -36 = I/O error
I have this similar issue before with my external HD. The worst case is that suddenly my external HD would not connect at all. Mac OS does not recognize the device. I end up reformatting the whole HD to Mac format.
I guess the problem is that Mac is having problem reading and writing to a windows formatted drive. I have a few thumb drive that will only work on windows pc but not Mac. Couldn't reformatting it under Mac either. Weird...

Premier Media Cache Files eating up Drive Space

Using Premiere Pro CS 5.5, Media Cache files are eating up the Boot Drive. I keep media and render files on 2 additional internal drives. When I tried to move the Media Cache files from inside Premiere Pro, it resulted in an inability to read the drives from the Startup> Computer menu on the Desktop. This window would open but it was blank with green bar scrolling across the top (as though the computer was trying to read the 3 internal drives. I had to restore the System to correct the problem. How do I reset the Media Cache files to my Render drive which has the most available space without causing a read system problem. When can one safely delete the Media Cache files?
I was an FCP user and all we had to do was delete the render files and/or the media files to get space back. Never had a read system problem from it.

You can do three things.
1 Go to EDIT - Preferences - Media and CLEAN your cache.
2. You can also browse via explorer to the MEDIA CACH. The directory path is shown there in the screen where you CLEAN.
Usually the name is ..../user/yourname/AppData/Roaming/Adobe/Common/MediaCache - the path is shown on that screen and then delete items and render files etc.
3. At that screen, you can also change your Media CACHE to be stored with your Project Files and Autosave files.
4. I think you can delete them anytime, because even if you delete them. Adobe will re-create them next time you open the project, but it will want to relink. But maybe double cheque on this before doing. I have deleted render files out of here with no negative effect. But there are also other files here. That I would want
to do more investigation before deleted. But as it is relinking..don't touch ANYTHING until it completes relinking because that seems to cause the sound and vision to go out of sync. It seems a bit of a bug in Adobe.

Remove caches file's automatically if you delete a folder from your drive???

Gday,
First off all sorry for my poor/bad English.
When i remove/delete a folder in bridge, where will by the cache file of this folder??
Does it also Remove/delete automatically, ????
Or should I in the preferences box, tick on the (automatically Export Cache to folders when possible) option???
Already many Thanks,
Henry

As the others say, no, the backup copy won't be deleted immediately, but it will eventually.
If you want to delete all backups of a selected item, such as for space or security reasons, see #12 in Time Machine - Frequently Asked Questions.

Lightroom cache files permanently written to alternate drive

Similar Messages

Maybe you are looking for