Server startup is being delayed because fabric pool manager is initializing. Cause: This is normal when Pool is bootstrapped and indicates that the Front-End is waiting for a quorum of other Front-Ends to be started. Resolution: If this event recurs persistently, 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 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 ...
Server with the fully qualified domain name (FQDN) "{0}" has OrdinalInCluster "{1}", which exceeds the limit for servers ...
Server with the fully qualified domain name (FQDN) "{0}" requires NetInterfaceId "{1}" for NetPortId "{2}" defined within ...
Server-wide concurrent subscription limit reached. 30 subscriptions were rejected in the past 30 minutes. Maximum subscription ...
Service "{0}" is running and cannot pick up the change to unrestricted service identifier type until you restart the service. ...