Discussion Locked

inetinfo process takes the server memory

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

NT 4 Server with PIII 800MHz, 256 MB RAM, 512 Paging file size, gets out of memory. Initially every thing works fine. But later on the developers complain about slow response of server. Inetinfo process actually takes the major portion of memory & causes the server to slow down.

I removed IIS 4 & patches & then reinstalled them. Now the problem still comes occasionally.

Im getting the following errors at this application server which is NT4, sp6, SRP patch ,IIS,4 Visual studio SQL installed.

From my w2k system Im pasting the error messages here.

Event Type: Error
Event Source: IISInfoCtrs
Event Category: None
Event ID: 1003
Date: 10/18/2001
Time: 11:54:03 AM
User: N/A
Computer: C3K
Description:
Unable to query the IIS Info service performance data. The error code returned by the service is data DWORD 0.
For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.Data:
0000: ff ff ff ff ????

Event Type: Error
Event Source: W3Ctrs
Event Category: None
Event ID: 1003
Date: 10/18/2001
Time: 11:54:03 AM
User: N/A
Computer: C3K
Description:
Unable to query the W3SVC (HTTP) service performance data. The error code returned by the service is data DWORD 0.
Data:
0000: 01 00 00 00 ....

6 replies

by faisalmasood

Just read the KB article Q201638 regarding 1003.

But why Inetinfo process taking too much memory. or Tell me how can I track if a particular application module / page is cauging IIS to slow down the server. Our application is ASP based running onIIS4.

by leo.valmores

InetInfo is a central process of IIS for the HTTP/FTP standard services. It also contains standard info services, caches, loggings, SNMP support. It is no wonder why it try to gobble as much memory as it can from your server.

First, try to trace back your ASP apps and zero-in if there are huge caches that were created and to release them when done.

Secondly, try to upgrade your server's mem from 256 to at least 512 or better still 1024MB.

Hope this helps....

by bhrdwh

I think its due to your Developers' ASP code.
Ways to trck this is...
1. Remove your web site & install IIS Default Site. Now let it run for few hrs, check if INETINFO goes 100%.
2. Install PWS on the Developers Systems & ask thm to work on theirmodules on their PCs.
This way you can isolate which delelopers' module is the mem hog.

Increase the Server RAM to 512MB & Pagefile to 760MB is another option.
Akash

This discussion is closed to new replies.