@guillaume86 Our issue was the result of a memory leak in the IIS Advanced Logging that was installed on the servers that exhibited the problem. Patching the known Microsoft bug in the IIS Advanced Logging module completely eliminated these errors for us. So there wasn't really a work-around, we patched the bug in IIS Advanced Logging and that fixed the memory leak that it caused in our app pool/application.
↧