What are the steps required to defragment the .NET Framework on my Notification Server and why is it necessary?
When workers are getting licensing errors on Helpdesk, this is due to an excessive amount fragmented temp files in the “Temporary ASP.NET Files” folder. As the number of assemblies that are loaded in a process grows, the virtual address space can become fragmented. When the virtual address space is fragmented, out-of-memory conditions are more likely to occur. To prevent a large number of assemblies from loading in a process, ASP.NET tries to compile all pages that are in the same directory into a single assembly. This occurs when the first request for a page in that directory occurs. In the case of our software, the amount of items that are constantly being cached, grows which in turn causes memory problems. Removing these files/folders removes everything from memory and allows a clean start.
First try to restart .NET to clear all of its current memory accations and let it start with a fresh memory set.
If this does not work, then it maybe an issue with the pre-compiled .NET code. To force .NET to reset and recompile every page. The following steps can be followed.
In extreme cases, .NET itself may be corrupted and may need to be completely re-installed, but this should be reserved only if the above attempts are still falling.
NOTE: This is not to be used on Notification Server 7 as it uses .NET 2.0 and the above sets 1.1 as the default to Default Web Site. If performed on NS 7, just edit the Default Web Site back to .NET 2.0.