Exchange Server 2016
- Exception %1 is within threshold in the last %2 minutes for Feature:PersonaCard, API: GetPersona and ClientAction: Perso ...
- Exception %1 is within threshold in the last %2 minutes for Feature:PersonaCard, API: GetPersona and ClientAction: PersonaCard_peopleHub. ...
- Exception %1 is within threshold in the last %2 minutes for Feature:PersonaCard, API: GetPersona and ClientAction: PersonaCard_readOnlyRecipientWell. ...
- Exception %1 is within threshold in the last %2 minutes for Feature:PersonaCard, API: GetPersona and ClientAction: PersonaCard_sharePoint. ...
- Exception %1 is within threshold in the last %2 minutes for Feature:ReadingPane, API: GetItem and ClientAction: GetMailItem. ...
- Exception occured when trying to write Lam Notification event at Stage: %1 for InternetMessageId: %2; MailboxGuid: %3; Exception ...
- Exception occured while parsing MessageItemSchema.MapiSubmitLamNotificationId on the message with InternetMessageId: %1; ...
- Exception occurred while trying to clear the "ForceDomainSync" flag in Perimeter Settings object for company %1. Failure ...
- Exception occurred while trying to clear the "ForceDomainSync" flag in Perimeter Settings object for domain %1. Failure details: ...
- Exchange 2016 Setup can't contact the update server right now. This could be because the update server is temporarily unavailable ...
- Exchange 2016 Setup has detected updates that were downloaded during a previous run of Setup. You can use these updates, ...
- Exchange ActiveSync device requests for your users are being blocked. This problem frequently occurs when the HTTP OPTIONS ...
- Exchange ActiveSync didn't upgrade from Exchange 2007 to Exchange 2010. The user {0} may have a poor user experience when ...
- Exchange ActiveSync doesn't have sufficient permissions to create the "%1" container under Active Directory user "%2". Make ...
- Exchange ActiveSync doesn't have sufficient permissions to create the object for device type "%1" ID "%2" under Active Directory ...
- Exchange ActiveSync enables access to a Microsoft Exchange mailbox from a mobile device. To configure Exchange ActiveSync, ...
- Exchange ActiveSync experienced a transient error when it tried to access Active Directory information for user "%1". Exchange ...
- Exchange ActiveSync experienced an error when it tried to perform an Active Directory operation for user "%1". If this event ...
- Exchange ActiveSync failed to find the Global Criminal Compliance (GCC) secret keys. Run InstallNewDatacenterSecretKey.ps1 ...
- Exchange ActiveSync failed to send e-mail informing administrators of quarantined mobile clients because no recipients have ...
- Exchange ActiveSync has been disabled for the user %1. It's possible the user's mailbox is in the process of being moved. ...
- Exchange ActiveSync has been loaded. This event is logged when Exchange ActiveSync receives its first sync request. The DLL ...
- Exchange ActiveSync has generated a fatal exception and has shut down. For more information, see the description below, which ...
- Exchange ActiveSync tracing is currently enabled on server {2}. This should be enabled only when troubleshooting problems. ...
- Exchange ActiveSync tried to access a mailbox on Mailbox server "%1". It could not access the mailbox because the Mailbox ...
- Exchange Admin Center is failing to respond to ping request on Mailbox server {0}.Availability has dropped to {Monitor.TotalValue}%. ...
- Exchange Admin Center logon is failing on Client Access Server {0}.Availability has dropped to {Monitor.TotalValue}%. You ...
- Exchange Admin Center logon is failing on Mailbox Server {0}.Availability has dropped to {Monitor.TotalValue}%. You can find ...
- Exchange can't connect to the Information Store service on server {0}. Make sure that the service is running and that there ...
- Exchange can't connect to the Microsoft Exchange Transport service on computer "{0}". Verify that the service is started. ...
- Exchange can't disable the mailbox "{0}" because it is set as JournalingReportNdrTo in the transport configuration. You can ...
- Exchange can't disable the mailbox "{0}" because one or more Offline Address Books are assigned to it for generation. Please ...
- Exchange can't remote the ApprovalApplication object, because there are still arbitration mailboxes that are associated with ...
- Exchange can't remove the mailbox "{0}" because it is set as JournalingReportNdrTo in the transport configuration. You can ...
- Exchange can't remove the mailbox "{0}" because it moderates one or more mailboxes. To find out which mailboxes are moderated ...
- Exchange can't remove the mailbox "{0}" because one or more Offline Address Books are assigned to it for generation. Please ...
- Exchange can't remove the public folder database {0} because it's the last public folder database in an organization that ...
- Exchange can't store database (.edb) files in the root directory. Choose another location. The specified file path is '{0}'. ...
- Exchange cluster node {2} is running Windows 2000 Server and does not have '{4}' set to {8}. This can cause cluster communication ...
- Exchange cluster node {2} is running Windows Server 2003 and does not have '{4}' set to {8}. A value of 0 is recommended ...
- Exchange cluster node {2} is using storage driver '{1}' which is not StorPort Miniport-compatible. For additional performance ...
- Exchange cluster {2} is running Exchange 2000 Server and Kerberos is enabled for the network name resource. This configuration ...
- Exchange cluster {2} is running Exchange Server 2003 and Kerberos is disabled for the network name resource. This configuration ...
- Exchange could not create the folder "Managed Folders" in mailbox {0}. The mailbox was not processed by the managed folder ...
- Exchange couldn't find any usable connections to the Active Directory server {0}. Take a look at the event logs, and try ...
- Exchange couldn't find the accepted domain "{0}". You must use one of the configured accepted domains. Please make sure you ...
- Exchange couldn't get the information necessary to connect to Active Directory Lightweight Directory Services (AD LDS) instance ...
- Exchange couldn't load attachment filtering configuration on startup. Use the Get-AttachmentFilterEntry cmdlet to verify ...
- Exchange couldn't open the database because it can't find a file. The Microsoft Exchange Transport service is shutting down. ...
- Exchange couldn't open the database because it can't find a table. The Microsoft Exchange Transport service is shutting down. ...
- Exchange couldn't open the database because the drive of %1 is not accessible. Invalid setting for the database path or Bitlocker ...
- Exchange data files and the page file are located on drive {4}. This may not be an issue if there is no disk bottleneck on ...
- Exchange data files and the Windows system partition is located on drive {4}. This may not be an issue if there is no disk ...
- Exchange detected that "%1" is not the correct version required to run Exchange System Manager or Exchange Server 2003. This ...
- Exchange detected that "%s" is not the correct version required to run Exchange System Manager or Exchange Server 2003. This ...
- Exchange detected the server '{0}' in the organization, but couldn't determine the server version. You may encounter compatibility ...
- Exchange Development Kit (EDK) connector '{3}' was found in the organization. Exchange Server 2007 does not support EDK connectors. ...
- Exchange Diagnostics Service (EDS) passive monitoring is reporting that {Probe.MachineName} is experiencing a high Admin ...
- Exchange Diagnostics Service (EDS) passive monitoring is reporting that {Probe.MachineName} is experiencing a high failure ...
- Exchange Diagnostics Service (EDS) passive monitoring is reporting that {Probe.MachineName} is experiencing a high latency ...
- Exchange Diagnostics Service (EDS) passive monitoring is reporting that {Probe.MachineName} is experiencing a high Mailbox ...
- Exchange Diagnostics Service (EDS) passive monitoring is reporting that {Probe.MachineName} is experiencing a high OAuth ...
- Exchange Diagnostics Service (EDS) passive monitoring is reporting that {Probe.MachineName} is experiencing a high Synchronous ...
- Exchange Diagnostics Services has detected through passive monitoring that the failure rate of Outlook Web App Outside-In ...
- Exchange Diagnostics Services has detected through passive monitoring that the number of OAB requests encountering HTTP error ...
- Exchange Diagnostics Services has detected through passive monitoring that the number of Outlook Web Access logoffs encountering ...
- Exchange Diagnostics Services has detected through passive monitoring that the number of Outlook Web Access logons encountering ...
- Exchange Diagnostics Services has detected through passive monitoring that the number of OWA requests encountering HTTP error ...
- Exchange Diagnostics Services has detected through passive monitoring that the number of requests for the light version of ...
- Exchange Diagnostics Services has detected through passive monitoring that the number of SingleUserOAB requests encountering ...
- Exchange Diagnostics Services has detected through passive monitoring that the OAB requests encountered FileLoadException. ...
- Exchange Diagnostics Services has detected through passive monitoring that the OABGEN is out of SLA. Please review MSExchangeDiagnostics ...
- Exchange fatal error information on server {0} isn't automatically sent to Microsoft for analysis. It is recommended that ...
- Exchange fatal error information on server {2} is not automatically sent to Microsoft for analysis. It is recommended that ...
- Exchange front-end server {2} has /3GB set in the Boot.ini file. Better performance would result if this value was removed. ...