Server is being shutdown because fabric pool manager could not complete initial placement of users. Cause: This can happen if insufficient number of Front-Ends are available in the Pool. Resolution: Ensure that all the Front-Ends configured for this Pool are up and running. 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 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 ...
Server startup is being delayed because fabric pool manager is initializing. Cause: This is normal when Pool is bootstrapped ...