Don't take me wrong, what is being done is phenomenal effort by the dev teams!! My frustration is more that other users who are implementing DNN on an enterprise level aren't participating on the forums. My assumption is that most users are contracting with providers instead of running their own webfarms, which means that there is not much discussion of the kinds of problems I am facing. The intricate details of IIS6 configuration alone is enough to be a full time job researching. And now IIS 7 release is approaching, will that be good or bad? dotNet Framework 3?

I'll send you my document and hope that it contributes to the effort!!

 

Penra ~  No worries.  We appreciate your participation and share some of that frustration, but also understand that a lot of folks are just out there trying to do their thing and participating in the forums just isn't it.  But they do lurk and occasionally drop some feedback on us, and we also solicit them privately for information where we can.  I received your do in the mail today and will have a look at it over the weekend.

Thank you.

---

Scott Willhite, Co-Founder DNN

We are running the this configuration using a remote share and three front end web servers and a shared database server. We have been running under this configuration for almost 9 months now using a domain-level service account as the owner of the processes on each server. Prior to installing, 4.4.1 our sites functioned just fine. Ever since we installed 4.4.1 we have been experiencing countless file locking issues on the /portals/_default/cache folder. As load increases, so do the exceptions. Sometimes it is a security exception trying to access a .resources file in the folder, but most of the time it is the file is being used by another process. I would say 1 out of 10 page requests end up failing with this error. We are not using a web garden and there is one worker process running on each web server. The configuration is exactly the same across all servers.

I have posted regarding this twice and not received even an acknowledgement from the core team about this. So, I will place it here and hope that one of you reading this thread can either a) confirm they are having this issue, b) share configuration info, and/or c) help identify a fix for this.

Any help/response is appreciated.