Urgent Help!!!! (inetinfo.exe problem)

[ckong]

I have code an Attachment (Upload File) Function by using MS WebPost (In ASP Format). When I try to upload some files from User Client PC to a Web Server, my webserver inetinfo.exe jumps to 50-100% cpu usage and won't come down until I restart the server.

I'm running NT4.0 and IIS4.0 SP 5.0. The Server's RAM is 128M.

Question
1. Is it because of the limitation of memory?
2. Is there a way to solve the problem?
3. Beside MS WebPost, can I use other ways to code the Attachment Function?? Would it solved the problem?? What method that I can use?? How??

 

[Nikolaj]

Hi!!

I have the exact same problem!!!!

I have found this but it dosent help me much!! Maybe it can help you!

> Dear all,>
> I have two IIS 5 (clustered) connecting to SQL 7.0 server. There are ASP
> running on those IIS 5. The IISs handle about 180 concurrent users and I
> found there are about 30 connections to the SQL server from IISs. The
> problem is that the CPU utilization keep constantly at 100%, even when the
> the concurrent users drop down to about 20. The CPU usage can be reduced
> only when I restart the IIS.

you should use SQL Profiler to see which connections in SQL Server are
consuming the most CPU and then see what those queries are doing.


Use Performance Monitor to track down what is using the CPU's. Keep in mind
that many things on NT are interrelated.Some measures to check:
Memoryages/Sec greater than 0 or Memoryage Reads/Sec greater than 5
means that Windows is going to disk to resolve memory references. These are
hard page faults which will cost disk I/O and CPU Resources.
Memory: Page Faults/Sec - Memory: Pages Input/sec
This reading is your Soft Page Faults per second. This reading won't
typically be zero, but watch for high numbers. Until SQL Server accesses
all of it's data cache pages for the first time, these intial accesses will
cause soft page faults. But look into what process using Process: Page
Faults/sec is causing soft page faults if it is high. Soft Page faults
consume CPU resources.
Systemrocessor Queue Length. If it is greater than 2 for each cpu the
processors are receiving more work requests than they can handle. This can
be caused by hard and/or soft paging


Regards

Nikolaj