.NET & Web Applications In General

  • Thread starter Thread starter Jim Douglas
  • Start date Start date
J

Jim Douglas

How many times a day do other's have to reset IIS or reboot a system? We are
rolling out our first .NET application and during the pilot phase found that
we need to reset IIS at lease 2-3 times a week, we have only about 50 users
on it now! We have implemented exception handling and EIF and see nothing
that points to an issue within any logs. The applications just "freeze", in
theory the network monitoring guys say the machine is not busy neither is
memory?

Any ideas of what to check would be appreciated.

Thanks,

Jim Douglas
 
Jim Douglas said:
How many times a day do other's have to reset IIS or reboot a system? We
are
rolling out our first .NET application and during the pilot phase found
that
we need to reset IIS at lease 2-3 times a week, we have only about 50
users
on it now! We have implemented exception handling and EIF and see nothing
that points to an issue within any logs. The applications just "freeze",
in
theory the network monitoring guys say the machine is not busy neither is
memory?
Click to expand...

I never have to restart IIS unless there's a problem with some COM
component.


John Saunders
 
2-3 times/week is a lot. A number of things could cause IIS to
hang...calling any service on other boxes (database, web services, network
shares), calling COM components...

You can try checking your COM+ Applications to see if there's a large number
of objects, check your web service & asp.net counters in perfmon, or use the
IIS Crash/Hang agent. The Crash/Hang agent is nice b/c it can give you a
dump of what all your IIS threads are doing.
 
Back
Top