Exchange Server 2016
- Exchange had to force the configuration update for %1 %2 time(s). This might indicate a problem with Active Directory notifications. ...
- Exchange has added the string "ncacn_HTTP:6004" to the following registry key entry: HKEY_LOCAL_MACHINE\System\CurrentCo ...
- Exchange has detected an inconsistency in the Active Directory configuration for the following virtual directories. This ...
- Exchange has detected an inconsistency in the Active Directory configuration for the following virtual directories. This ...
- Exchange Health Manager scheduling latency has been above 100ms since '{Monitor.FirstAlertObservedTime}'. Sustained high ...
- Exchange Hosted Filtering administation synchronization operation failed due to a permanent error in the EHF Adminsync service. ...
- Exchange Hosted Filtering administation synchronization operation failed due to a transient error in the EHF Adminsync service. ...
- Exchange Hosted Filtering provisioning operation failed because invalid credentials were supplied to EHF. Please verify Edge ...
- Exchange Hosted Filtering provisioning operation failed due to a transient error in the EHF provisioning system. The current ...
- Exchange Information Store is inaccessible. Make sure that the network is connected and that the Exchange Information Store ...
- Exchange Information Store on server '{0}' is inaccessible. Make sure that the network is connected and that the Exchange ...
- Exchange Installable File System (IFS) path is not excluded from real-time scanning on server {2}. This may cause corruption ...
- Exchange isn't able to check for public folder replicas for "{0}". Verify that the Microsoft Information Store service is ...
- Exchange isn't supported on machines whose Computer Names contain non-standard characters. Please change your machine name, ...
- Exchange mailbox server {2} has 1 GB or more of memory, accommodates {9} mailboxes, and does not have /3GB set in the Boot.ini ...
- Exchange object '{1}' of class '{0}' was found in the 'LostAndFoundConfig' container. Reliability problems may occur if attempts ...
- Exchange object '{3}' of class '{1}' was found in the '{4}' container. Reliability problems may occur if attempts to access ...
- Exchange Online error: the action '{1}', '{2}', can't be performed without an Exchange Online subscription containing this ...
- Exchange online notification client is initialized. The Psws host url is '{0}'; the sync service url is '{1}'; the credential ...
- Exchange Online Protection error: the action '{1}', '{2}', can't be performed without an Exchange Online subscription containing ...
- Exchange Online Protection error: the action '{1}', '{2}', can't be performed without an Exchange Online subscription containing ...
- Exchange organization name is required for this mode. To specify an organization name, use the /OrganizationName parameter. ...
- Exchange organization-level objects either have not been created, or have not replicated to the local domain, but the schema ...
- Exchange organization-level objects have been created but have not yet replicated to the local domain. Wait for replication ...
- Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not ...
- Exchange provider tracing is enabled on server {2}. This should be enabled only when troubleshooting problems. You can disable ...
- Exchange Replication Service VSS Writer failed restoring a backup because a prohibited attempt was made to add additional ...
- Exchange Replication Service VSS Writer failed restoring a backup because an illegal attempt was made to add additional restores ...
- Exchange Replication Service VSS Writer failed restoring a backup because circular logging is enabled, either in the backup ...
- Exchange Replication Service VSS Writer failed restoring a backup because of a target database location mismatch. The file ...
- Exchange Replication Service VSS Writer failed restoring a backup because the backup set to be restored has an invalid version ...
- Exchange Replication Service VSS Writer failed restoring a backup because the backup set to be restored is missing a version ...
- Exchange Replication Service VSS Writer failed restoring a backup because the base name ('%1') of the logfiles in the backup ...
- Exchange Replication Service VSS Writer failed restoring a backup because the database '%1' in '%2' of database '%3' is targeted ...
- Exchange Replication Service VSS Writer failed restoring a backup because the file '%1' in '%2' specified for re-targetting ...
- Exchange Replication Service VSS Writer failed restoring a backup because the file '%1' in '%2' was incorrectly re-targeted ...
- Exchange Replication Service VSS Writer failed restoring a backup because the logfile base name ('%1') in the backup set ...
- Exchange Replication Service VSS Writer failed restoring a backup because the logfile path ('%1') specified for re-targetting ...
- Exchange Replication Service VSS Writer failed restoring a backup because the Restore Options string contains a database ...
- Exchange Replication Service VSS Writer failed restoring a backup because the signature (%1-%2) of the log files in the backup ...
- Exchange Replication Service VSS Writer failed restoring a backup because the system path ('%1') specified for re-targetting ...
- Exchange Replication Service VSS Writer failed restoring a backup because the target database GUID ('%1') does not match ...
- Exchange Replication Service VSS Writer failed restoring a backup because the target log file path ('%1') does not match ...
- Exchange Replication Service VSS Writer failed restoring a backup because the target log file path ('%1') specified for restore ...
- Exchange Replication Service VSS Writer failed restoring a backup because the target system path ('%1') does not match the ...
- Exchange Replication Service VSS Writer failed restoring a backup because the target system path ('%1') specified for restore ...
- Exchange Replication Service VSS Writer failed restoring a backup for '%1' because an unexpected error (%3) was encountered ...
- Exchange Replication Service VSS Writer failed restoring a backup to '%1' because another backup is already in the process ...
- Exchange Replication Service VSS Writer failed restoring a backup to an alternate location because the target log file path ...
- Exchange Replication Service VSS Writer failed restoring a backup to database '%1' because another backup is already in the ...
- Exchange Replication Service VSS Writer failed retrieving information for the database '%1' / '%2' from the Active Directory. ...
- Exchange Replication Service VSS Writer failed to delete the restore environment document '%1' after successfully running ...
- Exchange Replication Service VSS Writer failed to delete the transaction log file '%1' in '%2' after successfully running ...
- Exchange Replication Service VSS Writer failed with error code %2 when attempting to delete the checkpoint file %1. Delete ...
- Exchange Replication Service VSS Writer successfully completed the restore for '%1'. Database recovery will not be run because ...
- Exchange Replication Service VSS Writer successfully completed the restore for '%1'. Database recovery will not be run because ...
- Exchange Replication Service VSS Writer successfully restored the backup set. In order to bring the restored databases to ...
- Exchange Replication Service VSS Writer will perform database recovery on database '%2' as part of the restore process for ...
- Exchange Replication Service VSS Writer will restore a backup set to database '%1', which is a different database than the ...
- Exchange Replication Service VSS Writer will restore a backup set to database '%1', which is the same database from which ...
- Exchange server "{0}" can't be licensed with this 32-bit trial edition. Use a 64-bit edition to license production servers. ...
- Exchange server "{0}" is neither a Hub Transport server nor an Edge Transport server. This operation can only be run on servers ...
- Exchange server '{0}' is running on a 32-bit version of the Windows operating system. The 32-bit version of Exchange 2007 ...
- Exchange server '{2}' is running on a 32-bit version of the Windows operating system. The 32-bit version of Exchange 2007 ...
- Exchange Server 2003 can be configured to run without the Microsoft Exchange MTA Stacks service. In this configuration, if ...
- Exchange Server 2003 is not installed in the default program files folder on server {2}. Exchange install path is {5}. If ...
- Exchange Server 2013 isn't installed on this computer. Install Exchange Server 2013 before installing the language resources. ...
- Exchange Server 2016 can't be installed on a server that has an Exchange Server 2007 or Exchange Server 2010 role installed. ...
- Exchange Server 2016 is already installed on this server. You can't change your organization's Customer Experience Improvement ...
- Exchange Server 2016 requires .NET Framework 4.5 or later. Download it from http://go.microsoft.com/fwlink/?LinkId=260991. ...
- Exchange Server 2016 requires Windows Management Framework 3.0. You can download Windows Management Framework 3.0 from h ...
- Exchange Server Alert: Event Assistant Dispatchers Catchup Queue for database {0} has been over the threshold of {1} for ...
- Exchange Server Alert: Event Assistant Dispatchers Catchup Queue has been over the threshold of {0} for at least last {1}. ...
- Exchange Server Alert: Event Assistant Dispatchers Catchup Queue has been over the threshold of {0} for at least last {1}. ...
- Exchange Server Alert: High version store usage detected for at least last {0}. Last Reported Database: {Probe.StateAttribute1} ...