IIS Routinely Crashes
rf926_at_hotmail.com
Date: 05/27/04
- Next message: Victor: "RE: RIS images on multiple servers"
- Previous message: Cobus: "Cant establish a Dialup on Win2003 server with a Duxbury ISDN Modem"
- In reply to: Aaron Lewis: "IIS Routinely Crashes"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 27 May 2004 01:08:30 -0700
http://support.microsoft.com/default.aspx?scid=kb;en-
us;290647&Product=winsvr2003
CAUSE
This issue may occur if you assign improper permissions to
the %SystemRoot%\Winnt\Sysvol folder or when you assign
improper groups to Bypass Traverse Checking User Rights
Assignment. Additionally, if the sysvol share permissions
are too restrictive, the issue will occur.
RESOLUTION
To resolve this issue:
Set the folder security permissions. To do so:
In Windows Explorer, right-click the %SystemRoot%
\Winnt\Sysvol folder, and then click Properties.
On the Security tab, clear the Allow inheritable
permissions from parent to propagate to this object check
box, and then make sure that the security settings match
the following:
Administrators: Full Control
Authenticated Users: Read, Read & Execute, and List Folder
Contents
Creator Owner: Nothing selected
Server Operators: Read, Read & Execute, and List Folder
Contents
System: Full Control
Click OK.
Right-click the %SystemRoot%\Winnt\Sysvol\Sysvol folder,
and then click Properties.
On the Security tab, select the Allow inheritable
permissions from parent to propagate to this object check
box, and then click OK.
Right-click the %SystemRoot%\Winnt\Sysvol\Sysvol\domain:
folder, and then click Properties.
On the Security tab, select the Allow inheritable
permissions from parent to propagate to this object check
box, and then click OK.
Right-click the %SystemRoot%
\Winnt\Sysvol\Sysvol\domain\Policies folder, and then
click Properties.
On the Security tab, clear the Allow inheritable
permissions from parent to propagate to this object check
box, and then make sure that the security settings match
the following:
Administrators: Full Control
Authenticated Users: Read, Read & Execute, and List Folder
Contents
Creator Owner: Nothing selected
Group Policy Creator Owners: Read, Read & Execute, List
Folder Contents, Modify, and Write
Server Operators: Read, Read & Execute, and List Folder
Contents
System: Full Control
Click OK.
For each file or folder that is located in the %SystemRoot%
\Winnt\Sysvol\Sysvol\domain\Policies folder, right-click
the file or folder, and then click Properties. On the
Security tab, select the Allow inheritable permissions
from parent to propagate to this object check box, and
then click OK.
Open Active Directory Users and Computers: Click Start,
click Programs, and then click Administrative Tools.
Expand Active Directory Users and Computers, and then
expand the domain name.
Right-click Domain Controllers, and then click Properties.
On the Group Policy tab, click Default Domain Controllers
Policy, and then click Edit.
Expand the folders:
Computer Configuration
Windows Settings
Security Settings
Local Policies
Click User Rights Assignment, and then double-click Bypass
traverse checking. The following default settings should
be present:
Authenticated Users
Everyone
Administrators
To add these groups if they are not present, click Add,
and then click Browse.
At a command prompt, type:
secedit /refreshpolicy machine_policy /enforce
Verify that the sysvol share permissions are set correctly.
Default Share permissions are:
Administrators = FC
Authenticated Users = FC
Everyone = Read
NOTE: If this procedure does not resolve the issue, or you
have problems accessing the Global Policy, check the
Bindings on the server to make sure the internal network
adapter is first in the binding order list. To check the
binding order, follow these steps:
Right-click My Network Places, and then clickProperties.
Click the Advanced Menu, and then click Advanced Settings.
Under Connections, make sure the internal network adapter
is listed first. If it is not, use the arrows to move it
to the top of the list.
>-----Original Message-----
>The following two "warnings" occur from 5-8 times a day,
and invariably result in a crashed IIS that stops
responding to requests. It's causing me to play the
iisreset monkey instead of focusing on the actual
software. It's standard ASP.NET 1.1 stuff, nothing
tricky.
>
>Event Type: Warning
>Event Source: W3SVC
>Event Category: None
>Event ID: 1011
>Date: 5/26/2004
>Time: 4:51:04 PM
>User: N/A
>Description:
>A process serving application pool 'DefaultAppPool'
suffered a fatal communication error with the World Wide
Web Publishing Service. The process id was '3692'. The
data field contains the error number.
>
>For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
>Data:
>0000: 8007006d
>
>
>Event Type: Warning
>Event Source: W3SVC
>Event Category: None
>Event ID: 1009
>Date: 5/26/2004
>Time: 4:51:05 PM
>User: N/A
>Description:
>A process serving application pool 'DefaultAppPool'
terminated unexpectedly. The process id was '3108'. The
process exit code was '0xc0000005'.
>
>For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
>
>.
>
- Next message: Victor: "RE: RIS images on multiple servers"
- Previous message: Cobus: "Cant establish a Dialup on Win2003 server with a Duxbury ISDN Modem"
- In reply to: Aaron Lewis: "IIS Routinely Crashes"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
