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.
Windows Process Activation Service (WAS) is stopping because it encountered an error. The data field contains the error number. ...
Windows Process Activation Service (WAS) was unable to determine the security identifier (SID) for the worker process identity ...
Windows Process Activation Service (WAS) was unable to notify protocol %2 about an identity change for application pool %1. ...
Windows Process Activation Service (WAS) was unable to register protocol %1. The listener adapter for protocol %1 may not ...
Windows Process Activation Service encountered an error trying to track worker process '%1' that belongs to app pool '%2'. ...
Windows Process Activation Service failed to create the internal protocol app pool object for app pool '%1' and protocol ...
Windows Process Activation Service generalizes the IIS process model, removing the dependency on HTTP. All the features of ...
Windows Process Activation Service listens for messages on behalf of Windows Communication Foundation (WCF) services and ...
Windows Process Activation Service Support enables Application Server to invoke applications remotely over the network using ...