Failed to update pool state in backup database. Pool: %1. State: %2. Era: %3. Execution Error: %4. Native Error: %5. Error Details: %6. Cause: This may indicate a problem with connectivity to backup database or some unknown product issue. Resolution: Ensure that connectivity to backup database is proper. If the error persists, please contact product support with server traces.
Failed to suspend sync from blob store. Cause: This may indicate a problem with connectivity to local or backup database ...
Failed to sync data for Routing group %1 from backup store. Cause: This may indicate a problem with connectivity to backup ...
Failed to synchronize remote domain %1 due to missing data privacy boundary for local or remote domain. Source of replication ...
Failed to update Mcu health in the backend. This will be retried but if this continues to occur conferencing functionality ...
Failed to update pool state in backup database. Pool: %1. State: %2. Era: %3. Execution Error: %4. Native Error: %5. Error ...
Failed to update pool state in local database. Pool: %1. State: %2. Era: %3. Execution Error: %4. Native Error: %5. Error ...
Failed to update source pool during move. User: %1. Execution Error: %2. Native Error: %3. Error Details: %4. Cause: This ...
Failed to update the Archiving purge settings in the Archiving database. Component: %1 Error: %2 Cause: Configuration issues ...
Failed to update the auto attendant state for Exchange UM contact. Use Set-CsExUmContact cmdlet to fix the auto attendant ...