Windows Forum

Ask something
Discussion Locked

inetinfo.exe using 99% of CPU

0 helpful
5 replies

by scifiman 2 views

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

PLEASE EMAIL 'AUTHORSHIP@AOL.COM' TO ANSWER THIS QUESTION:

My Exchange server (W2K Advanced Server; Exchange 2000) began having a problem last week with INETINFO.EXE using 99 percent of the CPU, although email kept working. Memory for that process shows 24,316. Today I moved the server from where it was being hosted back to our office and I need to change it's IP address, etc. Trouble is, now inetinfo.exe is still using 99% and as soon as the desktop comes up it bogs down so badly I can'teven bring up the start menu. Every mouse click takes over 15 minutest to happen. Task Manager can't kill inetinfo, says "access denied". Does anyone have any suggestions as to how to kill that process and/or repair this problem. Hopefully without messing up Exchange, which I am not in a position to rebuild without intense pain. I don't have an emergency repair disk for that server. Would reinstalling Windows damage Exchange??? Or would it even help?

Thanks!
David

5 replies

by ewgny

Disable IIS Admin service from Services. If you can't get there from the OS boot into recovery console from the CD and disable it. INETINFO.exe is related to IIS. You will then have your CPU back to find out the problem.
See http://tinyurl.com/d6hr
Once you disable it you won't have IIS, but at least you will be able to work on the problem.
Possibly re install of IIS would help at that point.

by scifiman

After 4 hours or so the box worked through its start up issues and although still at 99% at least the console useable if slow.

I will try your suggestions this weekend. Thank you!

by bcot

I assume you have used the latest virus updates and suggest you sweep the server having paused the services.

by scifiman

I have the latest and it auto scans twice each day, plus Antigen for Exchange itself. But I will try to suspend services and manually check it also. Thanks, and sorry for the late response!

This discussion is closed to new replies.