Security: The server was unable to read the file due a to lack of access permissions.

Security__The_server_was_unable_to_read_the_file_due_a_to_lack_of_access_permissions__6_Rule.Monitor (UnitMonitor)

Knowledge Base article:

Summary

The IIS Server could not read a file with the account it is running with.

Causes

The Server tried to read a file which has permissions not allowing access.

Resolutions

You can set Web permissions for specific Web sites, folders, and files on your server. Unlike the NTFS file system permissions that apply only to either a specific user or a group of users who have a valid Windows account, Web permissions apply to all users who access your Web site regardless of their specific access rights. NTFS permissions control access to physical directories on your server, whereas Web permissions control access to virtual directories on your Web site.

For example, you can use Web permissions to control whether visitors to your Web site can view a particular Web page, upload information, or run scripts. When you configure both Web permissions and NTFS permissions, you can control how users access your Web content on several levels, from the whole Web site to individual files.

Configure Web Server Permissions for Web Content

To configure Web server permissions for Web content, follow these steps:

1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

2. Expand ServerName, where ServerName is the name of the server, and then expand Web Sites.

3. Right-click the Web site, the virtual directory, the folder, or the file that you want to set permissions for, and then click Properties.

4. Click one of the following tabs, as appropriate to your situation:

5. Either click to select or click to clear any of the following check boxes (if present) that are appropriate for the level of Web permissions that you want to set:

6. In the Execute Permissions box, click the option that you want to determine how scripts run on the site. The following options are available:

7. Click OK, and then quit the IIS snap-in.

Notes:

When both Web permissions and NTFS permissions are set, the permissions that explicitly deny access take precedence over permissions that grant access.

Additional

For more information about how to configure Web server and NTFS permissions for Web content, see the "Access Control" topic in the "Security" section of the Server Administrator Guide in the IIS 6.0 Online Documentation. To view the IIS 6.0 Online Documentation, visit the following Microsoft Web site:

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/server/iiswelcome.asp

Element properties:

TargetMicrosoft.Windows.InternetInformationServices.2003.WebServer
Parent MonitorSystem.Health.ConfigurationState
CategoryStateCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityLow
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.SingleEventLogManualReset2StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Security The server was unable to read the file due a to lack of access permissions
{0}
RunAsDefault
CommentMom2005ID='{C81E7739-CF7C-468E-8E11-763555CE7052}'

Source Code:

<UnitMonitor ID="Security__The_server_was_unable_to_read_the_file_due_a_to_lack_of_access_permissions__6_Rule.Monitor" Comment="Mom2005ID='{C81E7739-CF7C-468E-8E11-763555CE7052}'" Accessibility="Public" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.InternetInformationServices.2003.WebServer" ParentMonitorID="SystemHealth!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.SingleEventLogManualReset2StateMonitorType" ConfirmDelivery="false">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="Security__The_server_was_unable_to_read_the_file_due_a_to_lack_of_access_permissions__6_Rule.Monitor.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Low</AlertPriority>
<AlertSeverity>Warning</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/EventDescription$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="ManualReset" MonitorTypeStateID="ManualResetEventRaised" HealthState="Success"/>
<OperationalState ID="ConfigError" MonitorTypeStateID="EventRaised" HealthState="Warning"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>W3SVC</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>2226</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</Configuration>
</UnitMonitor>