IIS5 InetInfo 99% utilization

Hello,

We have a Windows 2000 web server that every several days the INETINFO service will peg at 99% until a reboot is done.

I am trying to determine what is setting this off and was wondering if anyone here has had any experience with this and have suggestions on tracking down what may cause this.

Of course I am searhing Google and Microsoft to see if I can find possible solutions.

Thanks in advance.
 
Check for installed DLL(Com objects), make sure any code referencing them terminates when done, otherwise this happens. (We fight this battle on a daily basis)
 
Stephen said:
Check for installed DLL(Com objects), make sure any code referencing them terminates when done, otherwise this happens. (We fight this battle on a daily basis)

We also have OWA for Exchange 5.5 installed on this server and suspect this may have something to do with it. I am going to try a free tool called IISState and see if it will help figure out what is going on.

I know there is software that will report what objects are installed... can you point me to one that Jodo uses or anything you would recommend in listed what they are.

This is all inhouse stuff so not much is being used other than ADO to pull data and then just display it... I think we may have ASPMail, but that is probably it.

Greg
 
Stephen said:
This works well to display ones installed:
http://www.pensaworks.com/prg_com.asp

IISState is good, here is another:
http://www.alchemy.co.nz/products/products_6.html

It is similar to IIStracer, but free.

Thanks for the links...

The IISStatus from alchemy says it is for NT4 only... or at least the readme file says that. I did find microsoft has a beta of Debug Diagnostics 1.0 which seems to be a pretty neat debugging tool. You have to go to http://demo.microsoft.com and then login using a Microsoft passport. Then use DebugDiag as the guestID. You can then download it and a powerpoint presentation on it. Pretty neat looking.
 
gsaunders said:
Thanks for the links...

The IISStatus from alchemy says it is for NT4 only... or at least the readme file says that. I did find microsoft has a beta of Debug Diagnostics 1.0 which seems to be a pretty neat debugging tool. You have to go to http://demo.microsoft.com and then login using a Microsoft passport. Then use DebugDiag as the guestID. You can then download it and a powerpoint presentation on it. Pretty neat looking.

By the way. The Microsoft beta DebugDiag pointed to the OWA as the cuplprit that was bringing down our web server with 99% utilization of the cpu. We have shut it down and have our users using Citrix now since OWA is so old and out dated. At the first of the year we will move to the newest MSExchange and newest OWA.

Greg
 
Back
Top