Windows Process Activation Service (WAS) did not register protocol %1, because WAS cannot register a protocol when there are listener channels from a previous listener adapter connection for the protocol. This may occur because you have worker processes running under debuggers and because orphaning may not be turned on. In this condition, WAS can detect the stop of a listener adapter, but it cannot kill the processes that contain listener channels. For this reason, WAS must wait for an admin to end these processes before a new listener adapter can connect. The data field contains the error number.
Windows PowerShell updated your execution policy successfully, but the setting is overridden by a policy defined at a more ...
Windows Process Activation Service (WAS) did not create a relationship between protocol %1 and application %2, which belongs ...
Windows Process Activation Service (WAS) did not notify protocol %1 to enable request processing. Requests made to this protocol ...
Windows Process Activation Service (WAS) did not process changes that affect supported protocols for site %1. The site will ...
Windows Process Activation Service (WAS) did not register protocol %1, because WAS cannot register a protocol when there ...
Windows Process Activation Service (WAS) did not run the automatic shutdown executable %2 for application pool %1. The data ...
Windows Process Activation Service (WAS) did not send a request to protocol %1 to remove configuration for application %3 ...
Windows Process Activation Service (WAS) disabled protocol %1 because the protocol was unable to acknowledge a change in ...
Windows Process Activation Service (WAS) disabled protocol %1 because WAS received bad data about the protocol. To re-enable ...