Hello Forums.
I recently started at a job as an Engineer and told of a problem our web servers we have had in the past which locks up IIS and kicks off users logged on. Sadly I have not been present for this myself. The problem is about a IIS / Server issue about a locked / corrupt temp .net file. It has happened twice this year, in January and March. The resulting action of this is that the memory will continue to be eaten until we restart the AppPool.
We receive this non descriptive email to our IT inbox(that is all it says):
Task Server Manager is currently running no tasks but appears to be unusually busy.
We do get other emails with the subject line Unhandled Exception: System.Web.HttpException
It lists files as not being found in the body of the email.
Message: The file '[filename]' does not exist.
It is known that the solution is to stop the AppPool kicking all users off, deleting all files and folders in the \Temporary ASP .NET Files\root, and then starting the AppPool.
We are on Microsoft Windows Server 2008 version 6.1, build 7601, SP 1, R2
IIS version 7.5
Is the root user creating and locking the files preventing .NET from doing any garbage cleanup?
Should any specific best practices be followed to prevent this?
Thanks for reading