Hinweis
Für den Zugriff auf diese Seite ist eine Autorisierung erforderlich. Sie können versuchen, sich anzumelden oder das Verzeichnis zu wechseln.
Für den Zugriff auf diese Seite ist eine Autorisierung erforderlich. Sie können versuchen, das Verzeichnis zu wechseln.
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.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-IIS-WMSVC |
The worker process for app pool '%1', PID='%2', failed to initialize the http.sys communication when asked to start processing http requests and therefore will be considered ill by W3SVC and terminated. The data field contains the error number. | |
Microsoft-Windows-IIS-WMSVC |
The worker process failed to initialize correctly and therefore could not be started. The data is the error. | |
Microsoft-Windows-IIS-W3SVC-WP |
The worker process failed to load the process model host. If this was during the launch of a queue the W3SVC will consider this worker process ill. The data is the error. | |
Microsoft-Windows-IIS-W3SVC-WP |
The worker process failed to start http request processing. A previous event log message may contain more information. The data is the error. | |
Microsoft-Windows-IIS-W3SVC-WP |
The worker process failed to start servering a queue for protocol %1. The data is the error. | |
Microsoft-Windows-IIS-WMSVC |
The Module DLL %1 failed to load. The data is the error. | |
Microsoft-Windows-IIS-WMSVC |
The worker process failed to initialize communication with the W3SVC and therefore could not be started. The data is the error. | |
Microsoft-Windows-IIS-WMSVC |
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 https://go.microsoft.com/fwlink/?LinkId=29349. | |
Microsoft-Windows-IIS-W3SVC-WP |
The worker process failed to pre-load .Net Runtime version %1. | |
Microsoft-Windows-IIS-W3SVC-WP |
The worker process cannot access the CLR configuration file at '%1'. Verify that the file exists and that the worker process has read access to the file. | |
Microsoft-Windows-IIS-W3SVC-WP |
There was an error during application preload for configuration path '%1'. The error will be ignored. The data is the error. | |
Microsoft-Windows-IIS-W3SVC-WP |
There was an error during application preload for configuration path '%1'. The worker process will be marked unhealthy and will be shutdown. The data is the error. | |
Microsoft-Windows-IIS-W3SVC-WP |
There was an unexpected error during application preload for application pool: '%1'. Some application preloads may not have been processed correctly. Please check the configuration for preload for the application(s) assigned to this application pool. The data is the error. | |
Microsoft-Windows-IIS-W3SVC-WP |
There was an unexpected error during the loading of managed runtime version '%1'. The managed runtime loader '%2' was unable to load the managed runtime. The data is the error. | |
Microsoft-Windows-WAS |
The Windows Process Activation Service failed to create a worker process for the application pool '%1'. The data field contains the error number. | |
Microsoft-Windows-WAS |
The Windows Process Activation Service failed to add the worker process '%1' to the job object representing application pool '%2'. The data field contains the error number. | |
Microsoft-Windows-WAS |
Windows Process Activation Service encountered an error trying to track worker process '%1' that belongs to app pool '%2'. This will result in this worker process not showing up in global queries enumerating all worker processes. It will also disable clients from being able to directly create a WORKER_PROCESS object to monitor this worker process. A client can see find this worker process by querying all worker processes in the app pool that this process belongs to. The data field contains the error number. |