I understand from MS that IIS6.0 has an issue with Memory Fragmentation that is supposed to be resolved in IIS7.0. In the meantime, has anyone found anything that will help remedy these out of memory errors?
A couple things I have tried:
-Reset IIS when the problem occurs.
-Schedule application pool recycles after hours.
As you can imainge, these are not the best of solutions. Is there anything else we can do to help with these, other than upgrade to Server 2008? They cause quite an issue for users of our web application.
Some background on our paticular sitation. We worked with MS for months on this issue and it was determined that we were suffering from Memory Fragmentation, which was to be fixed with IIS7.0/Server 2008. I am sure nobody has a magical fix, but just curious if anyone else uses another method to help remedy this situation.
Thanks.