IIS hangs every 36 hours, must reboot to restore

Hello,

I have II6 running on a new 2003 server with FrontPage extension installed.
That's all that is running on the box (Dell PE 2900) except for Backup Exec.
All patches up to date.

The server hums along fine for about 36 hours then simply stops serving.
Clients recieve page not available or connection reset depending on which
browser is used.

Simply stopping and restarting IIS doesn't fix the issue. I must reboot the
server.

I am now running the debug diagnostic tool in an attempt to capture any
hints as to what is the issue.

Anybody have experience with this? How can I fix?



There are no errors in the log files. Other than not serving, the server
seems to be fine.
--
JT

Justin
Wed May 09 14:48:02 CDT 2007

how long has it stayed in a hung state?
some simple things to take a look at (just to rule out) would be to see if
the port is open to accept web requests...

netstat -a

if the port is there and listening then try to connect to it and send a get

telnet servername 80
get

the get should return and error with a bad request (cuz it is) but this will
let you know where IIS stands.

if its not responding at all then its pretty well screwed.
what was the last thing accessed in your IIS logs? could it perhaps be a
page that has some crazy code thats locking it up?

what is IIS serving? static HTML? ASP? ASP.NET? do you have an ISAPI
filters?

if the failure closer to 36 hours or closer to a certain time?

how are the resources on the machine? page file free? memory free? paged and
non-paged pool?

I think what you have done is a great start but we need a LOT more
information to really give you any guidance.

let us know what you find with the debug.


"JT" <JT@discussions.microsoft.com> wrote in message
news:81C455E6-6960-475C-BD58-B0E99E26EAA9@microsoft.com...
> Hello,
>
> I have II6 running on a new 2003 server with FrontPage extension
> installed.
> That's all that is running on the box (Dell PE 2900) except for Backup
> Exec.
> All patches up to date.
>
> The server hums along fine for about 36 hours then simply stops serving.
> Clients recieve page not available or connection reset depending on which
> browser is used.
>
> Simply stopping and restarting IIS doesn't fix the issue. I must reboot
> the
> server.
>
> I am now running the debug diagnostic tool in an attempt to capture any
> hints as to what is the issue.
>
> Anybody have experience with this? How can I fix?
>
>
>
> There are no errors in the log files. Other than not serving, the server
> seems to be fine.
> --
> JT

David
Thu May 10 03:33:39 CDT 2007

Sounds like you want to read this blog entry and read the extensive
set of comments of what users have encountered that cause this issue
-- all were problems outside of IIS6 and Windows:
http://blogs.msdn.com/david.wang/archive/2005/09/21/HOWTO-Diagnose-IIS6-failing-to-accept-connections-due-to-Connections-Refused.aspx

I am going to speculate that Backup Exec or your Network card driver
are to blame for your issue.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On May 9, 8:07 am, JT <J...@discussions.microsoft.com> wrote:
> Hello,
>
> I have II6 running on a new 2003 server with FrontPage extension installed.
> That's all that is running on the box (Dell PE 2900) except for Backup Exec.
> All patches up to date.
>
> The server hums along fine for about 36 hours then simply stops serving.
> Clients recieve page not available or connection reset depending on which
> browser is used.
>
> Simply stopping and restarting IIS doesn't fix the issue. I must reboot the
> server.
>
> I am now running the debug diagnostic tool in an attempt to capture any
> hints as to what is the issue.
>
> Anybody have experience with this? How can I fix?
>
> There are no errors in the log files. Other than not serving, the server
> seems to be fine.
> --
> JT

David
Thu May 10 03:37:07 CDT 2007

And you want to read this blog entry on how to start troubleshooting.
You only need to look for a couple of log files to conclude where
things are disconnected.

http://blogs.msdn.com/david.wang/archive/2005/12/31/HOWTO_Basics_of_IIS6_Troubleshooting.aspx


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On May 10, 1:33 am, David Wang <w3.4...@gmail.com> wrote:
> Sounds like you want to read this blog entry and read the extensive
> set of comments of what users have encountered that cause this issue
> -- all were problems outside of IIS6 and Windows:http://blogs.msdn.com/david.wang/archive/2005/09/21/HOWTO-Diagnose-II...
>
> I am going to speculate that Backup Exec or your Network card driver
> are to blame for your issue.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> //
>
> On May 9, 8:07 am, JT <J...@discussions.microsoft.com> wrote:
>
>
>
> > Hello,
>
> > I have II6 running on a new 2003 server with FrontPage extension installed.
> > That's all that is running on the box (Dell PE 2900) except for Backup Exec.
> > All patches up to date.
>
> > The server hums along fine for about 36 hours then simply stops serving.
> > Clients recieve page not available or connection reset depending on which
> > browser is used.
>
> > Simply stopping and restarting IIS doesn't fix the issue. I must reboot the
> > server.
>
> > I am now running the debug diagnostic tool in an attempt to capture any
> > hints as to what is the issue.
>
> > Anybody have experience with this? How can I fix?
>
> > There are no errors in the log files. Other than not serving, the server
> > seems to be fine.
> > --
> > JT- Hide quoted text -
>
> - Show quoted text -

JT
Thu May 10 07:09:00 CDT 2007

Thanks Justin and David.

I'm just serving static pages. I am using FrontPage extensions which
includes an ISAPI filter. The server stopped serving when I had debug
diagnostics running, I thought, but a dump was not captured. This may be
because I logged off the box, I now have it running with the server locked.

I will start reading the blogs to troubleshoot.

Thanks so much for your advice. I'll post the results of my troubleshooting.

JT


"David Wang" wrote:

> And you want to read this blog entry on how to start troubleshooting.
> You only need to look for a couple of log files to conclude where
> things are disconnected.
>
> http://blogs.msdn.com/david.wang/archive/2005/12/31/HOWTO_Basics_of_IIS6_Troubleshooting.aspx
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>
>
>
>
> On May 10, 1:33 am, David Wang <w3.4...@gmail.com> wrote:
> > Sounds like you want to read this blog entry and read the extensive
> > set of comments of what users have encountered that cause this issue
> > -- all were problems outside of IIS6 and Windows:http://blogs.msdn.com/david.wang/archive/2005/09/21/HOWTO-Diagnose-II...
> >
> > I am going to speculate that Backup Exec or your Network card driver
> > are to blame for your issue.
> >
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David.Wang
> > //
> >
> > On May 9, 8:07 am, JT <J...@discussions.microsoft.com> wrote:
> >
> >
> >
> > > Hello,
> >
> > > I have II6 running on a new 2003 server with FrontPage extension installed.
> > > That's all that is running on the box (Dell PE 2900) except for Backup Exec.
> > > All patches up to date.
> >
> > > The server hums along fine for about 36 hours then simply stops serving.
> > > Clients recieve page not available or connection reset depending on which
> > > browser is used.
> >
> > > Simply stopping and restarting IIS doesn't fix the issue. I must reboot the
> > > server.
> >
> > > I am now running the debug diagnostic tool in an attempt to capture any
> > > hints as to what is the issue.
> >
> > > Anybody have experience with this? How can I fix?
> >
> > > There are no errors in the log files. Other than not serving, the server
> > > seems to be fine.
> > > --
> > > JT- Hide quoted text -
> >
> > - Show quoted text -
>
>
>

JT
Thu May 10 15:06:03 CDT 2007


Hey David,

Poolmon indicates I have a memory leak in Ddk. I have searched but I am not
able to associate with a driver. Itis currently using 102347608 bytes and is
growing.

Any hints?

--
JT


"David Wang" wrote:

> Sounds like you want to read this blog entry and read the extensive
> set of comments of what users have encountered that cause this issue
> -- all were problems outside of IIS6 and Windows:
> http://blogs.msdn.com/david.wang/archive/2005/09/21/HOWTO-Diagnose-IIS6-failing-to-accept-connections-due-to-Connections-Refused.aspx
>
> I am going to speculate that Backup Exec or your Network card driver
> are to blame for your issue.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>
>
>
>
> On May 9, 8:07 am, JT <J...@discussions.microsoft.com> wrote:
> > Hello,
> >
> > I have II6 running on a new 2003 server with FrontPage extension installed.
> > That's all that is running on the box (Dell PE 2900) except for Backup Exec.
> > All patches up to date.
> >
> > The server hums along fine for about 36 hours then simply stops serving.
> > Clients recieve page not available or connection reset depending on which
> > browser is used.
> >
> > Simply stopping and restarting IIS doesn't fix the issue. I must reboot the
> > server.
> >
> > I am now running the debug diagnostic tool in an attempt to capture any
> > hints as to what is the issue.
> >
> > Anybody have experience with this? How can I fix?
> >
> > There are no errors in the log files. Other than not serving, the server
> > seems to be fine.
> > --
> > JT
>
>
>

David
Fri May 11 05:08:43 CDT 2007

It sounds like the driver writer used the DDK driver sample and forgot
to update it to identify their driver. Which makes your job harder.
Sorry, I have no magical hints.

Nothing leaks like that on default Windows installation and its
drivers -- they've all been stress tested to run 20+ days. I suggest
start looking at any backup, "agents" (i.e. IBM, Compaq/HP, Toshiba
have all had various "server agents" leak non-paged pool), security
(CA, Symantec, McAfee, etc), anti-virus, networking, sound card, etc
software -- basically, anything that remotely look like it runs a NT
service, a driver, or some other "notification service") installed on
your machine since Windows Server 2003 was installed -- then go
through process of elimination of each software package to determine
which driver is the cause.

Sorry, there may not be a "quick" solution here, but at least you know
what the problem is, how to monitor it, and it is a process of
elimination to determine the culprit from a handful of software
packages categories that I've listed.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On May 10, 1:06 pm, JT <J...@discussions.microsoft.com> wrote:
> Hey David,
>
> Poolmon indicates I have a memory leak in Ddk. I have searched but I am not
> able to associate with a driver. Itis currently using 102347608 bytes and is
> growing.
>
> Any hints?
>
> --
> JT
>
>
>
> "David Wang" wrote:
> > Sounds like you want to read this blog entry and read the extensive
> > set of comments of what users have encountered that cause this issue
> > -- all were problems outside of IIS6 and Windows:
> >http://blogs.msdn.com/david.wang/archive/2005/09/21/HOWTO-Diagnose-II...
>
> > I am going to speculate that Backup Exec or your Network card driver
> > are to blame for your issue.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //
>
> > On May 9, 8:07 am, JT <J...@discussions.microsoft.com> wrote:
> > > Hello,
>
> > > I have II6 running on a new 2003 server with FrontPage extension installed.
> > > That's all that is running on the box (Dell PE 2900) except for Backup Exec.
> > > All patches up to date.
>
> > > The server hums along fine for about 36 hours then simply stops serving.
> > > Clients recieve page not available or connection reset depending on which
> > > browser is used.
>
> > > Simply stopping and restarting IIS doesn't fix the issue. I must reboot the
> > > server.
>
> > > I am now running the debug diagnostic tool in an attempt to capture any
> > > hints as to what is the issue.
>
> > > Anybody have experience with this? How can I fix?
>
> > > There are no errors in the log files. Other than not serving, the server
> > > seems to be fine.
> > > --
> > > JT- Hide quoted text -
>
> - Show quoted text -