continuously memory increase on front end server

6 Dec 2006 9:27 AM

Pat

Hello

On our Exchange2003 Front End server we have a continuously memory increase.
Responsible seems to be inetinfo.exe. This process consumes Memory until the
whole system gets instable.

After e reboot it is set back to normal.

How can I avoid that?

Thanks,
Patrick

6 Dec 2006 4:43 PM

Mark Arnold [MVP]

On Wed, 6 Dec 2006 01:27:00 -0800, Pat <P**@discussions.microsoft.com>
wrote:

>
>Hello
>
>On our Exchange2003 Front End server we have a continuously memory increase.
>Responsible seems to be inetinfo.exe. This process consumes Memory until the
>whole system gets instable.
>
>After e reboot it is set back to normal.
>
>How can I avoid that?
>
>Thanks,
>Patrick

Not sure. Inetinfo.exe is an IIS component so it might not actually be
Exchange causing the process to run away. Have you checked what
happens when Exchange services on the FE are not running, i.e. does
inetinfo still go mad?

7 Dec 2006 8:14 AM

Pat

Show quote Hide quote

"Mark Arnold [MVP]" wrote:

> On Wed, 6 Dec 2006 01:27:00 -0800, Pat <P**@discussions.microsoft.com>
> wrote:
>
> >
> >Hello
> >
> >On our Exchange2003 Front End server we have a continuously memory increase.
> >Responsible seems to be inetinfo.exe. This process consumes Memory until the
> >whole system gets instable.
> >
> >After e reboot it is set back to normal.
> >
> >How can I avoid that?
> >
> >Thanks,
> >Patrick
>
> Not sure. Inetinfo.exe is an IIS component so it might not actually be
> Exchange causing the process to run away. Have you checked what
> happens when Exchange services on the FE are not running, i.e. does
> inetinfo still go mad?
>

Since the FE is running in an productive environment I can not stop the
Exchange services. The process of memory increase is going over days.

But when I replace the active FE through our second FE then the increase of
memory stops on the passive one.
We have two FE and memory increase is always on the acitve one and stops on
the passive.

Patrick

7 Dec 2006 9:10 PM

Mark Arnold [MVP]

Well that answer has the same effect of leading one towards Exchange
itself rather than merely IIS.
Good idea to check all the build states for SP level and pathes.
Post the numbers back here if you need and someone might be able to
look through them and point you to an out of date something or other,
be it Exchange or IIS.