M
mills.toby
We have a Windows 2003 Server, serving an asp.net (2.0) website.
Recently the website stopped responding. When trying to access the
website, no response is received at all. This includes when browsing
the website from the local machine.
While investigating the problem, we added a second copy of the
website, created a second virtual directory in IIS, tried to access
it, and it worked. The original website was still not responding.
Further investigation showed that after restarting IIS, whichever of
the 2 websites was accessed first would hang, and then the other would
work just fine. The problem also is restricted to an Application Pool.
If I create a second application pool, with two more copies of the
website, only the website accessed second will respond (i.e. we have
two responsive and two non-responsive websites).
This problem only began recently on 2 separate servers (on the same
WAN) that were both previously working fine. We created a brand new
Virtual Server and were immediately faced with the same problem.
We have two other servers on the same WAN, with the same website
installed which do not suffer from this problem at all.
Has anybody seen anything like this before?
Thanks in advance,
Toby
Recently the website stopped responding. When trying to access the
website, no response is received at all. This includes when browsing
the website from the local machine.
While investigating the problem, we added a second copy of the
website, created a second virtual directory in IIS, tried to access
it, and it worked. The original website was still not responding.
Further investigation showed that after restarting IIS, whichever of
the 2 websites was accessed first would hang, and then the other would
work just fine. The problem also is restricted to an Application Pool.
If I create a second application pool, with two more copies of the
website, only the website accessed second will respond (i.e. we have
two responsive and two non-responsive websites).
This problem only began recently on 2 separate servers (on the same
WAN) that were both previously working fine. We created a brand new
Virtual Server and were immediately faced with the same problem.
We have two other servers on the same WAN, with the same website
installed which do not suffer from this problem at all.
Has anybody seen anything like this before?
Thanks in advance,
Toby