A
amessimon
Hi
Im having a problem at the mo where i have site (built in asp.net) that
can work reliably for 2-3 hours at a time. Ocassionally it just fails to
respond and i cant access any pages. Restarting the site in IIS seems to
fix the problem.
Im running 'karens net monitor and generally what i see is a long period
of reliability followed by ....
Error: Request timed out (35761)
This is usually followed by combinations of ....
HTTP Error: Operation canceled (12017)
Error: 500 (Internal server error)
This continues until i restart the site in IIS. Initially i thought it
might be because i had mistakenly deployed the site with debugging still
enabled in web.config. Having removed "<compilation debug="true"/>" i
hoped this might fix the problem as im aware that it can have a
detrimental effect on performance. Once the error occurs all .aspx pages
in the site fail to respond.
Anyone got any ideas on this?
Thanks in advance
amessimon
Im having a problem at the mo where i have site (built in asp.net) that
can work reliably for 2-3 hours at a time. Ocassionally it just fails to
respond and i cant access any pages. Restarting the site in IIS seems to
fix the problem.
Im running 'karens net monitor and generally what i see is a long period
of reliability followed by ....
Error: Request timed out (35761)
This is usually followed by combinations of ....
HTTP Error: Operation canceled (12017)
Error: 500 (Internal server error)
This continues until i restart the site in IIS. Initially i thought it
might be because i had mistakenly deployed the site with debugging still
enabled in web.config. Having removed "<compilation debug="true"/>" i
hoped this might fix the problem as im aware that it can have a
detrimental effect on performance. Once the error occurs all .aspx pages
in the site fail to respond.
Anyone got any ideas on this?
Thanks in advance
amessimon