Event ID 2298 — IIS W3SVC Module Configuration
Applies To: Windows Server 2008 R2
Internet Information Services (IIS) versions 7.0 and 7.5 enable developers to easily configure native and managed code modules that process requests made to the Web server. In order for worker processes to load them, the modules must be configured correctly. Proper module configuration requires that the module have a unique name, and a valid type or path. Managed modules can specify whether they should be invoked only for requests to ASP.NET applications or managed handlers. When specified, this setting can optimize performance.
|Product:||Internet Information Services|
|Message:||The globalModules list is empty. No requests can be served successfully.|
Define a global module
In order for IIS to be able to serve requests successfully, there must be at least one global module defined in the in the globalModules section in the ApplicationHost.config file. The module definition must have a unique name attribute for the module and an image attribute that specifies the file system path of the .dll file that contains the global module.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
Add a global module definition to ApplicationHost.config
To add a global module definition to ApplicationHost.config by using notepad:
- Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- Type cd %Windir%\system32\inetsrv\config
- Type notepad applicationHost.config
- In notepad, search for the globalModules section under the system.webServer section.
- Add a module entry that contains the name and image attributes. An example is shown in the following section.
- Save the ApplicationHost.config file, and exit notepad.
Sample Global Module Definition
For more information about the globalModules section, see IIS 7.0: add Element for globalModules (IIS Settings Schema).
You can use IIS Manager or Task Manager to verify that a module is functioning.
To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.
Verify that a module is running by using IIS Manager
To verify that a module is running by using IIS Manager:
- Click Start, click Control Panel, and then click Administrative Tools.
- Right-click Internet Information Services (IIS) Manager and select Run as administrator.
- In the Connections pane, expand the computer name.
- Expand Sites.
- Select the Web site that is hosting the module that you want to verify.
- In the Actions pane, click the link under Browse Web Site. If the Web page appears, the worker process is running.
Verify that a module is running by using Task Manager
To verify that a module is running by using Task Manager:
- Click Start, Run, type taskmgr, and press ENTER.
- Click the Processes tab. When the Web page that uses the module is loaded, the IIS worker process W3wp.exe will appear in the Image Name column.