The process cannot access the file NuCache.Content.db because it is being used by another process
Hi! We have an umbraco v.10 site that we released to production earlier this week. Unfortunately the site crashed almost right away and we received following error "The process cannot access the file NuCache.Content.db because it is being used by another process".
The error occurred inconsistently and some users could access the site and some didn't. It seemed that it was connected to localDb caching since setting "IgnoreLocalDb" to true in code seemed to solve the issue. See link below:
The process cannot access the file NuCache.Content.db because it is being used by another process
Hi! We have an umbraco v.10 site that we released to production earlier this week. Unfortunately the site crashed almost right away and we received following error "The process cannot access the file NuCache.Content.db because it is being used by another process".
The error occurred inconsistently and some users could access the site and some didn't. It seemed that it was connected to localDb caching since setting "IgnoreLocalDb" to true in code seemed to solve the issue. See link below:
https://docs.umbraco.com/v/10.x-lts/umbraco-cms/reference/configuration/nucachesettings#additional-settings.
We have two environments that share the same database, stage and production.
Is this the right approach to address this problem and is it reliable long term?
Hi Emma, We only use one environment, on site to use one database but we have just run into the same problem in 10.8.3.
Have you found the fix?
Hi Ewuski,
If you're using Azure, then this post by Jason, from the Umbraco Discord server, might be helpful to you:
Public Umbraco Discord mirror/archive:
https://discord-chats.umbraco.com/t/16365547/nucache-nucache-content-db-because-it-is-being-used-by-anoth#6ac57c8f-ea5c-482f-a5ea-ed795101648f
Actual Discord link:
https://discord.com/channels/869656431308189746/1203003576511897621/1206945725741535243
Edit: Just noticed you replied to the thread in Discord, sorry!
is working on a reply...