>>I don't know. In your original post you mentioned that another application in the same environment also experienced problems so that might well point to a NAS related issue. OTOH the event log entries for the caching problem shows that the compression error relates to the local c: drive. Also it implies that the problem is not fatal - just that compression is being disabled.
>
>The switch will be set tomorrow night. So, I will be able to see during the week if this resolves the issue with the event log. If yes, I will leave it as is for a few weeks to see if there could be any kind of relation with that and the recycle issue on the worker process that happens exactly at the same time. And, I would also have to verify about the cause of the compression so to resolve it and have it back enabled.
>
>>It might be worth temporarily disabling the web-garden (i.e. setting 'Maximum Worker Process' to 1) and see if the problem still occurs.
>
>I cannot do it as we have too much traffic. I really need to have at least 3. So, I will leave it at 4.

How did you determine that this is the case? What degradation did you find when using just one instance ?

>>Don't know if this can help (never used it) : http://www.iis.net/downloads/community/2009/11/aspnet-debugger-extension-for-iis-7
>
>I will take note of that and might have to use it on the long run.
>
>>You could try turning on event logging for more recycle related events (in the 'Generate Recycle Event Log Entry' section) but it may not help.
>>Also log application start events in ASP.NET to see if it gets that far (and make sure any exception there gets logged)
>
>I am also wondering if IIS 8 has this issue. However, I am not sure if we can run IIS 8 on Windows Server 2008.

Pretty sure that you can. If IIS8 Express works (http://www.microsoft.com/en-gb/download/details.aspx?id=34679) then I'd assume same for full IIS8?

>
>On this one, I might have to contact Microsoft support as this is a very unique situation and I still believe it is related to the environment. I do not know if you remember, but, a while ago, before deploying, I noticed that we had some servers not responding exactly the same on the network and they had a similar configuration. So, I suspected something at the higher level such as the VMWare, privileges and so on. We still have some servers flagged as red. The one that this IIS issue is happening on is flagged as red. This was the issue when the Windows Service takes longer to load than the same Windows Service on another server with the same configuration. And, those servers have all been cloned. So, for as long as that one is not resolved, this could all be related. We know we did not have that before. It is only since we moved to this new environment. I also did not have that on about 60 IIS installations I have done over the years. The recycle process is one of the smootest operation that IIS does. It has always been working 100% up until we moved into this new architecture.

MS might duck the issue if non-MS technologies are involved :-{