Localhost not responding

  • Thread starter Thread starter AC
  • Start date Start date
A

AC

Running IIS on my WinXP Pro SP1 machine. Haven't installed anything new lately, but suddenly overnight, IIS has stop responding. At first I thought it was Visual Studio.NET 2003 because it would hang when it tried to load web projects, but after trying to navigate to the http://localhost (or by IP), I saw that it wouldn't ever respond... not even timeout... just keeps waiting for a response.

Some info:
I can't access ASP.NET, ASP, HTML, GIFs, or TXT files via the IIS root OR a virtual directory.
Haven't found anything that would indicate errors in the event log
Resetting IIS doesn't help
I can navigate the IIS admin manager just fine
Running NetStat -an doesn't seem to show IIS listening on 80 on the loopback (doesn't show 127.0.0.1), but it does show it listening on 0.0.0.0:80
No errors shown in the IIS log files
Click to expand...

I haven't changed any network settings that would affect the loopback.

Only think I can think of right now is to backup the metabase and uninstall/reinstall IIS... any other ideas?
 
If the metabase is corrupt and making IIS hang, it might be faster to
reinstall than fight with it.



Running IIS on my WinXP Pro SP1 machine. Haven't installed anything new
lately, but suddenly overnight, IIS has stop responding. At first I thought
it was Visual Studio.NET 2003 because it would hang when it tried to load
web projects, but after trying to navigate to the http://localhost (or by
IP), I saw that it wouldn't ever respond... not even timeout... just keeps
waiting for a response.

Some info:
I can't access ASP.NET, ASP, HTML, GIFs, or TXT files via the IIS root OR
a virtual directory.
Haven't found anything that would indicate errors in the event log
Resetting IIS doesn't help
I can navigate the IIS admin manager just fine
Running NetStat -an doesn't seem to show IIS listening on 80 on the
loopback (doesn't show 127.0.0.1), but it does show it listening on
0.0.0.0:80
No errors shown in the IIS log files
Click to expand...

I haven't changed any network settings that would affect the loopback.

Only think I can think of right now is to backup the metabase and
uninstall/reinstall IIS... any other ideas?
 
Thanks Ken... figured it out.

Ends up it was a database issue. We're running Microsoft Content Management
Server 2002. The ISAPI filters running on the IIS installs trying to query
the DB on every URL request to determine if CMS was supposed to manage the
URL based on the first subdirectory supplied. For the first time, a single
database on the entire server was hung up so it was never getting a reply,
and therefore the request was never getting to IIS for a timeout or HTTP
error status code to be returned. After a reboot of the database server
(SQL Services), it started working.

First it looked like it was VS.NET, then IIS... then it took a while to
track it down to the ISAPI filters and then the DB (finally uncovered it
when we removed the CMS ISAPI filters from one of the IIS installs).

-AC
 
Back
Top