Server is being shutdown because fabric pool manager could not be initialized. Cause: This could happen because insufficient number of Front-Ends are currently active in the Pool. Resolution: Ensure that 85% of the Front-Ends configured for this Pool are up and running. For 2 or 3 machine Pools, initial cold-start of the Pool requires all machines to be started. If multiple Front-Ends have been recently decommissioned, run Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery to enable the Pool to recover from Quorum Loss and make progress.
Server could not find the upgrade version for back-end. Version missing database "%1" using the connection string of %2. ...
Server could not register with the back-end since a version mismatch was detected. Version mismatch database "%1" using the ...
Server could not register with the back-end since a version mismatch was detected. Version mismatch database "%1" using the ...
Server did not present a certificate during TLS negotiation. The process %1 did not receive a certificate from the server. ...
Server is being shutdown because fabric pool manager could not be initialized. Cause: This could happen because insufficient ...
Server is being shutdown because fabric pool manager could not complete initial placement of users. Cause: This can happen ...
Server is being started for the first time and is preparing the database for use. This could take a while depending on the ...
Server is waiting for the first run of user replicator task to complete. This could take a while depending on the network ...
Server startup is being delayed because fabric pool manager has not finished initial placement of users. Currently waiting ...