| Event Id | 5101 |
| Source | Microsoft-Windows-WAS |
| Description | The Windows Process Activation Service (WAS) did not create application pool %1. The data field contains the error number. |
| Event Information | According to Microsoft : Cause : This event is logged when Windows Process Activation Service (WAS) did not create application pool. Resolution : Stop and restart WAS Stopping the WAS service will also stop the World Wide Web Publishing Service (W3SVC) and any other services that depend on WAS. Thus, you may also have to start these other services. To perform this procedure, you must have membership in Administrators , or you must have been delegated the appropriate authority. To stop and restart WAS: 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.At the command prompt, type net stop was /y . 3.At the command prompt, type net start was . 4.To restart W3SVC, from the command prompt, type net start w3svc . Also, start any other services that were stopped when WAS was shut down. Verify : 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 has started: 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, expand the server node and select Application Pools . 4.In Features View , the Status column for the application pool will indicate Started if the application pool has started. |
| Reference Links | Event ID 5101 from Microsoft-Windows-WAS |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.