I am developing a website for our client, and I have had problems with grunts for several weeks. The problem is intermittent and can occur twice a day or once every 2 weeks.
When this happens, the client will begin to receive 401.3 "Unauthorized" errors when trying to load static script or style tags on the page. This is always a .css or .js file that fails, and setting <modules runAllManagedModulesForAllRequests="false" />
does not fix the problem. When a problem occurs, it effectively locks the file until the application pool restarts.
The site uses forms authentication with a margin of "AspNetSqlMembershipProvider". The site is protected by files in the / Accounts folder, styles in / Styles and scripts in / Scripts. The site has anonymous access and has a separate web.config file in the / Accounts folder, which prohibits access to anonymous users (although this does not even matter with runAllManagedModulesForAllRequests = false).
I looked at the event logs and I see the following:
2012-06-06 14:23:32 [ipaddress] GET / subfolder / Styles / Site.css ver = 11 443 - [ipaddress] Mozilla / 5.0 + (Windows + NT + 6.1; + WOW64; + rv: 12.0) + Gecko / 20100101 + Firefox / 12.0 https://thesitename.net/subfolder/Account/Login.aspx 401 3 5 1493 429 62
Sometimes after a short period of time it fixes itself or restarts the application pool, I get the following:
2012-06-06 14:30:30 [ipaddress] GET / subfolder / Styles / Site.css ver = 11 443 - [ipaddress] Mozilla / 5.0 + (Windows + NT + 6.1; + WOW64; + rv: 12.0) + Gecko / 20100101 + Firefox / 12.0 https://thesitename.net/subfolder/Account/Login.aspx 200 0 0 2533 455 78
Finally, I got a hosting provider that turned on failed request tracing and finally got an error trace:
Every failed request trace file I received this time said that the crash happens right after the FILE_CACHE_ACCESS_END event. What does this event do and why will it be denied access?
source share