Windows Process Activation Service (WAS) was unable to determine the security identifier (SID) for the worker process identity in application pool %1. WAS will be unable to provide the correct identity to listener adapters, which may prevent the worker process or processes in the application pool from processing requests for this protocol. To resolve this issue, change the worker process identity to a new identity and then change it back to the previous identity. The data field contains the error number.
Windows Process Activation Service (WAS) disabled protocol %1 because WAS received bad data about the protocol. To re-enable ...
Windows Process Activation Service (WAS) encountered an error trying to determine the correct security identifier (SID) for ...
Windows Process Activation Service (WAS) is disabling protocol %1 because the protocol was unable to acknowledge a change ...
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 ...