Odd problem

D

Dave

I have about 30 sites all using FPSE without any trouble. Then this
morning one of them was unresponsive. Couldn't hit the URL, but it would
load within FrontPage. I tried stopping and starting that particular
site, but that did no good. The solution was to run IISRESET.

I guess my question is why would this happen? Or what could have caused
this?

thanks!
 
K

Kevin Spencer

Do you have a URL for us to look at?

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
 
J

Jim Buyens

A lot of weird stuff happens to a Web server. Visitors
send malformed requests, they terminate connections
unexpectedly, they click the Submit button twenty or
thirty times if there's a momentary delay in response. In
addition, no piece of software is immune to memory leaks
and other problems that build up over time. As a result,
all Web servers (and not just IIS) occasionally hang for
no apparent reason.

If this turns out to be a one-time occurrence, I'd
probably just forget about it. If it keeps happening, you
may want to institute regular reboots (i.e. once a month
of once every two weeks). If it starts happening a *lot*,
you may want to increase the amount of physical memory on
the server, check the overall server load, or look for
hardware problems.

And of course, stay up to date with all Windows Updates
and other fixes.

It's very odd, however, that you could access this site
via FrontPage (using http, I presume) and not via the
browser. The opposite problem (accessible by browser, not
by FrontPage) is much more common. This suggests that some
network interruption may have occurred at about the same
time. Which is also nothing to worry about, unless you're
the network guy or wish to beat up on one.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------
 
D

Dave

Wow. Great response - thanks Jim!

Jim said:
A lot of weird stuff happens to a Web server. Visitors
send malformed requests, they terminate connections
unexpectedly, they click the Submit button twenty or
thirty times if there's a momentary delay in response. In
addition, no piece of software is immune to memory leaks
and other problems that build up over time. As a result,
all Web servers (and not just IIS) occasionally hang for
no apparent reason.

If this turns out to be a one-time occurrence, I'd
probably just forget about it. If it keeps happening, you
may want to institute regular reboots (i.e. once a month
of once every two weeks). If it starts happening a *lot*,
you may want to increase the amount of physical memory on
the server, check the overall server load, or look for
hardware problems.

And of course, stay up to date with all Windows Updates
and other fixes.

It's very odd, however, that you could access this site
via FrontPage (using http, I presume) and not via the
browser. The opposite problem (accessible by browser, not
by FrontPage) is much more common. This suggests that some
network interruption may have occurred at about the same
time. Which is also nothing to worry about, unless you're
the network guy or wish to beat up on one.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------




Then this


URL, but it would


could have caused
 
Top