Event ID 2282 — IIS Worker Process Availability
Applies To: Windows Server 2008 R2
Internet Information Services (IIS) worker processes serve an application pool and can be in a starting, running, stopping, or unknown state. In IIS 7.0 and IIS 7.5, worker processes are managed by WAS (the Windows Process Activation Service). If a worker process fails to respond, it may be recycled by WAS.
|Product:||Internet Information Services|
|Message:||The Module DLL '%1' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a %2 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.|
Correct module DLL load failure
If a module DLL fails to load, possible resolutions include the following:
- If the module is third-party, contact the module vendor. The vendor should have more specific knowledge about the module's features and behavior.
- If the module failed to load because of a processor mismatch, see Knowledge Base article 894435.
- Check the event log message for a specific error number that may provide more information. This error number will be different from the Event ID. To do this, perform the following steps.
To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.
Check for a specific error number
To check for a specific error number:
- In the Event Viewer, select the event that you received.
- Click the Details tab, then Friendly View.
- If a specific error number is available, the words Binary data should appear.
- Below In Words, note the number after the colon.
Find out more about a specific error number
To learn more about a specific error number:
- Download the Err.exe utility from the Microsoft Exchange Server Error Code Look-up page.
- Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- At the command prompt, navigate to the directory where you downloaded Err.exe. For example, if you downloaded Err.exe to C:\Err, type cd C:\Err.
- Type err errornumber to obtain more information about the error. For example, if the specific error number is 80070005, type err 80070005.
- In the example in Step 4, the error resolves to ERROR_ACCESS_DENIED, so your next step would be to check permissions on the module.
You can use a browser client and IIS Manager to verify that an application pool worker process has started.
Note: An IIS worker process does not exist until a request is made to the application pool for the Web application. For this reason, you may have to test browse the Web application before you can verify that a worker process is functional.
Test browse the application
To test browse the application:
- Open up your default browser or required client.
- Browse to the Web site or application whose worker process you want to test. The client should display the expected output page.
Verify that an application pool worker process is running
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To verify that an application pool worker process is running:
- 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, select the computer name.
- In Features View, under the Feature Name column heading, double-click the Worker Processes management feature. A list of currently active application pools and worker processes will appear.
- The State column for the worker process will indicate Running if the worker process is running.
- You can also view currently executing requests by right-clicking the application pool name or worker process id and selecting View Current Requests.