Link to home
Start Free TrialLog in
Avatar of ziwez0
ziwez0

asked on

inetinfo.exe 99% CPU usage

Ive come into work this morning to find that are windows 2000 webserver is running very/dead slow.

something called inetinfo.exe is using all the cpu power, i cant get into iis admin to end the process ive tried stopping iis in services but it wont, has anyone have any idea how to get it working back to normal?

Cheers

David
Avatar of fz2hqs
fz2hqs

Run iisreset from teh run dialog - that will restart the inetinfo.exe process. If that fails try a reboot !

Inetinfo.exe is the webserver, chances are that either some code recently uploaded has gone into an infinite loop ?

Also try and get your hands on something that will tell you what is going on inside the webserver i.e. http:///www.iisfaq.com/iisstate running that will tell you what it is that is going on, and hoopefully at the time when it has maxxed out the processor
Avatar of ziwez0

ASKER

ok ive reinstalled all of iis again when i clicked on the link to from our main website to our online server inetinfo.exe went from 1% to 99%, i replaced all of my code with a backup (that worked fine), but the only thing i didnt change was the database, but the database dose not come into effect until the second page, its just a pure html page the first page.

(oh yeah i did restart the online server)
ASKER CERTIFIED SOLUTION
Avatar of fz2hqs
fz2hqs

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You might have a an infinite loop in the code somewhere.
you need to debug the problem, your saying it only happens when you click on a link from the main website, isolate this page and everything that is called from page, and go through the code, run it bit by bit, i.e. take all the code out and put it back in bit by bit. You might even be able to use breaks with ASP I don't know since I'm not an ASP person?
Have you uploaded some new stuff to the website lately?
Avatar of ziwez0

ASKER

Their was a problem with the code in conection to the db, its now been corrected.

thanx guys.