Hello,

I am having a problem with a locked resource file, and I have tried everything I can think of to solve this issue, but have had no success, yet.

I am not sure where to start. In the Portals\_default\Cache folder there is 412517EFE3EAAF5BD4873D1097CA25CC.resources file. It is always this file that trips up the site. I can easily reproduce the problem by opening two browsers and trying to navigate the website. One or both browsers will error out with this error.

The process cannot access the file 'D:\Inetpub\wwwroot\PNE1\Portals\_default\Cache\412517EFE3EAAF5BD4873D1097CA25CC.resources' because it is being used by another process.

I have checked file permissions and have given full control to both IUSER and Network Service to ensure enough permissions. I had started to create a module using the live server until I read enough to know that was not a good idea, so I made sure I cleaned all the old files off. I tried deleting the resources file (created backup first) and now I get Service Unavailable. I restored the file from backup and still got the Service Unavailable error. I restarted IIS and it is now available. Unfortunately, I still get the locked resources file.

Here is an excerpt of what is in the file. Hopefully, it will help.

<dictionary><item key="36" type="DotNetNuke.Security.Permissions.TabPermissionCollection, DotNetNuke, Version=4.8.3.4, Culture=neutral, PublicKeyToken=null"><ArrayOfTabPermissionInfo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

I would be very grateful for any help to get this fixed.

Thank you.

 Ben

I seem to have it figured out, although I am still testing. In the host settings, I had module cache set to memory. However, after viewing this thread:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/118/threadid/221834/scope/posts/Default.aspx

and

http://www.snapsis.com/DotNetNuke/Support/tabid/560/forumid/11/postid/6093/view/topic/Cache-Folders-in-the-Portal-Root-causing.aspx

I checked the web.config file and it had:

<add key="EnableCachePersistence" value="true" />

I set it to false and tried to recreate the problem and so far no errors. I am not sure if the setting in the host settings are directly related to the value in the web.config file, but it seems that perhaps exposing a way to edit the property in the web.config file without having to dig through everything might be beneficial.

Thank you.