ASP stops working on IIS4

Has anyone encountered a problem where .asp pages suddenly stop working on
an IIS4 server. All other types of pages such as .html work fine but asp
pages will no longer work. One of the things that we noticed is that when
the server stops serving asp pages the Inetinfo process is using 100% cpu
and continues to so do until the Inetinfo process is killed. The solution
for this problem thus far has been to kill the inetinfo process and restart
the IIS services. We have been experiencing this problem intermitently
since this past weekend and have experienced this problem once or twice
since the beginning of the year. The server has sporatically been doing
this throughout the week and has done this 2 to 3 times in the same day.
This has become a big problem for the past week and we have thus far been
unable to find the cause of this problem. We find no indication of a
problem in the event logs. Does anyone have a solution to this problem or
has anyone ever seen this problem? Any input would be greatly appreciated.

Thanks in advance.

AAO

Most likely a bug on an ASP page. Run IISState (www.iisfaq.com/iisstate)
against inetinfo.exe when it is at 100% CPU. If you need help w/the log
file, you can post it to the group.

iisstate -p <pid of inetinfo.exe> <enter>

Pat


"AAO" <ortiza.RemoveThis@uthscsa.edu> wrote in message
news:%235S1X5ZmDHA.2160@TK2MSFTNGP10.phx.gbl...
 > Has anyone encountered a problem where .asp pages suddenly stop working on
 > an IIS4 server. All other types of pages such as .html work fine but asp
 > pages will no longer work. One of the things that we noticed is that when
 > the server stops serving asp pages the Inetinfo process is using 100% cpu
 > and continues to so do until the Inetinfo process is killed. The solution
 > for this problem thus far has been to kill the inetinfo process and
restart
 > the IIS services. We have been experiencing this problem intermitently
 > since this past weekend and have experienced this problem once or twice
 > since the beginning of the year. The server has sporatically been doing
 > this throughout the week and has done this 2 to 3 times in the same day.
 > This has become a big problem for the past week and we have thus far been
 > unable to find the cause of this problem. We find no indication of a
 > problem in the event logs. Does anyone have a solution to this problem or
 > has anyone ever seen this problem? Any input would be greatly appreciated.
 >
 > Thanks in advance.
 >
 > AAO
 >
 ><!-- ~MESSAGE_AFTER~ -->