HELP - w3svc crash/is stopping

Discussion:

(too old to reply)

Anders

2004-09-14 08:28:39 UTC

Hi all,

The problem I have with my IIS4 on my NT4 SP6a (with all the latest patches
from Microsoft) server is:

* The w3svc (World Wide Wed Publishing Service) service either
stops/crash or is stopping.
* If the service is stopped, I can just start the service either from my
XP computer or from the Service manager on my NT4 Server. But if the
w3svc service is in "Is stopping" mode then the only way to restart it is to
use the TaskMgr to End the inetinfo.exe process and then start the service
from the Service Mgr.

* I can't find any logs on why the w3svc service goes down.

I run OWA and our Intranet on my IIS server. After I have restarted the
w3svc service it works perfectly for about 1-2 days then it goes down again!
We do not have that much traffic on our server so I don't think that's the
problem.

If anybody have any ideas on what could be the problem I should appreciate
your suggestions.

PS. I have just downloaded the IISstate and all it needs and I will install
it ASAP.

Best Regards
Anders Raneland

David Wang [Msft]

2004-09-15 04:38:47 UTC

Permalink

Use IISState to gather information from the crash and we can go from there.
Anything else will be pure speculation, which won't help you resolve the
issue and can obscure/corrupt the real issue.

Do you regularly start/stop/recycle IIS on this machine? Because a crash
would just kill the process instantly (so it won't get to the "is stopping"
state) -- but if you manually tried to stop IIS, it can get stuck in "is
stopping" state.

Also, regularly recycling IIS can cause metabase corruption, which may lead
to your server failing to start in the future.

Best advice is to take regular known-good backups of the IIS configuration
file ( %windir%\System32\inetsrv\metabase.bin ). If it does get corrupted,
you can just copy the backup and be ready to go.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Anders" <***@1nospam2connectBlue.se> wrote in message news:***@tk2msftngp13.phx.gbl...
Hi all,

The problem I have with my IIS4 on my NT4 SP6a (with all the latest patches
from Microsoft) server is:

* The w3svc (World Wide Wed Publishing Service) service either
stops/crash or is stopping.
* If the service is stopped, I can just start the service either from my
XP computer or from the Service manager on my NT4 Server. But if the
w3svc service is in "Is stopping" mode then the only way to restart it is to
use the TaskMgr to End the inetinfo.exe process and then start the service
from the Service Mgr.

* I can't find any logs on why the w3svc service goes down.

I run OWA and our Intranet on my IIS server. After I have restarted the
w3svc service it works perfectly for about 1-2 days then it goes down again!
We do not have that much traffic on our server so I don't think that's the
problem.

If anybody have any ideas on what could be the problem I should appreciate
your suggestions.

PS. I have just downloaded the IISstate and all it needs and I will install
it ASAP.

Best Regards
Anders Raneland

Anders

2004-09-15 10:35:13 UTC

Permalink

Hi David,

Thank you very much for taking the time to help me!

I will install the IISState today, because the sever that IIS is running on
is so much more than just a web server. I do not want to work with my
servers under working hours if it's not absolute necessary.

Answers:
1. I don't regularly start/stop/pause the w3svc service, I only start it if
it has gone down. I never stop any of my services manually.

2. When the w3svc service is in "is stopping" mode I can't do anything else
than either restart the hole server and end the Inetinfo.exe process and
then start it again. It is not I who have tried to stop the service when it
is in "is stopping mode", usually it has happen during the nights.

I appreciate your tip on the metabase backup!
I already do that in my daily backup routines.

Should I just post the log file here when I have IISState installed?
When is the best time to try get a log that might help me solve the problem?
When the w3svc service has crashed/stopped or when the w3svc service is in
"is stopping" mode or when the w3svc service is running?

Best Regards

Anders

Post by David Wang [Msft]
Use IISState to gather information from the crash and we can go from there.
Anything else will be pure speculation, which won't help you resolve the
issue and can obscure/corrupt the real issue.
Do you regularly start/stop/recycle IIS on this machine? Because a crash
would just kill the process instantly (so it won't get to the "is stopping"
state) -- but if you manually tried to stop IIS, it can get stuck in "is
stopping" state.
Also, regularly recycling IIS can cause metabase corruption, which may lead
to your server failing to start in the future.
Best advice is to take regular known-good backups of the IIS configuration
file ( %windir%\System32\inetsrv\metabase.bin ). If it does get corrupted,
you can just copy the backup and be ready to go.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
Hi all,
The problem I have with my IIS4 on my NT4 SP6a (with all the latest patches
* The w3svc (World Wide Wed Publishing Service) service either
stops/crash or is stopping.
* If the service is stopped, I can just start the service either from my
XP computer or from the Service manager on my NT4 Server. But if the
w3svc service is in "Is stopping" mode then the only way to restart it is to
use the TaskMgr to End the inetinfo.exe process and then start the service
from the Service Mgr.
* I can't find any logs on why the w3svc service goes down.
I run OWA and our Intranet on my IIS server. After I have restarted the
w3svc service it works perfectly for about 1-2 days then it goes down again!
We do not have that much traffic on our server so I don't think that's the
problem.
If anybody have any ideas on what could be the problem I should appreciate
your suggestions.
PS. I have just downloaded the IISstate and all it needs and I will install
it ASAP.
Best Regards
Anders Raneland

David Wang [Msft]

2004-09-15 21:04:56 UTC

Permalink

You want to get a log when the problem is happening -- right before
inetinfo.exe crashes or hangs -- so that we can see what is going on that is
causing the crash.

You may not be regularly start/stop/pause the W3SVC service, but someone or
some process MUST be stopping IIS because you cannot get into the "is
stopping" state otherwise. You want to control that process since it can
cause problems. If you have a practice of recycling IIS during the
evenings, that may be a part of your problem.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Anders" <***@1nospam2connectBlue.se> wrote in message news:***@TK2MSFTNGP12.phx.gbl...

Hi David,

Thank you very much for taking the time to help me!

I will install the IISState today, because the sever that IIS is running on
is so much more than just a web server. I do not want to work with my
servers under working hours if it's not absolute necessary.

Answers:
1. I don't regularly start/stop/pause the w3svc service, I only start it if
it has gone down. I never stop any of my services manually.

2. When the w3svc service is in "is stopping" mode I can't do anything else
than either restart the hole server and end the Inetinfo.exe process and
then start it again. It is not I who have tried to stop the service when it
is in "is stopping mode", usually it has happen during the nights.

I appreciate your tip on the metabase backup!
I already do that in my daily backup routines.

Should I just post the log file here when I have IISState installed?
When is the best time to try get a log that might help me solve the problem?
When the w3svc service has crashed/stopped or when the w3svc service is in
"is stopping" mode or when the w3svc service is running?

Best Regards

Anders

Anders

2004-09-23 08:35:02 UTC

Permalink

Hi David,

Just want to let you know that I have installed the IISState and I'm waiting
for something to happen!
Just to keep you up-to-date.

Thanks again for all your help, so far!

Best Regards

Anders

Post by David Wang [Msft]
You want to get a log when the problem is happening -- right before
inetinfo.exe crashes or hangs -- so that we can see what is going on that is
causing the crash.
You may not be regularly start/stop/pause the W3SVC service, but someone or
some process MUST be stopping IIS because you cannot get into the "is
stopping" state otherwise. You want to control that process since it can
cause problems. If you have a practice of recycling IIS during the
evenings, that may be a part of your problem.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
Hi David,
Thank you very much for taking the time to help me!
I will install the IISState today, because the sever that IIS is running on
is so much more than just a web server. I do not want to work with my
servers under working hours if it's not absolute necessary.
1. I don't regularly start/stop/pause the w3svc service, I only start it if
it has gone down. I never stop any of my services manually.
2. When the w3svc service is in "is stopping" mode I can't do anything else
than either restart the hole server and end the Inetinfo.exe process and
then start it again. It is not I who have tried to stop the service when it
is in "is stopping mode", usually it has happen during the nights.
I appreciate your tip on the metabase backup!
I already do that in my daily backup routines.
Should I just post the log file here when I have IISState installed?
When is the best time to try get a log that might help me solve the problem?
When the w3svc service has crashed/stopped or when the w3svc service is in
"is stopping" mode or when the w3svc service is running?
Best Regards
Anders

Post by David Wang [Msft]
Use IISState to gather information from the crash and we can go from

there.

Post by David Wang [Msft]
Anything else will be pure speculation, which won't help you resolve the
issue and can obscure/corrupt the real issue.
Do you regularly start/stop/recycle IIS on this machine? Because a crash
would just kill the process instantly (so it won't get to the "is

stopping"

Post by David Wang [Msft]
state) -- but if you manually tried to stop IIS, it can get stuck in "is
stopping" state.
Also, regularly recycling IIS can cause metabase corruption, which may

lead

Post by David Wang [Msft]
to your server failing to start in the future.
Best advice is to take regular known-good backups of the IIS

configuration