Failed to start kernel mode driver component. Cause: An IP address and/or listening ports may be configured incorrectly. Resolution: Verify that the computer has the IP addresses specified in the topology configuration. Determine whether any other application or service has already used the TCP/UDP ports specified in the topology configuration.
Failed to set the server role Role: '%1'. Resolution: Check the previous event log entries and resolve them. Restart the ...
Failed to start all critical applications Cause: One or more critical applications failed to register within the maximum ...
Failed to start Call Notification Queuing Engine. Failed to start Call Notification Queuing Engine. Exception Message: %1. ...
Failed to start kernel mode driver component Driver Name: %1 Exception: %2 Cause: Either invalid configuration or permission ...
Failed to start kernel mode driver component. Cause: An IP address and/or listening ports may be configured incorrectly. ...
Failed to stop kernel mode driver component Driver Name: %1 Exception: %2 Cause: Driver is not responding in a timely fashion. ...
Failed to update Mcu health in the backend. This will be retried but if this continues to occur conferencing functionality ...
Failed to update the auto attendant state for Exchange UM contact. Use Set-CsExUmContact cmdlet to fix the auto attendant ...
Failed to update the list of domains in this forest to synchronize. The error that occurred was %1 (%2) User Replicator has ...