Find bad script/app in IIS6
Putting sites one by one into a separate "test" pool until we find which one is the problem is one method, but would be very time consuming. There must be a way of getting at the info, as IIS uses it internally?
Putting sites one by one into a separate "test" pool until we find which one is the problem is one method, but would be very time consuming. There must be a way of getting at the info, as IIS uses it internally?
