Share via

Event ID 2286 — IIS Worker Process Tracing

  • Article

Applies To: Windows Server 2008 R2

In Internet Information Services (IIS) versions 7.0 and 7.5, worker processes can trace request activity. Of the requests that reach the worker process, you can log successful requests, failed requests, or all requests. In order to log this information, the worker process identity must have permissions to create directories and subdirectories, and to write files to the directory configured for the site.

Event Details

Product: Internet Information Services
ID: 2286
Source: Microsoft-Windows-IIS-W3SVC-WP
Version: 7.5
Symbolic Name: W3_EVENT_INVALID_FREB_CONFIGURATION_STATUS
Message: FailedRequestTracing module detected invalid configuration on path '%4'. Attribute "statusCode" contains invalid value '%3'. Examples of valid status are '404' or '403.1'. No logs will be generated until this condition is corrected. The problem happened at least %1 times in the last %2 minutes. The data is the error.

Resolve

Correct failed request tracing configuration

Possible corrections to failed request tracing include the following:

  • Correct your configuration to use one or more of the trace providers that are defined in the traceProviderDefinitions section of the ApplicationHost.config file.

  • Make sure that the trace provider Areas are mapped in compliance with the traceProviderDefinitions section.

  • Correct an invalid section that may have been defined in the traceFailedRequests section.

  • Correct an invalid statusCodes attribute in the failureDefinitions section of the ApplicationHost.config file.

  • For detailed information about how to find the traceFailedRequests and traceProviderDefinitions sections in the ApplicationHost.config file, see the section titled "Find the tracing section in ApplicationHost.config”.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Find the tracing section in ApplicationHost.config

To find the tracing section in the ApplicationHost.config file:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type cd %Windir%\system32\inetsrv\config
  3. Type notepad ApplicationHost.config
  4. In notepad, search for the tracing section under system.webServer.
  5. The traceFailedRequests and traceProviderDefinitions sections are located under the tracing section.

See Also

Verify

Tracing lets you diagnose and troubleshoot Web applications. Failed Request Tracing buffers trace events for a request and only flushes them to disk if the request falls into a user-configured error condition. The failed request tracing feature is a Web Server Role Service that can be installed through Server Manager. If the role service is installed, the Failed Request Tracing Module will be available by default for the Web sites and applications on the server.

  • To create a test trace to verify that the Failed Request Tracing Module is working, see the article Troubleshooting Failed Requests using Tracing in IIS7.
  • To verify that the Failed Request Tracing Module is installed, see the following information in section A.
  • To install the Trace Role Service in Server Manager, see the following information in section B.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

A. Verify that the Failed Request Tracing Module is installed

To verify that the Failed Request Tracing Module is installed:

  1. Click Start, click Control Panel, and then click Administrative Tools.
  2. Right-click Internet Information Services (IIS) Manager and select Run as administrator.
  3. In the Connections pane, click the + sign by the Web server name to expand the tree beneath.
  4. Click the Sites folder.
  5. Double-click the name of the Web site for which you want to verify that failed request tracing is installed. The title of the middle pane changes to websitename Home, where websitename is the name of the site that you selected.
  6. Under the Feature Name column, double-click the Modules icon. The Modules pane appears with a list of installed modules.
  7. Find FailedRequestsTracingModule in the list. If it appears in the list, failed request tracing is available for the site.
  8. If the module does not appear in the list, click the server name in the Connections pane, then double-click the Modules icon in Features View. The name FailedRequestsTracingModule should appear in the list.
  9. If the module does not appear in the modules list at the server level, you will have to install the Tracing Role Service in Server Manager. 

B. Install the Tracing Role Service in Server Manager

To install the Tracing Role Service in Server Manager:

  1. Click Start and select Administrative Tools.

  2. Right-click Server Manager and click Run as administrator.

  3. In Server Manager, click Roles.

  4. In the Role Service column, find Web Server, then look for Health and Diagnostics.

  5. Under Health and Diagnostics, look for Tracing.

  6. Look under the Status column for the tracing status.

  7. If the tracing status is Not installed, then click Add Role Services.

  8. Under Health and Diagnostics, select the Tracing check box.

  9. Click Next.

  10. Click Install. After several moments, the Installation succeeded message should appear.

  11. Click Close to close the Add Role Services window.

    Note:   Installing health and diagnostics tracing in this manner enables support for both ETW tracing and Failed Request Tracing for IIS.

For more information about Failed Request Tracing, see the article Troubleshooting Failed Requests using Tracing in IIS7.

IIS Worker Process Tracing

Internet Information Services (IIS) 7.5