Hi everybody,

About once in a week we're getting this message from IIS and only re-starting it seems to be the cure.

I guess it's too general question to answer, but anyway, may be someone had similar experience and know what should we change in our configuration.

Thanks in advance.