Failed to start all critical applications Cause: One or more critical applications failed to register within the maximum ...

Failed to start all critical applications

Cause: One or more critical applications failed to register within the maximum allowable time, which is (60 + (30 * n)) seconds where n is the number of critical applications.
Resolution:
Examine the list of enabled critical applications via PowerShell (using Get-CSServerApplication cmdlet). Examine the event log entries before this one to determine which critical applications successfully registered with the server.  Those that did not register successfully with the server within the maximum allowable time are the ones causing this error.

Failed to send Http application request to service. Requests for this service will be retried but if this error continues ... Failed to set "{0}". Manually disable "{0}" to ensure that cluster fully qualified domain names (FQDNs) can authenticate ... Failed to set "{0}". Manually disable "{0}" to ensure that cluster fully qualified domain names (FQDNs) can authenticate ... 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. ...