Operations Manager Management Pack for Exchange 2010 - Knowledge Base

• Operations Manager Management Pack for Exchange 2010
  • Common Components
    • Active Directory Access
      • Site monitor failed to start.
      • The configuration domain controller specified in a call to SetConfigDCName wasn't found in the Sites container in Active Directory.
      • Couldn't discover the Active Directory topology in a timely manner.
      • Collect: MSExchange ADAccess Domain Controllers: LDAP Search Time.
      • The Preload Filter for the DN could not be parsed. This filter will not be used.
      • The 'PreloadBaseDNs' and 'PreloadFilters' registry keys don't contain the same number of entries.
      • An RPC request to the Microsoft Exchange Active Directory Topology service failed.
      • An asynchronous LDAP call failed. In the absence of other events, you can ignore this one.
      • The Exchange topology couldn't be generated.
      • DSAccess failed to register an Active Directory shutdown notification with the local server.
      • Collect: MSExchange ADAccess Domain Controllers: LDAP long running operations/Min.
      • An internal error occurred. Restart the Microsoft Exchange Active Directory Topology service.
      • Every Active Directory server in the domain failed to respond.
      • LDAP notify call failed. In the absence of other events, this event shouldn't impact mail flow. Review the Application log for related events.
      • The domain controller isn't running Windows Server 2003 Service Pack 1 or later.
      • The cache or hash table ran out of memory. Restart the Microsoft Exchange Active Directory Topology service.
      • Couldn't find SRV records for specified domain controller. Records may not contain correct root hints. Use Dcdiag to verify DNS server config and health.
      • Didn't find suitable domain controllers in local site. Check that you configured enough global catalogs. Check the Application log for ADAccess events.
      • The Exchange Active Directory Provider couldn't bind to Active Directory.
      • A LDAP search call failed. Ignore this error if there are no related events. Review the Application log and check for network connectivity issues.
      • A search request that was sent to the server running Active Directory didn't provide a result within a reasonable time period.
      • Collect: MSExchange ADAccess Domain Controllers: LDAP Searches timed out per minute.
      • The Exchange Active Directory Provider didn't find any domain controllers.
      • Couldn't find SRV records for domain controller. The records may not be registered in DNS. Use Dcdiag to verify the DNS server configuration and health.
      • Couldn't find SRV records for domain controller. An SRV record may be configured incorrectly in DNS. Use Dcdiag to check domain controller and DNS health.
      • RPC could not start.
      • There was an invalid configuration object found in Active Directory. The object was removed from the result set.
      • The maximum number of allowed processes are using DSAccess. No additional processes can use the API. Restart the Active Directory Topology service.
      • An error occurred when the Domain Name System (DNS) was queried for domain entries.
      • The Exchange Active Directory Provider failed to obtain an IP address for an Active Directory server.
      • The server doesn't have the Audit Security privilege on a domain controller. This privilege is used by ADAccess. Run policytest.exe. See KB 314294.
      • The Exchange Active Directory Provider couldn't find an available domain controller in the domain.
      • The Configuration Domain Controller specified in the registry wasn't found in the Sites container in Active Directory.
      • The Exchange Active Directory Provider didn't find any global catalog servers.
      • The Exchange Active Directory Provider couldn't contact a domain controller in the domain, but it could resolve the name.
      • Couldn't connect to domain controller. It won't be used by ADAccess. Check for connectivity to the domain controller and that DNS is configured correctly.
      • The configuration domain controller specified in a call to SetConfigDCName is unreachable.
      • The New Topology couldn't be generated. Make sure that the local domain controllers are reachable and running.
      • A request to establish a connection between the Exchange Active Directory Provider and a domain controller failed. The domain controller isn't available.
      • A recipient object in Active Directory isn't valid. It has been removed from the result set.
      • A recipient object in Active Directory isn't valid. Review the exception in MSExchange ADAccess 2156 for the cause.
      • Exchange failed to retrieve the local server. It's possible that the DNS name of the server has changed.
      • The DNS servers for the specified domain aren't responding.
      • Site monitor failed to update the msExchServerSite attribute in AD.
      • The directory server specified in the registry wasn't found in the Sites container in Active Directory, so the AD Provider won't use this server.
      • Internal cache error. Hash table value is incorrect. Restart Active Directory Topology service or restart server. Check System log for hardware errors.
      • A configuration object in Active Directory isn't valid so an exception occurred.
      • Couldn't create the shared memory heap. This could result from internal Epoxy (ExIPC) failures or the system may be running out of memory.
      • A general Active Directory error occured. Review the error code in the event description to determine the cause of this error.
      • Consolidate: A general Active Directory error occured.
      • The Configuration Domain Controller specified in the registry is not available.
      • The Exchange Information Store cannot contact Active Directory
      • No global catalog server was found in the local site. Make sure that the local site has enough global catalog servers for Exchange.
      • Consolidate: An LDAP search call failed.
      • The site monitor failed in its attempt to check the current site name.
      • An incorrect record was used with the cache hash table.
      • Exchange couldn't get the SID for an account. The Exchange Active Directory Topology service will continue starting with limited permissions.
      • The Exchange Active Directory Provider failed to obtain DNS records for the specified domain or forest.
      • The Exchange Active Directory Provider couldn't read an attribute from the root DSE of the Active Directory server.
    • Hub Transport and Edge Transport
      • Agents
        • Common
          • Exchange was unable to successfully use the Microsoft Update agent.
          • The download of the Microsoft Exchange Anti-Spam Update failed with an error.
          • The Content Filter agent couldn't be initialized because ExSMime.dll couldn't be initialized.
          • The Content Filter agent couldn't read the current mode. Recent changes to the mode might not be used. Restart the Microsoft Exchange Transport service.
          • Operation Manager is unable to stop the Microsoft Exchange Anti-spam Update Service.
          • Exchange was unable to determine the version of the Microsoft Update agent or the Microsoft Update agent is not current.
          • Exchange is unable to start the Microsoft Exchange Anti-spam Update Service.
          • The Content Filter agent process isn't responding. Exchange is unable to scan the message.
          • Sender ID agent: DNS isn't configured. Messages will temporarily be handled as if DNS requests have failed.
          • Unable to complete the opt-in process for Microsoft Update.
          • The Content Filter wrapper process couldn't be restarted in a timely manner. Restarting the Microsoft Exchange Transport Service may solve the problem.
          • Couldn't initialize the Content Filter agent because a required file couldn't be found on your system.
          • The Content Filter agent couldn't be initialized because notification of the file system change couldn't be initialized.
          • A notification of a configuration change has been received but the new configuration couldn't be read. The agent will continue to run with the old configuration.
          • A transport rules agent failed to create an agent instance.
          • Couldn't initialize the the Content Filter agent. Check the access control lists (ACLs) on the files.
          • Connection Filter agent: DNS isn't configured. The IP Allow List and Block List providers will be skipped.
          • The Content Filter agent couldn't be initialized because sufficient memory couldn't be allocated for an internal buffer.
          • A message could not be sent to the Content Filter wrapper because of an error. The message is being rejected.
          • The Content Filter encountered an error while trying to scan the message. This message hasn't been assigned a spam confidence level (SCL) value.
          • A transport rules agent caused an unhandled exception.
          • The maximum allowable execution time of the agent was exceeded.
          • Couldn't load the IP reputation data file.
          • The Content Filter wrapper didn't respond to the last message.
          • Protocol Analysis Background agent warning: The queue used by this agent is full. Open proxy, reverse DNS, and sender blocking are affected.
          • The Content Filter agent process is being restarted.
          • The Content Filter agent couldn't be initialized. There may be corrupted files.
          • The installation of the Microsoft Exchange Anti-Spam Update service failed with an error.
          • The Content Filter agent couldn't be initialized.
          • Exchange was unable to quarantine a message because the spam quarantine mailbox is invalid. Please configure the quarantine mailbox.
          • An error occurred while sending the shutdown message to the Content Filter wrapper process.
          • Protocol Analysis: No DNS entries were found for this server's authoritative domains. Open proxy detection is not available.
          • Protocol Analysis: DNS is not configured. Most likely, the reason for this is that no DNS servers were found. Sender Reputation calculations are disabled.
      • Transport
        • A secure connection from a domain-secured domain failed to authenticate because validation of the TLS certificate failed.
        • Spam quarantine message generation may fail because there was an error reading the quarantine mailbox configuration from the directory.
        • SMTP Connector rejected an incoming connection - the maximum number of connections has been reached
        • The configuration for one of the SMTP Receive connectors is invalid
        • Replay for 99 percentile of messages.
        • An invalid smart hosts string was detected in the routing tables for the specified SMTP connector. The SMTP connector has been ignored.
        • No route could be found to the MDB file for the Public Folder Hierarchy in the routing tables.
        • Initialization of outbound authentication failed with the specified error for the Send connector.
        • A non-SMTP gateway connection failure has occurred: The drop directory doesn't have the correct access permissions.
        • No target bridgehead servers were found for this routing group connector in the routing tables.
        • Collect: SmtpAvailability: Failures Due To Active Directory Unavailable
        • Exchange was unable to load the Active Directory recipient cache performance counters.
        • Remote server advertised hash authentication for Exchange, which isn't supported by this server.
        • The path to the location for the protocol logging for Receive connectors hasn't been set, so the existing path will be used.
        • An invalid network adapter is specified in the Transport server DNS configuration
        • SMTP rejected a mail because the Active Directory lookup for the sender address returned validation errors
        • Categorizer for 99 percentile of messages.
        • A transient configuration error was detected while the routing configuration was being loaded.
        • Exchange was unable to load the resolver performance counters.
        • The Exchange authentication certificate must be updated. Run the Enable-ExchangeCertificate command on this server to update it.
        • Transport availability impacted - SMTP availability of receive connector Default not meeting KHI threshold over last 15 minutes - Yellow(<99).
        • The STARTTLS certificate has expired. The certificate must be renewed to resume mail flow.
        • The Routing tables failed to load because Active Directory is unavailable. The system will continue to use the old instance if there is one.
        • Microsoft Exchange Transport is rejecting messages because the available disk space has dropped below the configured threshold
        • Transport availability impacted - SMTP availability of receive connector Client not meeting KHI threshold over last 15 minutes - Yellow(<99).
        • The SmtpReceive process failed to start listening on a configured binding because the specified address is already in use
        • The Exchange Transport service is rejecting message submissions due to memory consumption higher than the configured threshold
        • The topology doesn't have a route to an Exchange 2003 server from the Routing Group in the routing tables. The recipients will not be routed to this server.
        • The OnRoutedMessage agent failed to handle a catchable exception.
        • No route has been created for this Public Folder Hierarchy in the routing tables.
        • The route to the source transport or MTA server for the specified connector couldn't be found in the routing tables.
        • Collect: SmtpAvailability: Failures Due To WLID Down
        • The attempt to bind to the SourceIPAddress configured on the Send connector failed. The SourceIPAddress should be checked for correctness.
        • There wasn't enough disk space to complete the database operation. The Microsoft Exchange Transport service is shutting down.
        • The Non-SMTP Gateway Connection failed because the drop directory filename exceeds the system-defined maximum length.
        • An agent didn't close the MIME stream after handling the event for a message. The message has been rejected. Please report this problem to the agent vendor
        • Outbound direct trust authentication failed for the certificate. Make sure the EdgeSync service (MSExchangeEdgeSync) is running.
        • The Exchange Transport service was unable to start listening on the receive connector binding because an error was encountered
        • A Non-SMTP Gateway Connection failure has occurred on the specified connector: the drop directory does not exist.
        • The topology doesn't have a route to this connector in the routing tables, so the connector will not be used.
        • The Exchange Transport service was unable to listen on the Receive connector because a 'Socket Access Denied' error was encountered
        • Collect: SmtpAvailability: Failures Due To MaxInboundConnectionLimit
        • The Transport database log file path is invalid. The Microsoft Exchange Transport service is shutting down.
        • The Tranport service failed to create the Pickup directory. Pickup won't function until the directory is created.
        • Service Restart for 99 percentile of messages.
        • An Exchange 2003 server was found in the Exchange 2010 Routing Group in the routing tables.
        • Routing group configuration supported only in routing groups with Exchange 2003 servers.
        • The path to the protocol logging location for Receive connectors has not been set. As a result no protocol log for Receive connectors was written
        • A secure connection to a domain secure domain could not be established because the validation of the TLS server certificate failed.
        • The connection to a secure domain on a Send connector failed because Transport Layer Security (TLS) negotiation failed.
        • A secure connection to a domain-secured domain couldn't be established because validation of the TLS certificate failed.
        • Can't delete files from Pickup directory. Verify Network Service account has Delete Subfolders and Files permission for the directory.
        • The SMTP service completed authentication but couldn't determine the account name or security identifier (SID) for this authentication attempt
        • SMTP authentication errors from this remote site have exceeded the maximum allowed
        • Exchange was unable to load the routing performance counters.
        • The STARTTLS certificate will expire soon. The certificate must be renewed to preserve mail flow.
        • The Exchange Transport process isn't responding and will be forced to shut down.
        • Couldn't open a Transport database because a log file is missing or corrupted. The Transport service is shutting down.
        • The database file doesn't match the log files. The Microsoft Exchange Transport service is shutting down.
        • The Send connector requires Transport Layer Security before the MailFrom command but the server can't establish TLS.
        • A message from a domain-secured domain could not be authenticated because the server did not use Transport Layer Security (TLS).
        • A certificate used for federation is about to expire
        • More than 90% messages failed to decrypt during cross-premise decryption.
        • Exchange could not read the Receive connector configuration. The Microsoft Exchange Transport service will be stopped.
        • The topology doesn't contain a route to the server in the Active Directory site in the routing tables.
        • The message could not be received from a domain-secured domain because of a configuration error on a Receive connector.
        • Exchange was unable to load the STARTTLS certificate from the local store because of a mismatch with what was configured on connector FQDN.
        • Outbound authentication failed at the send connector. It may have failed to acquire a Kerberos ticket for the destination target name.
        • The SMTP connector rejected an incoming connection because the maximum number of connections for this connector has been reached
        • No source routing group was found in the routing tables for the specified connector. Therefore, the connector has been skipped.
        • A route to the owning server couldn't be found in the routing tables. Messages sent to recipients on this store won't be routed.
        • Inbound direct trust authentication failed for a certificate
        • The transport process could not load poison message information from the registry. Access to the registry failed with the specified error.
        • Exchange couldn't find a certificate in the personal store on the local computer.
        • Can't open or rename file in the Pickup directory. As a result, some mail may not be processed by Pickup. For more information, review the event description.
        • The SMTP Receive connector rejected the specified error message because of a database issue
        • The maximum allowable number of retries to load routing configuration data has been reached. The service will be stopped.
        • Store Driver Submission for 99 percentile of messages.
        • Processing the MSExchangeTransport Pickup file caused the Transport process to fail. The file will be deleted.
        • Message Deferred for 99 percentile of messages.
        • A Transport database operation has encountered a fatal error. The Transport service is shutting down.
        • Collect: SmtpAvailability: Failures Due To I/O Exceptions
        • The SmtpReceive process failed to start listening on a configured binding because IPv6 is not enabled
        • SMTP Receive for 99 percentile of messages.
        • A non-SMTP Gateway Connection failure has occurred on the specified connector: The Drop Directory Quota limit has been exceeded.
        • Transport categorizer jobs are partially unavailable - percentage of available categorizer jobs - Yellow(<99)
        • The MessageTrackingLog is enabled, but the MessageTrackingLogPath value is null, so the MessageTrackingLog will be disabled.
        • No source Hub Transport servers or home MTA server set for the specified connector could be found in the routing tables.
        • Couldn't categorize a non-expirable message.
        • Collect: IsMemberOfResolver ResolvedGroups Cache Size Percentage
        • MSExchangeTransport found a critical storage error and has stopped because of insufficient permission to update registry
        • SendProtocolLogPath has been set to null, which disables protocol logging for all Send connectors on the server. No send protocol log will be written.
        • Can't find the target bridgehead server for Routing Group connector in the routing tables. Ignoring the target bridgehead server.
        • The Transport Layer Security (TLS) Certificate for the specified partner domain couldn't be validated.
        • An accepted domain entry contains invalid data. As a result the associated record will be skipped.
        • The connected routing group for the specified connector was not found in the routing tables.
        • The server can't achieveTransport Layer Security which the Receive connector requires for the MailFrom command to be run
        • Transport found a connector with source servers belonging to multiple Active Directory sites. Transport only uses servers in site with least-cost route.
        • Transport latency impacted - percent messages completing categorization over last 30 min - Yellow(<90).
        • The connection to a secure domain failed because the Transport Layer Security negotiation was unsuccessful.
        • Failed to read message customization configuration.
        • Collect: SmtpAvailability: Failures Due To TLS Errors
        • The account provided valid credentials; however, it is not authorized to use the server to submit mail to SMTP, so the authentication has failed
        • The non-nullable column in the Extensible Storage Engine (ESE) can't be found in the actual database table.
        • Collect: SmtpAvailability: Total Connections
        • Transport latency impacted - percent messages completing categorization over last 5 min - Red(<1).
        • Collect: SmtpAvailability: Failures Due To Back Pressure
        • Transport pipeline tracing is active, which may degrade system performance.
        • The account provided valid credentials; however, it does not have submit permissions on the SMTP Receive connector, so the authentication has failed
        • A configuration change was detected but the updated Receive connector configuration could not be read. The configuration change will be ignored.
        • Activation of transport components failed because of an unexpected exception.
        • Transport Categorizer Jobs are unavailable - percentage of available categorizer jobs - Red(<90)
        • The TLS certificate used for SMTP authentication by Exchange couldn't be read from Active Directory
        • The connection to the Send connector was disconnected by the remote server.
        • SMTP Send for 99 percentile of messages.
        • Unreachable Queue for 99 percentile of messages.
        • A non-SMTP address space has been detected on the SMTP Send connector that is configured to use DNS for routing messages. The address space will be ignored.
        • The database is already in use. The service will be stopped.
        • The transport process couldn't remove poison message information from the registry. Access to the registry failed with the specified error.
        • The Send connector has failed to authenticate with the remote server.
        • Percentage of messages completing categorization.
        • SMTP rejected a mail because the Active Directory lookup for the FROM address failed: the send-on-behalf-of check returned invalid data
        • Collect: SmtpAvailability: Server Alive
        • Initialization of inbound authentication failed with an error for a Receive connector
        • A message from a domain-secured domain failed to authenticate because the TLS certificate does not contain the domain name.
        • A Send connector error occurred while connecting to the specified server.
        • Total Server Latency for 99 percentile of messages.
        • Pickup service cannot submit the message due to database issues.
        • A message from a domain-secured domain failed to authenticate because no Transport Layer Security (TLS) certificate was supplied.
        • Exchange was unable to load the configuration information needed for routing. The operation will be retried after the specified interval.
        • The target routing group wasn't found for this routing group connector in the routing tables. The connector will be skipped.
        • MSExchangeTransport has detected a critical storage error and has taken an automated recovery action by moving the database
        • Submission Queue for 99 percentile of messages.
        • Exchange can't obtain the fully qualified domain name (FQDN) of the specified Exchange server in the routing tables.
        • The process to start transport agents failed. The transport service will be stopped.
        • Exchange was unable to register the service principal name.
        • A column in the Extensible Storage Engine (ESE) contains an incorrect data type.
        • External Servers Latency for 99 percentile of messages.
        • The worker process has failed to load the specified application configuration file. Please check the format of this file.
        • The STARTTLS certificate for the remote server has expired. The certificate must be renewed to resume mail flow.
        • PoisonCount has reached or exceeded the configured poison threshold.
        • Collect: SmtpAvailability: Activity Percentage
        • The connection was dropped due to an agent error.
        • A message was rejected by the remote server. This message will be deferred and retried because it was marked for retry if rejected.
        • Categorizer Job Availability
        • A DNS failure occurred at the Send connector. See the associated diagnostic information.
        • Exchange couldn't read the Receive connector configuration so the service will be stopped.
        • A configuration update occurred, but the internal cache failed to load. The existing configuration will be retained.
        • The specified connector experienced a non-SMTP gateway connection failure. An I/O exception occurred when writing to the drop directory.
        • The internal TLS certificate for this server is missing.
        • No source routing group was found in the routing tables for the specified connector with connected routing groups.
        • There is no default authoritative domain or the domain name is empty.
        • MSExchangeTransport has detected a critical storage error but won't take recovery actions
        • Anti-spam agents are enabled, but the list of internal SMTP servers is empty
        • The Exchange Transport service was unable to start listening on the Receive connector binding because the address is already in use
        • The MSExchangeTransport Pickup process does not have the necessary
        • The transport process crashed during a message processing operation. For more information, review the call stack in MSExchangeTransport event 10003.
        • The OnSubmittedMessage agent did not handle a catchable exception.
        • The topology doesn't have a route to the Active Directory site in the routing tables.
        • Authentication of the connection to a secure domain failed because the TLS server certificate didn't contain the name of that domain.
        • The Microsoft Exchange Transport Service (MSExchangeTransport) isn't running
        • Collect: IsMemberOfResolver ExpandvedGroups Cache Size Percentage.
        • An accepted domain entry was found to be corrupt in Active Directory so the configuration was rejected.
        • The Microsoft Exchange Transport service doesn't have sufficient permissions to write the Pickup directory location to the registry.
        • MSExchangeTransport detected a critical storage error but didn't complete the recovery action
        • SMTP Send Connect for 99 percentile of messages.
        • The Active Directory site for the specified Exchange server was not determined from the routing tables.
        • The Microsoft Exchange EdgeSync Service (MSExchangeEdgeSync) isn't running
        • Delivery Queue for 99 percentile of messages.
        • The SendProtocolLogPath parameter is set to null; therefore, Exchange will continue to use the old location for protocol log storage.
        • The database checkpoint file (.chk) is missing or corrupted. The Microsoft Exchange Transport service is shutting down.
        • Collect: SmtpAvailability: Availability Percentage
        • Store Driver Delivery for 99 percentile of messages.
        • Exchange was unable to create the Routing Table log file or directory.
        • The Transport process couldn't save poison message information to the registry.
        • Exchange was unable to delete the Routing Table log file.
        • Content Aggregation for 99 percentile of messages.
        • At least one file couldn't be processed. These files have been tagged with .bad extensions. Look for .bad files, and verify the content is valid.
        • Read-only files have been found in the Pickup directory.
        • A routing group for the specified Exchange server couldn't be determined in the routing tables.
        • Transport availability impacted - Server down over last 5 minutes - Red(<50)
      • Transport Log Search
        • The Microsoft Exchange Transport Log Search service failed because MessageTrackingLogPath was set to an invalid value.
        • The Microsoft Exchange Transport Log Search service failed to access a log file due to insufficient access permissions.
        • The Microsoft Exchange Transport Log Search service failed to access a log file due to an I/O error.
        • The Transport Log Search service failed to create the message tracking log directory because of an error.
        • The Microsoft Exchange Transport Log Search Service failed to start due to a LogSessionManager startup error.
        • The Microsoft Exchange Transport Log Search Service failed to start due to a message tracking log error.
        • The Microsoft Exchange Transport Log Search Service failed to start due to an ACL setup error.
        • The Microsoft Exchange Transport Log Search service failed to read configuration from Active Directory.
        • The Microsoft Exchange Transport Log Search Service (MSExchangeTransportLogSearch) isn't running
        • The Microsoft Exchange Transport Log Search service was unable to access the registry
        • The Microsoft Exchange Transport Log Search Service could not be stopped.
        • The MessageTracking log file is corrupted. The corrupted file won't be included in the search results.
    • File Distribution Service
      • An Active Directory object for the local Exchange server is not found or is invalid
      • Failed to copy file
      • File Distribution Service: Failed to read from metabase because specified metabase object could not be found. OAB synchronization suspended
      • File Distribution Service: IO operation has failed. Current file synchronization operation is aborted
      • Failed to read object configuration from Active Directory
      • File Distribution Service: Active Directory contains invalid configuration object
      • File Distribution Service: Active Directory contains invalid value for PollInterval attribute of OAB Virtual Directory object
      • Failed to connect to remote server
      • File Distribution Service: Unhandled exception occurred in worker thread. Current synchronization task is aborted
      • File Distribution Service: Failed to read property from metabase object. OAB synchronization suspended
      • File Distribution Service: Temporarily unable to connect to Active Directory to read configuration data. Will automatically retry in one minute
      • File Distribution Service: Manifest file for Offline Address Book is corrupted. Aborting current file synchronization operation
      • File Distribution Service: Failed to read the security descriptor from Active Directory for the offline address book
      • Failed to find source directory or file
      • The File Distribution service detected that the manifest file for the UM dial plan is corrupted. The current file synchronization operation is aborted
      • File Distribution Service: Remote file not found. Current synchronization task aborted
    • Transport Throttling Client
    • All Server Roles
      • Collect: Microsoft Exchange problem analysis events.
      • No DNS servers could be retrieved via the network adapter. Use the Get-NetworkConnectionInfo cmdlet to check your network connectivity .
      • Collect: Microsoft Exchange Monitoring service events.
      • The removal of privileges from a process failed with an error code. The process and error code are specified in the event description.
      • Collect: Microsoft Exchange initial problem report event.
      • Exchange failed to write the logs because of an error. The source component and cause of the error are specified in the event description.
      • Exchange failed to create the log directory. Logs won't be generated until the reason for the failure is corrected.
    • Remote PowerShell
      • Failed to execute the Test-PowerShellConnectivity (Internal) diagnostic cmdlet.
      • Collect: WSMan:Active Users
      • Remote PowerShell connectivity (Internal) failures
      • Remote PowerShell connectivity (Internal) transaction failure - Server configuration check failure
      • Collect: WSMan:Active Shells
      • Collect: WSMan:Active Operations
    • Internal Role Services Monitoring
      • The World Wide Web Publishing Service (W3Svc) isn't running
      • The IIS Admin Service (IISAdmin) isn't running
      • The Windows Remote Management Service (WinRM) isn't running
      • The Microsoft Exchange Active Directory Topology Service (MSExchangeADTopology) isn't running
    • Service Monitoring
      • The Microsoft Exchange Service Host service (MSExchangeServiceHost) isn't running
    • Domain Controller
      • Collect: Domain Controllers: LDAP Fatal errors per minute.
      • Collect: Domain Controllers: LDAP Disconnects per minute.
      • Collect: Domain Controllers: LDAP Searches timed out per minute.
      • Collect: Domain Controllers: User searches failed per minute.
      • Collect: Domain Controllers: Number of outstanding requests.
      • Collect: Domain Controllers: Long running LDAP operations/Min.
    • Server
      • Disk Free Megabytes low - Yellow(<40MB).
      • Collect: LogicalDisk: % Free Space.
      • An error was detected on a hard drive during a paging operation
      • The file system structure on the disk is corrupt and unusable
      • Collect: LogicalDisk: Free Megabytes.
      • Disk Free Megabytes low - Red(<20MB).
      • Disk % Free Space low - Red(<10%).
      • Disk % Free Space low - Yellow(<15%).
    • MSExchangeRPC Service Monitoring
      • The Microsoft Exchange RPC Client Access Service (MSExchangeRPC) isn't running
  • Client Access
    • Exchange Control Panel
      • ECP Connectivity
        • Exchange Control Panel connectivity (External) transaction failure - Client Access server configuration check failure.
        • An Exchange Control Panel connectivity (Internal) transaction failure occurred. Test-ECPConnectivity must be run on an Exchange server.
        • Exchange Control Panel connectivity (Internal) transaction warnings.
        • Exchange Control Panel connectivity (Internal) transaction failures.
        • Exchange Control Panel connectivity (External) transaction failures.
        • Filter: ECP Connectivity (External) success events.
        • Filter: ECP Connectivity (Internal) missing test user events.
        • Filter: ECP Connectivity (External) missing test user events.
        • Exchange Control Panel connectivity (External) transaction failure - Test-ECPConnectivity must be run on an Exchange server.
        • Exchange Control Panel connectivity (External) transaction warnings.
        • Filter: ECP Connectivity (Internal) success events.
        • Exchange Control Panel connectivity (Internal) transaction failure - Client Access server configuration check failure.
      • Exchange Control Panel detected an unhandled exception during a web service request
      • Exchange Control Panel detected an unhandled exception during a page request
      • An external ECP CAS server wasn't authorized to make proxy calls to the internal CAS server
      • Exchange Control Panel failed to find a mailbox for a user
      • Exchange Control Panel detected an SSL trust failure while making a proxy call
      • The cmdlet that Exchange Control Panel requires to determine an RBAC role returned an error
      • The file that lists the mobile operators and their capabilities can't be found
      • There's an invalid scheme in the Exchange Control Panel proxy URL
      • An Exchange Control Panel proxy call failed to connect with the target server
      • Indicates that Exchange Control Panel detected an error during a proxy call
      • Exchange Control Panel failed to find a Client Access server in the same site as a user's mailbox
      • Exchange Control Panel detected an unhandled exception during a script resource request
    • Availability Service
      • Collect: Availability Service Suggestions Requests
      • Collect: Availability Service Requests/sec
      • Failed Availability Service request to Local Server FQDN
      • Collect: .NET Queue for EWS Application Pool
      • Collect: .NET Time in Queue for EWS Application Pool
      • Availability Service Initialization Failure
      • Collect: Availability Service Avg Time Cross Forest
      • Collect: Availability Service Avg Time Cross-Site Queries/sec
      • Missing Availability Service Configuration Information for the Current Forest
      • Failed Availability Service requests to External Hostnames
      • Collect: Availability Service Avg Time Cross-Site Failures/sec
      • Collect: Availability Service Avg Time Federated
      • Collect: Availability Service Avg Time/request
      • Collect: Availability Service Avg Time Cross Site
      • Invalid Account Credentials/Unable to Authenticate
    • Client Access Test Configurations
      • The Test-ECPConnectivity (Internal) diagnostic cmdlet failed to run.
      • Exchange was unable to execute the diagnostic cmdlet to probe the IMAP4 connectivity state.
      • POP3 connectivity couldn't be tested.
      • Exchange Control Panel connectivity (External) transaction failure - The test credentials can't be used to test Exchange Control Panel.
      • Failed to execute the Test-ActiveSyncConnectivity (Internal) diagnostic cmdlet.
      • Exchange was unable to execute the diagnostic cmdlet to probe the POP3 connectivity state
      • There was a Web Services connectivity (Internal) transaction failure. The credentials supplied can't be used to test Web Services.
      • An Outlook Web App connectivity (Internal) transaction failure occurred. The test credentials can't be used to test Outlook Web App.
      • An error occurred while running the Test-ECPConnectivity (Internal) cmdlet.
      • The Test-OutlookConnectivity (Internal) cmdlet failed to run.
      • Failed to execute the Test-OutlookWebServices diagnostic cmdlet
      • An error occurred while running the Test-WebServicesConnectivity cmdlet in internal mode.
      • An Outlook Web App connectivity (External) transaction failure occurred. The test credentials can't be used to test Outlook Web App
      • An error occurred while the Test-ECPConnectivity (External) cmdlet was running.
      • The state of IMAP4 connectivity couldn't be detected.
      • An error occurred while running the Test-OWAConnectivity (External) cmdlet
      • Failed to execute the Test-OWAConnectivity (Internal) diagnostic cmdlet
      • An error occurred while executing the Test-OWAConnectivity (Internal) cmdlet
      • Failed to execute the Test-WebServices (Internal) diagnostic cmdlet.
      • The Test-ECPConnectivity (External) cmdlet failed to run.
      • Failed to execute the Test-OWAConnectivity (External) diagnostic cmdlet
      • An Exchange ActiveSync connectivity (Internal) transaction failure occurred. The test credentials can't be used to test Exchange ActiveSync.
      • Exchange Control Panel connectivity (Internal) transaction failure - The test credentials can't be used to test Exchange Control Panel.
      • An error occurred while running the Test-ActiveSyncConnectivity (Internal) cmdlet.
    • Outlook Web Access
      • Outlook Web App couldn't parse the Address Book custom properties.
      • WebReady Document Viewing isn't registered. To correct this problem, reinstall Outlook Web App.
      • The Outlook Web App proxy failed because the server that was supposed to receive the proxy traffic didn't respond.
      • OWA Connectivity
        • Filter: OWA Connectivity (External) missing test user events.
        • There was an Outlook Web App connectivity (External) transaction failure. The Client Access server configuration check failed
        • Filter: OWA Connectivity (Internal) success events.
        • There was an Outlook Web App connectivity (External) transaction failure. The Test-OWAConnectivity cmdlet must be run on a Client Access server
        • Outlook Web App connectivity (External) transaction failures
        • There was an Outlook Web App connectivity (Internal) transaction failure. The Client Access server configuration check failed
        • Outlook Web App connectivity (Internal) transaction failures
        • There was an Outlook Web App connectivity (Internal) transaction failure. The Test-OWAConnectivity cmdlet must be run on a Client Access server.
        • Filter: OWA Connectivity (External) success events.
        • Filter: OWA Connectivity (Internal) missing test user events.
        • Outlook Web App connectivity (Internal) transaction warnings
      • Outlook Web App couldn't parse the Address Book custom properties. Review MSExchangeOWA event 33 for the cause.
      • The Outlook Web App proxy failed because it couldn't find a trusted certificate for SSL encryption.
      • Outlook Web App failed to initialize. A forms registry file is not valid.
      • The WebReady Document Viewing worker application can't be found.
      • Outlook Web App failed to retrieve the Active Directory system configuration session.
      • Outlook Web App failed to initialize. A theme ID attribute wasn't found. Review MSExchangeOWA event 24 for the cause.
      • Outlook Web App failed to initialize. A referenced forms registry folder doesn't exist. Review MSExchangeOWA event 1 for the cause.
      • Outlook Web App failed to initialize. A forms registry file isn't valid. Review MSExchangeOWA event 5 for the cause.
      • Outlook Web App failed to initialize. There are multiple forms registries with the same name.
      • The WebReady Document Viewing manager wasn't able to access the temporary folder.
      • Outlook Web App failed to initialize. A forms registry file isn't valid. Review MSExchangeOWA event 6 for the cause.
      • Outlook Web App failed to initialize. A referenced forms registry folder doesn't exist. Review MSExchangeOWA event 2 for the cause.
      • The Outlook Web App proxy failed because no Outlook Web App virtual directory configured for Kerberos authentication could be found in the site.
      • The Outlook Web App proxy failed because of SSL configuration issues on the destination Outlook Web App virtual directory.
      • Outlook Web App failed to read the message classification settings from Active Directory for one of its virtual directories.
      • The Outlook Web App proxy or redirection failed because one of the service discovery entries isn't valid.
      • Outlook Web App failed to parse the Address Book custom properties. Review MSExchange OWA event 34 for the cause. One of the elements isn't valid.
      • Outlook Directory
        • The average MSExchangeAB NSPI directory browse request is taking longer than the allotted threshold and negatively affecting the Outlook experience
        • The average Microsoft Exchange Address Book NSPI directory request is taking longer than the allotted threshold. This is negatively affecting the Outlook experience
      • Outlook Web App failed to initialize.
      • Outlook Web App isn't available for one of the mailboxes in a mailbox database.
      • Outlook Web App failed to initialize. No default theme was found. Review MSExchangeOWA event 26 for the cause.
      • Outlook Web App failed to initialize. A forms registry file isn't valid. Review MSExchangeOWA event 8 for the cause.
      • Outlook Web App failed to parse the Address Book custom properties. Review MSExchangeOWA event 35 for the cause. A custom property file isn't valid.
      • A corrupted calendar configuration was detected for a user. Review MSExchangeOWA event 59 for the cause. Exchange is resetting the configuration.
      • Outlook Web App wasn't able to proxy traffic because the authentication for the connection between the two Client Access servers failed.
      • Outlook Connectivity
        • HTTP Connectivity with Autodiscover - RPC Client Access failure (Logon)
        • TCP Connectivity with Autodiscover - Unexpected Exception
        • TCP Connectivity with Autodiscover - Autodiscover failure
        • TCP Connectivity with Autodiscover - Address Book failure (NSPI)
        • HTTP Connectivity with Autodiscover - Address Book failure (ABREF)
        • TCP Connectivity with Autodiscover - RPC Client Access failure (Logon)
        • HTTP Connectivity with Autodiscover - RPC Client Access failure (Connect)
        • HTTP Connectivity with Autodiscover - Address Book failure (NSPI)
        • HTTP Connectivity with Autodiscover - Unexpected Exception
        • HTTP Connectivity with Autodiscover - Autodiscover failure
        • TCP Connectivity with Autodiscover - RPC Client Access failure (Connect)
        • TCP Connectivity with Autodiscover - Address Book failure (ABREF)
      • The Outlook Web App proxy failed to verify access for the account used by the Exchange Client Access server.
      • The Outlook Web App proxy failed because the user for whom the traffic was proxied is a member of too many groups.
      • Outlook Web App failed to read or update some of its configuration settings.
      • Outlook Web App failed to initialize. A forms registry file isn't valid. Review MSExchangeOWA event 7 for the cause.
      • There's an error in your Outlook Web App configuration. A character in a file extension isn't valid.
      • Outlook Web App failed to initialize. A required small icon configuration file doesn't exist.
      • Outlook Web App failed to initialize. A required forms registry folder doesn't exist. For more information, review MSExchangeOWA event 3.
      • Outlook Web App failed to parse the Address Book custom properties.
      • Outlook Web App failed to initialize. A file from a theme folder couldn't be parsed. Review MSExchangeOWA event 22 for the cause.
      • A user couldn't sign in to Outlook Web App because the user's Active Directory profile doesn't have a primary SMTP address.
      • Outlook Web App failed to initialize. A file from a theme folder couldn't be parsed.
      • Outlook Web App encountered an error when a user tried to change the Outlook Web App language setting.
      • Collect: MSExchange RpcClientAccess Per Server RPC Failed Backend Connections
      • Collect: MSExchange RpcClientAccess Per Server RPC Active Backend Connections (% of Limit)
      • Collect: MSExchange RpcClientAccess Per Server Average End-To-End RPC Latency
      • Collect: MSExchange RpcClientAccess Per Server RPC Average Latency (Backend)
      • The average MSExchange RpcClientAccess request is taking longer than the allotted threshold. This is negatively affecting the Outlook experience
      • Outlook Web App failed to initialize. A forms registry file isn't valid. Review MSExchangeOWA event 9 for the cause.
      • The Outlook Web App proxy failed because the Client Access server that was supposed to receive the proxy traffic didn't respond.
      • Outlook Web App wasn't able to register for setting change notification for one of its virtual directories.
      • Outlook Server
        • HTTP Connectivity Against Local Server - Unexpected Exception
        • HTTP Connectivity Against Local Server - RPC Client Access failure (Logon)
        • HTTP Connectivity Against Local Server - RPC Client Access failure (Connect)
        • HTTP Connectivity Against Local Server - Autodiscover failure
        • HTTP Connectivity Against Local Server - Address Book failure (ABREF)
        • HTTP Connectivity Against Local Server - Address Book failure (NSPI)
        • TCP Connectivity Against Local Server - Unexpected Exception
        • TCP Connectivity Against Local Server - RPC Client Access failure (Logon)
        • TCP Connectivity Against Local Server - RPC Client Access failure (Connect)
        • TCP Connectivity Against Local Server - Address Book failure (ABREF)
        • TCP Connectivity Against Local Server - Address Book failure (NSPI)
      • There's an error in your Outlook Web App configuration. The authentication type specified in the Web.config file isn't correct.
      • Outlook Web App failed to read the configuration settings from Active Directory for one of its virtual directories.
      • Outlook Web App failed to initialize. A file from a theme folder couldn't be parsed. Review MSExchangeOWA event 19 for the cause.
      • The Outlook Web App proxy failed because of a version mismatch between the source and destination servers.
      • An Outlook Web App configuration setting isn't valid. The authentication type specified on the Outlook Web App virtual directory is Anonymous.
      • Outlook Web App failed to initialize. A referenced theme folder is missing. Review MSExchangeOWA event 18 for the cause.
      • Outlook Web App failed to initialize. A file from a theme folder couldn't be parsed. Review MSExchangeOWA event 25 for the cause.
      • A folder couldn't be created to cache the current Outlook Web App process. Other processes may be using the same directory.
      • Outlook Web App failed to initialize. A file from a theme folder couldn't be parsed. Review MSExchangeOWA event 20 for the cause.
      • Outlook Web App failed to initialize. A forms registry file isn't valid.
      • Outlook Web App encountered an error during initialization. The values defined for the Alt attribute in the small icon configuration file aren't valid.
      • There's an error in your Outlook Web App configuration. The configuration for a virtual directory couldn't be found.
    • POP3
      • POP Connectivity
        • A POP3 connectivity transaction failure occurred. The specified server isn't a Client Access server.
        • A POP3 connectivity transaction failure occurred. The mailbox database wasn't found.
        • A POP3 connectivity transaction failure occurred. The Microsoft Exchange Information Store service isn't running.
        • A POP3 connectivity transaction failure occurred. The Client Access server isn't enabled for RPC
        • A POP3 connectivity transaction failure occurred. There is no Exchange virtual server on the server that was specified by the user.
        • A POP3 connectivity transaction failure occurred. The session object hasn't been created
        • A POP3 connectivity transaction failure occurred. The version of the server is older than the supported versions
        • A POP3 connectivity transaction failure occurred. The Client Access server wasn't found.
        • A POP3 connectivity transaction failure occurred. The specified mailbox database is a recovery mailbox database and won't be monitored.
        • POP3 connectivity transaction failures.
        • A POP3 connectivity transaction failure occurred. The mailbox isn't enabled for the user.
        • A POP3 connectivity transaction failure occurred. The mailbox database isn't unique.
        • A POP3 connectivity transaction failure occurred because a security error was found
        • A POP3 connectivity transaction failure occurred. The NetworkCredential value for the given MailboxCredential is set to null.
        • A POP3 connectivity transaction failure occurred. The specified user isn't unique.
        • Filter: POP Connectivity success events.
        • A POP3 connectivity transaction failure occurred. The Client Access server wasn't specified
      • Collect: POP3 Current Connections
      • Collect: POP3 Average Command Processing Time (ms)
      • Collect: POP3 Current Proxy Connections
      • Collect: POP3 Connections Rate
    • IMAP4
      • IMAP Connectivity
        • An IMAP4 connectivity transaction failure occurred. The mailbox database isn't unique.
        • IMAP4 connectivity transaction failures.
        • An IMAP4 connectivity transaction failure occurred. The NetworkCredential value for the given MailboxCredential is set to null.
        • IMAP4 connectivity transaction failure - The Client Access Server is not RPC-enabled.
        • An IMAP4 connectivity transaction failure occurred. The specified mailbox database is a recovery mailbox database, so it won't be monitored.
        • An IMAP4 connectivity transaction failure occurred. The session object wasn't created.
        • Filter: IMAP Connectivity success events.
        • An IMAP4 connectivity transaction failure occurred. A security error was found.
        • An IMAP4 connectivity transaction failure occurred. No Exchange virtual server was found on the node specified by the user.
        • An IMAP4 connectivity transaction failure occurred. The Mailbox database wasn't found.
        • An IMAP4 connectivity transaction failure occurred. The specified server is not a Client Access server.
        • An IMAP4 connectivity transaction failure occurred. The specified server version is older than the currently-supported versions.
        • An IMAP4 connectivity transaction failure occurred. The Exchange Information Store service isn't running.
        • IMAP4 connectivity transaction failure - The Client Access server was not found.
        • An IMAP4 connectivity transaction failure occurred. The specified user isn't unique.
        • An IMAP4 connectivity transaction failure occurred. The mailbox isn't enabled for the user.
        • IMAP4 connectivity transaction failure - The Client Access Server was not specified.
      • Collect: IMAP4 Current Connections
      • Collect: IMAP4 Current Proxy Connections
      • Collect: IMAP4 Connections Rate
      • Collect: IMAP4 Average Command Processing Time (ms)
    • File Distribution Service
      • Collect: MSExchangeFDS:OAB: Download Tasks Completed
      • MSExchangeFDS:OAB: Download Tasks Completed - sustained for 24 hours - Red (= 0)
      • Collect: MSExchangeFDS:OAB: Download Task Queued
    • Information Worker
      • The remote forest AvailabilityAddressSpace object for proxying a cross-forest request couldn't be found.
      • A request to access a public folder failed.
      • The Proxy Web request to a remote Active Directory forest couldn't be issued because of invalid or missing credentials.
      • The Availability service couldn't successfully send a proxy Web request to another instance of the Availability service.
      • A Web request failed security checks.
      • The Autodiscover service couldn't discover the Availability service that's running in a remote Active Directory forest.
      • Availability Service initialization failed.
      • An exception occurred while attempting to locate a Client Access server to handle the request.
      • The configuration for verifying cross-forest requests wasn't found in Active Directory.
      • Unable to retreive the server security descriptor.
      • Unable to retrieve the local server object from Active Directory.
      • A Client Access server couldn't be found to handle the request.
      • The Availability service wasn't able to log on as the network service context for proxying requests.
    • Service Monitoring
      • The Microsoft Exchange POP3 service (MSExchangePOP3) isn't running
      • The Microsoft Exchange Mailbox Replication Service (MSExchangeMailboxReplication) isn't running
      • The Microsoft Exchange File Distribution service (MSExchangeFDS) isn't running
      • The Microsoft Exchange IMAP4 service (MSExchangeIMAP4) isn't running
      • The Microsoft Exchange Forms-Based Authentication service (MSExchangeFBA) isn't running
      • The Microsoft Exchange Address Book service (MSExchangeAB) isn't running
      • The Microsoft Exchange Protected Service Host service (MSExchangeProtectedServiceHost) isn't running
    • Mailbox Replication Service
      • The Microsoft Exchange Mailbox Replication service isn't running
      • Monitoring failed to run the Test-MRSHealth cmdlet
      • MSExchange Mailbox Replication service is not responding to RPC/WCF ping
      • The Microsoft Exchange Mailbox Replication service isn't scanning MDB queues for jobs
    • Auto Discovery
      • The provider that is required for the Autodiscover service is unavailable.
      • An unhandled exception occurred in the Autodiscover service. For more information, contact Microsoft Product Support.
      • An unexpected error occurred while retrieving data from the Autodiscover service.
      • An unexpected provider error occurred in the Autodiscover service.
      • The provider configuration for the Autodiscover service is not valid. To obtain a valid DLL, contact Microsoft Product Support.
      • Failed to complete Autodiscover request via Local Machine FQDN
      • The provider that was requested for the Autodiscover service could not be loaded.
      • Failed to complete Autodiscover request via External Hostnames
      • The Autodiscover service encountered an installation error.
    • ActiveSync
      • ActiveSync Connectivity
        • ActiveSync connectivity (Internal) transaction failures.
        • Filter: ActiveSync Connectivity (Internal) success events.
        • There was an Exchange ActiveSync connectivity (Internal) transaction failure. The Test-ActiveSyncConnectivity cmdlet must be run on a Client Access server.
        • Exchange ActiveSync connectivity (Internal) transaction failure - Autodiscovery failure.
      • A setting in the Web.Config file was not valid and has been reset to the default value.
      • Exchange ActiveSync has detected that the minimum heartbeat interval is set to a value that is higher than the maximum heartbeat interval.
      • The connection between the Client Access server and the Mailbox server failed.
      • Content indexing is not enabled on the mailbox server.
      • The proxy request has failed due to an invalid SSL certificate on the destination Client Access server.
      • The proxy request to a Client Access server has timed out. The server specified in the event description may be overloaded.
      • An exception occurred and was handled by Exchange ActiveSync.
      • The connection to the mailbox has failed.
      • Exchange ActiveSync has encountered repeated failures with a mailbox server. The process will be postponed.
      • Exchange ActiveSync could not access a mailbox on a Mailbox server because the Mailbox server is offline.
      • Privileges for the Exchange ActiveSync service are incorrect. Check permissions for the Exchange ActiveSync service's ASP.NET process account.
      • Collect: EAS Requests Queued
      • Collect: EAS Requests Per Second
      • Collect: EAS Current Requests
      • Exchange Direct Push has detected that the maximum heartbeat interval is set to a value that is greater than the maximum allowable value.
      • Exchange Direct Push has detected that the minimum heartbeat interval is set to a value that is lower than the minimum allowable value.
      • A transient error occurred while accessing Active Directory.
      • The proxy request has failed to authenticate. Make sure that Integrated Authentication is enabled on the destination Client Access server.
    • Web Services
      • WebServices Connectivity
        • The internal Web Services connectivity transaction failed. The Test-WebServicesConnectivity cmdlet must be run on a Client Access server.
        • Filter: WebServices Connectivity success events.
        • WebServices connectivity (Internal) transaction failure - The credentials cannot be used to test Web Services.
        • WebServices connectivity (Internal) transaction failures.
        • A Web Services connectivity (Internal) transaction failure occurred. There was an Autodiscover failure.
      • An internal server error occurred in the Exchange Web Services component
  • Unified Messaging
    • SubComponent
      • Pipeline
        • % of Messages Successfully Processed Over the Last Hour - Red (< 90)
        • % of Messages Successfully Processed Over the Last Hour - Yellow (< 95)
      • Telephony
        • Inbound
          • The Microsoft Exchange Speech Engine rejected a call
          • A service request to the Media Relay Authentication server has failed.
          • An error occurred during an Mserv lookup.
          • A Unified Messaging server couldn't be located to handle the call for a particular mailbox.
          • The Mserv lookup resulted in the same partner ID as the current site. It's possible that a provisioning error occurred.
      • PartnerTranscriptionFailures
      • ProtectedVoiceMessage
        • The Microsoft Exchange Unified Messaging service wasn't able to encrypt or decrypt a voice message.
    • Performance Reporting
      • Collect: MSExchangeUMAutoAttendant: Out of Hours Calls
      • Collect: MSExchangeUMGeneral: Delayed Calls (Report Collection)
      • Collect: MSExchangeUMSubscriberAccess: Calls Disconnected by Callers During UM Audio Hourglass
      • Collect: MSExchangeUMGeneral: Total Calls (Report Collection)
      • Collect: MSExchangeUMCallAnswer: Call Answering Missed Calls (Report Collection)
      • Collect: MSExchangeUMAvailability: Calls Disconnected by UM on Irrecoverable External Error (Report Collection)
      • Collect: MSExchangeUMSubscriberAccess: Email Messages Heard
      • Collect: MSExchangeUMCallAnswer: Average Voice Message Size
      • Collect: MSExchangeUMCallAnswer: Fetch Greeting Timed Out
      • Collect: MSExchangeUMSubscriberAccess: Voice Message Queue Accessed
      • Collect: MSExchangeUMGeneral: Calls Rejected (Report Collection)
      • Collect: MSExchangeUMSubscriberAccess: Email Message Queue Accessed
      • Collect: MSExchangeUMGeneral: Average Call Duration
      • Collect: MSExchangeUMAvailability: Directory Access Failures
      • Collect: MSExchangeUMSubscriberAccess: Email Messages Deleted
      • Collect: MSExchangeUMSubscriberAccess: Subscriber Logon Failures
      • Collect: MSExchangeUMSubscriberAccess: Launched Calls (Report Collection)
      • Collect: MSExchangeUMAvailability: Calls Disconnected on Irrecoverable Internal Error
      • Collect: MSExchangeUMCallAnswer: Call Answering Voice Messages (Report Collection)
      • Collect: MSExchangeUMGeneral: User Response Latency
      • Collect: MSExchangeUMSubscriberAccess: Reply Messages Sent (Report Collection)
      • Collect: MSExchangeUMAutoAttendant: Directory Accessed
      • Collect: MSExchangeUMGeneral: Total Calls per Second
      • Collect: MSExchangeUMSubscriberAccess: Voice Messages Deleted
      • Collect: MSExchangeUMGeneral: Current Calls
      • Collect: MSExchangeUMCallAnswer: Call Answering Calls (Report Collection)
      • Collect: MSExchangeUMAutoAttendant: Transferred Count
      • Collect: MSExchangeUMSubscriberAccess: Voice Messages Heard
      • Collect: MSExchangeUMSubscriberAccess: Calendar Items Heard
      • Collect: MSExchangeUMSubscriberAccess: Voice Messages Sent (Report Collection)
      • Collect: MSExchangeUMSubscriberAccess: Calendar Accessed
      • Collect: MSExchangeUMAutoAttendant: Total Calls (Report Collection)
      • Collect: MSExchangeUMAutoAttendant: Operator Transfers
      • Collect: MSExchangeUMSubscriberAccess: Subscriber Logons
      • Collect: MSExchangeUMCallAnswer: Calls Disconnected by Callers During UM Audio Hourglass
      • Collect: MSExchangeUMAvailability: Total Queued Messages
      • Collect: MSExchangeUMAutoAttendant: Disconnected Without Input
      • Collect: MSExchangeUMAutoAttendant: Business Hours Calls
      • Collect: MSExchangeUMSubscriberAccess: Average Subscriber Call Duration
      • Collect: MSExchangeUMAutoAttendant: Average Call Time
    • Availability
      • Service
        • UM Connectivity (Local Voice) transaction failure - Call wasn't answered before time-out.
        • The Test-UMConnectivity (Local Voice) cmdlet failed to run.
        • UM Connectivity (Local Voice) transaction failure - Microsoft Exchange Unified Messaging service isn't installed or running.
        • The Microsoft Exchange Unified Messaging service failed to start.
        • UM connectivity (Local Voice) transaction failure.
        • UM Connectivity (Local Voice) transaction failure - Active Directory error encountered.
        • An error occurred while the Test-UMConnectivity (Local Voice) cmdlet was running.
      • Gateway
        • An IP gateway or IP PBX didn't respond to a SIP OPTIONS request from the Unified Messaging server.
    • GeneralSensor
      • MailboxFailures
    • Service Monitoring
      • The Microsoft Exchange Unified Messaging service (MSExchangeUM) isn't running
      • The Microsoft Exchange Speech Engine service (MSSpeechService) isn't running
    • Client Access
      • The Client Access server wasn't able to contact a Unified Messaging server for a Play On Phone request.
  • Mailbox
    • Information Store
      • Collect: MSExchangeIS Client: Bytes Sent/sec.
      • Collect: MSExchangeIS Client: RPC Average Latency
      • Collect: MSExchange Database: I/O Database Reads Average Latency (Report Collection).
      • The Microsoft Exchange Information Store service (MSExchangeIS) is not running
      • Collect: MSExchange Database: I/O Database Writes Average Latency (Report Collection).
      • Collect: MSExchangeIS Client: JET pages read/sec
      • Collect: LogicalDisk: Avg. Disk sec/Write.
      • The Exchange store failed to start because it is out of file handles
      • Collect: MSExchangeIS: Deadlocks (Report Collection).
      • The Exchange store has failed to start due to an error retrieving the local host information
      • Collect: MSExchange Database: I/O Log Writes Average Latency (Report Collection).
      • Collect: MSExchange Database: I/O Database Reads/sec (Report Collection).
      • Collect: MSExchangeIS: RPC Requests (Report Collection).
      • The Exchange store failed to start because the RPC listener registration failed
      • Collect: LogicalDisk: Avg. Disk sec/Read.
      • Unable to initialize the Exchange store due to the clocks on the client and server not being synchronized
      • Collect: MSExchangeIS Mailbox: Messages Queued for Submission.
      • Collect: MSExchangeIS Client: Bytes Received/sec.
      • Collect: MSExchange Database: Version buckets allocated.
      • The Exchange store encountered a stack overflow
      • Collect: MSExchangeIS Client: JET pages preread/sec
      • The Exchange store failed to start because it is out of memory
      • Collect: Mailbox: MSExchange Database Log Records/sec.
      • The Exchange store has deadlocked
      • Collect: MSExchange Database: I/O Database Writes/sec (Report Collection).
      • Collect: MSExchangeIS Client: ROPs/sec.
      • Collect: MSExchangeIS: RPC Averaged Latency (Report Collection).
      • The Exchange store has terminated
      • The Exchange store has failed to initialize
      • Collect: MSExchangeIS: Client:RPCs succeeded (Report Collection).
    • System Attendant
      • System Attendant reported an error in its Directory Service (DS) Monitoring thread
      • OALGen failed to retrieve the CMS name.
      • OABGen received an error while generating the differential offline address book file.
      • OABGen failed to read the OAB version 4 property list from registry.
      • System Attendant reported an error when setting directory service notification.
      • Unable to find the e-mail address in the directory.
      • System Attendant failed to stop the server.
      • OABGen couldn't generate full details because the total size of the details information is greater than 64 KB.
      • Microsoft Exchange System Attendant does not have sufficient rights to read Exchange configuration objects in Active Directory.
      • Consolidate: A MAPI call failed with a specific error.
      • An Address List has an invalid Filter Rule (purportedSearch).
      • Consolidate: A monitoring thread was unable to read the queue information.
      • System Attendant requires the ABV DG dll for offline address book generation but it cannot be loaded
      • Failed to generate the Offline Address Book. The error is specified in the event description.
      • The directory object for this machine has the unexpected serverRole attribute value. OAB will not be generated by this server.
      • Name Service Provider Interface (NSPI) Proxy was unable to set the remote procedure call (RPC) endpoint for transport.
      • System Attendant is stopping.
      • OABGen couldn't generate full details for some entries in the offline address book.
      • The MAD Free Busy DLL is missing or failed to start properly.
      • Name Server Provider Interface (NSPI) Proxy is unable to run because the listen thread on transport failed to start.
      • An unexpected System Attendant error occurred. Review the event description for the error that was logged.
      • Unable to generate a unique e-mail address type.
      • OABGen encountered an error while generating versions 2 and 3 of an offline address book (OAB). Not all versions of this OAB will be published.
      • Could not establish a secure LDAP connection to the server. The domain controller is not running Windows 2000 SP3 or later.
      • Name Server Provider Interface (NSPI) Proxy has been forced to terminate some or all worker and listener threads during shutdown.
      • Active Directory Address Book Referral failed to service a client request. ABREF is returning an error.
      • OABGen encountered an error while calculating offline address lists. Offline address books will not be available for client download.
      • OABGen couldn't create a message to post in the public folder.
      • System Attendant failed to correctly generate Address List Service information for the task.
      • OABGen couldn't open the directory specified in the registry as the OAB V4 publishing point.
      • Name Service Provider Interface (NSPI) Proxy ran out of memory during initialization.
      • A new parent Legacy Exchange DN container was found during the offline address book generation.
      • Consolidate: The MAD Monitoring thread was unable to connect to WMI.
      • An E-mail Address Policy has an invalid Filter Rule (purportedSearch). New users, contacts and groups will not receive email.
      • System Attendant failed to add the local computer as a member of the Active Directory service group object.
      • Name Server Provider Interface (NSPI) Proxy encountered an unknown error while creating a new packet. The received data is being dropped.
      • Name Service Provider Interface (NSPI) Proxy cannot contact any global catalogs that support the NSPI Service.
      • System Attendant failed to read the membership of the universal security group.
      • Failed to register Service Principal Name. This may blocks specific users from accessing their mailboxes.
      • An Active Directory search has failed. Cannot access schema information.
      • System Attendant is starting.
      • The Directory Service Address Book Referral failed to start.
      • An error occurred while adding a replica of the naming context
      • The Address List service could not find the address list root.
      • The MSExchangeAL service logged an out of memory exception.
      • Consolidate: The MAD monitoring thread was unable to read the System Attendant configuration from Active Directory directory service.
      • The DsProxy service failed to start.
      • Performance counters for NSPI Proxy could not be initialized
      • Name Server Provider Interface (NSPI) Proxy listener thread could not connect to the server on transport. The Winsock subsystem returned an error.
      • One of the System Attendant's tasks is blocked
      • The MSExchangeAL service logged an unexpected exception. The exception is specified in the event description.
      • Consolidate: An error occurred during the message tracking decode operation.
      • Name Service Provider Interface (NSPI) Proxy encountered an error when stopping.
      • Unable to create directory.
      • Unable to generate the e-mail address; the address type is not valid.
      • The file version of the third-party proxy address DLL file installed on the local server is not current.
      • OABGen failed to download the files currently in the offline address book. This OAB will not be generated.
      • Consolidate: Active Directory Address Book Referral failed to service a client request. ABREF is returning an error.
      • Name Service Provider Interface (NSPI) Proxy could not listen on a listening socket. The Winsock subsystem returned an error.
      • Name Service Provider Interface (NSPI) Proxy encountered an error while sending a packet.
      • OABGen detected that the file in the distribution point is corrupted or missing. This OAB will not be published.
      • Unable to move mailbox.
      • Consolidate: System Attendant reported an error when setting directory service notification.
      • Consolidate: System Attendant reported an error in its directory service Monitoring thread.
      • OABGen is configured to generate version 2 or version 3 OAB files for an offline address book, but there is no public folder server available.
      • OALGen is running on the wrong CCR cluster node. Only one node in the CCR cluster can generate OAB. OAB generation will not be performed.
      • Unable to generate an e-mail address. The address type was returned by address generation DLL.
      • OALGen is running on a passive cluster node.
      • The e-mail address description object in the Microsoft Exchange directory is missing.
      • The Win32 API call returned an error. The service could not be initialized.
      • Name Server Provider Interface (NSPI) Proxy is unable to run because a worker thread failed to start.
      • An error occurred when the Referral Interface called DSAccess to obtain a list of available global catalog servers.
      • Failed to start the Microsoft Exchange System Attendant service; review related events for more information.
      • Filter: An error occurred during the message tracking decode operation.
      • A MAPI call failed with a specific error. Review the error in the event description for more information.
      • System Attendant was unable to find the Exchange server object in Active Directory.
      • OABGen failed to load the OAB version 4 manifest file
      • An attempt was made to use the Cluster Remote Procedure Call (RPC) interface without proper permissions.
      • A specific DLL cannot be loaded. Review the error in the event description for details about the specific DLL that could not be loaded.
      • System Attendant failed to start on the server.
      • Failed to initialize DSAccess. Proxy address calculation services will not be available on the local Exchange server.
      • The service could not be initialized because the necessary entry point could not be found.
      • System Attendant is unable to generate an e-mail address of particular type.
      • System Attendant detected that the local computer is not a member of the group.
      • Referral Interface cannot contact any global catalog server that supports the NSPI Service.
      • Unable to generate e-mail addresses because no valid e-mail address types were specified.
      • Proxy encountered an error while receiving a packet. The target domain controller, the network, or a client might be down.
      • Could not read the forest GUID. The Proxy address calculation services will not be available on the local Exchange server.
      • OABGen supports only alphanumeric and space characters for the offline address name. This OAB will not be generated.
      • DsProxy DLL is required but cannot be loaded.
      • Name Server Provider Interface (NSPI) Proxy called DSAccess to obtain a list of available global catalog servers.
      • Unable to generate the e-mail address; unable to load address module for this address type.
      • DSAccess failed to provide a domain controller to use to read configuration. Proxy address calculation services will not be available.
      • OABGen failed to find or open the OAB version 4 manifest file.
      • The MSExchangeAL service start is slow due to network issues. The service will retry until successful.
      • Name Service Provider Interface (NSPI) Proxy failed to connect to the global catalog.
      • Name Service Provider Interface (NSPI) Proxy was only able to send a portion of a packet. The remainder of the packet will be sent when the network is ready.
      • Could not read a registry key because the value is not a DWORD.
      • Could not read the root entry in Active Directory.
      • Name Service Provider Interface (NSPI) Proxy encountered an unknown error while initializing shared memory for performance counter data.
      • An incorrect file version was detected. Review the event description for more information.
      • Consolidate: The MAD Monitoring thread was unable to read the queue information.
      • OABGen received an error while trying to delete one of the offline address book files from the distribution point.
      • OABGen received an error while trying to publish one of the offline address book files to the distribution point.
      • Unsupported or unloadable policy group.
      • OALGen is running on an SCC cluster node which does not have the registry value 'OabDropFolderLocation' or it is set to a non-existing path.
      • Name Service Provider Interface (NSPI) Proxy encountered an unknown exception when registering its remote procedure call (RPC) endpoints.
      • OABGen failed to create the directory. One or more offline address books will not be published.
      • DSAccess returned an error during an Active Directory notification. System Attendant will try to perform the Active Directory notification at a later time.
      • Could not open LDAP session to Active Directory using local service credentials. Cannot access Address List configuration information.
      • Failed to generate an offline address book. The error is specified in the event description.
      • Name Service Provider Interface (NSPI) Proxy can contact the global catalog, but it does not support the NSPI service.
      • Could not find an accessible writable domain controller for the domain.
      • System Attendant failed while restarting its internal services.
      • Name Service Provider Interface (NSPI) Proxy is unable to run because the Winsock subsystem failed to initialize.
      • Could not search under a given entry in the directory. Cannot access Address List information.
      • Name Service Provider Interface (NSPI) Proxy could not register an interface on any network transport. NSPI Proxy is unable to run.
    • Mail Submission
      • Percent of Active Hub Servers over last 30 minutes - Red(<10) - Edge Server
      • Unable to load the performance counters for the Microsoft Exchange Mail Submission Service. The respective Performance object is named MSExchangeMail Submission
      • Mail submission service did not successfully initialize
      • The local topology server does not belong to any Active Directory site
      • The Exchange Topology discovery couldn't find the local Exchange server in Active Directory
      • Mail submission is not keeping up with the work being presented by the changes to the locally mounted databases
      • The Microsoft Exchange Mail Submission service isn't running. Mail submission to the Hub Transport server won't occur until service is started
      • Percent of Active Hub Servers over last 10 minutes - Yellow(<50) - Edge Server
      • The Microsoft Mail Submission Service encountered an exception when trying to load network topology information
    • Database Copy
      • Single page restore initiated to correct an error in a database copy
      • Collect: Database Copy: Suspended.
      • Single page restore successfully corrected a detected error of a database copy
      • Database copy isn't keeping up with the changes on the active database copy and has failed
      • Failed to remove continuous replication files for a database copy
      • A database copy's incremental reseed files failed to removed
      • Collect: Database Copy: Failed and Suspended.
      • Database copy is
      • Failed to remove a log file for database. Either the file is in use or the service has insufficient permissions
      • A database is approaching its size limit. Exceeding the limit may result in the database becoming unavailable
      • Collect: Database Copy: Failed.
      • Didn't recover from a database failure of a replicated database because the attempted failover did not succeed
      • Database copy is suspended. The database copy isn't keeping up with the changes on the active database copy
    • Database Copy Log Logical Disk Performance
      • The mounted database copy is experiencing a critically high log file write latency. The rate is sustained for at least 5 minutes
      • Collect: Log IO: Log File Read Average Latency (Report Collection).
      • Collect: Log IO: Log File Write Average Latency (Report Collection).
      • The passive database copy is experiencing a critically high log file read latency. The rate is sustained for at least 5 minutes
    • Mailbox Test Configurations
      • Error occurred while executing the Test-ExchangeSearch diagnostic cmdlet.
      • Error occurred while running the Test-MAPIConnectivity diagnostic cmdlet
      • Error occurred while executing the Test-ReplicationHealth diagnostic cmdlet
      • Databases were moved while Test-MAPIConnectivity cmdlet was executing
      • Failed to execute the Test-ReplicationHealth diagnostic cmdlet
      • Failed to run the Test-ExchangeSearch diagnostic cmdlet.
      • Failed to execute the Test-MAPIConnectivity diagnostic cmdlet.
    • Across Cluster
      • The server is a member of a database availability group and other servers are currently not operational
    • Mailbox Monitoring
      • A directory error occurred while running the Test-MAPIConnectivity cmdlet
      • Databases were moved while the Test-MAPIConnectivity cmdlet was running on this server
      • Filter: Cas Connectivity credentials reset success events.
      • Transaction failures occurred during MAPI connectivity testing
      • Monitoring failed to run the Test-MAPIConnectivity cmdlet.
      • Filter: MAPI Connectivity success events.
      • Error while running Set-CasConnectivityTestCredentials
      • An error occurred while running the Test-MAPIConnectivity cmdlet.
    • Service Monitoring
      • The Microsoft Exchange System Attendant service (MSExchangeSA) isn't running
      • The Microsoft Exchange Mail Submission service (MSExchangeMailSubmission) isn't running
      • The Microsoft Exchange Throttling service (MSExchangeThrottling) isn't running
      • The Microsoft Exchange Information Store service (MSExchangeIS) isn't running
    • Information Store Performance
      • The Exchange information store has used 90% of available connections
      • The Exchange store has terminated due to an out-of-memory error
      • Collect: MSExchangeIS % RPC Threads (Report Collection).
      • The Exchange store encountered an RPC error
      • The Exchange store has consumed 90% of available RPC threads
      • Collect: MSExchangeIS % Connections (Report Collection).
    • Database Copy Replication
      • The database copy is not replicating log files fast enough for the last 30 minutes to keep up with the changes being made to the active database copy
      • The database copy is not replicating log files fast enough to keep up with the changes being made to the active database copy
      • Collect: Database Copy: Log Copy is Not Keeping Up (Report Collection).
    • Mailbox on Database Copy
      • A user mailbox has hit recoverable items quota limit
      • A mailbox on this database has been quarantined
      • The Exchange store can't create any more MAPI-named properties
      • A user mailbox has hit recoverable items warning quota limit
      • Collect: Quarantined Mailbox Counts.
      • A user mailbox has hit session limits
    • Replay Service
      • Collect: Replay Service: Handles (Report Collection).
      • The Microsoft Exchange Replication service was not able to enable the Active Manager RPC listener
      • The Microsoft Exchange Replication service (continuous replication service) is consuming excessive memory
      • At startup, the Microsoft Exchange Replication service cannot enable the Active Manager RPC listener
      • The Microsoft Exchange Replication service wasn't able to enable the Tasks RPC listener
      • At startup, the Microsoft Exchange Replication service isn't fully initialized. The log copier listener didn't start
      • The Microsoft Exchange Replication service couldn't enable the log copier listener
      • At startup, the Microsoft Exchange Replication service couldn't enable the Tasks RPC listener
      • The Microsoft Exchange Replication service is not running
      • At startup, the Microsoft Exchange Replication service's VSS Writer failed to initialize
      • Collect: Replay Service: Private Bytes (Report Collection).
      • The Microsoft Exchange Replication service appears to be leaking operating system handles
    • Database Copy Searchable
      • ExchangeSearch Zero Results Queries: greater than or equal 100
      • Querying taking too long: Exchange Search Slow First Batch is over 10
      • The database copy is not searchable on the local server
      • Test-ExchangeSearch created an item in a mailbox on database and then indexed it. The subsequent search for the item failed.
    • Database Copy Log Logical Disk Space
      • Collect: Log Volume: % Free Space
      • The database copy is low on log volume space. The volume has reached error levels (35% free)
      • The database copy is low on log volume space. The volume has reached warning levels (50% free)
    • Assistants
      • Collect: MSExchangeAssistants - Elapsed Time Since Last Event Queued
      • MSExchangeAssistants Percentage Failed Event Dispatchers - Resource Booking Assistant
      • Collect: MSExchangeAssistants Percentage Failed Event Dispatchers - OOF Assistant
      • MSExchangeAssistants CPU
      • MSExchange Assistants RPC timout to store. Assistants Infrastructure is no longer getting responses from store
      • Collect: MSExchangeAssistants Percentage Failed Event Dispatchers - All Assistants
      • MSExchangeAssistants Percentage Failed Event Dispatchers - FreeBusy Assistant
      • Collect: MSExchangeAssistants Failed Requests - Calendar Assistant
      • The Microsoft Exchange Assistants Service startup is being delayed due to continuous crashes
      • Collect: MSExchangeAssistants CPU
      • MSExchangeAssistants Failed Requests - Resource Booking
      • MSExchangeAssistants Percentage Failed Event Dispatchers - All Assistants
      • Collect: MSExchangeAssistants Percentage Failed Event Dispatchers - Calendar Assistant
      • Collect: MSExchangeAssistants Memory Process
      • Collect: MSExchangeAssistants Failed Requests - Resource Booking
      • Collect: MSExchangeAssistants Percentage Failed Event Dispatchers - FreeBusy Assistant
      • MSExchangeAssistants Failed Requests - Calendar Assistant
      • MSExchangeAssistants Percentage Failed Event Dispatchers - OOF Assistant
      • Collect: MSExchangeAssistants Percentage Failed Event Dispatchers - Resource Booking Assistant
      • The Microsoft Exchange Mailbox Assistants service (MSExchangeMailboxAssistants) is not running
      • Collect: MSExchangeAssistants - Events in Queue
      • MSExchangeAssistants Percentage Failed Event Dispatchers - Calendar Assistant
      • MSExchangeAssistants Memory Process
    • Content Indexing Service
      • The Exchange Search Indexer failed to retreive the local server object from Active Directory. It will be retried
      • The Microsoft Exchange Search Indexer service (MSExchangeSearch) is not running
      • MS Search (Exchange) has reached the allocated memory cap
    • Public Folder Database
    • Database Copy Performance
      • Collect: Messages submitted/sec.
      • The database copy has more user load than it can support. Users need to be moved to a different database and/or server
      • Collect: Database RPC Average Latency.
      • Collect: Messages sent/sec.
      • Collect: Move Mailboxes Into Database.
      • Collect: Delivery blocked due to Low Log Space.
      • Collect: Messages Delivered/sec.
      • The local database copy has more user load than it can support. Users need to be moved to a different database and/or server
      • Collect: Message Opens/sec.
      • Collect: Delivery blocked due to Low Database Space.
      • Collect: Move Mailboxes Out Of Database.
    • Database Copy Edb Logical Disk Space
      • The database copy is low on database volume space. The volume has reached critical levels (8% free)
      • Collect: Database Volume: % Free Space
    • Database Copy Mounted
      • Collect: Database Copy: Mounted (Report Collection).
      • Couldn't load the Exchange store because the distinguished name (DN) of the message database doesn't match the DN of directory.
      • The database copy is not mounted on the local server. Another database copy may be mounted on a different server
    • Database Copy Corruption
      • The database engine has consumed 99% of the
      • Database copy encountered a serious I/O error (lost flush) that may have affected all copies of the database
      • Collect: Database Copy: Log Bytes Write/sec (Report Collection).
      • Collect: Database Copy: Log Generation Checkpoint Depth (Report Collection).
      • The database copy is experiencing an unusually high log generation checkpoint depth for a sustained period of at least 15 minutes
      • A database experienced a hard I/O error in NTFS. NTFS failed to allow the creation of a file as part of a failover
      • Local database copy encountered a serious I/O error (active lost flush) that may have affected all copies of the database
      • The database copy is experiencing an unusually high log generation rate (bytes written/second) for a sustained period of at least 15 minutes
      • Database copy encountered a serious I/O error (active lost flush) that may have affected all copies of the database
    • Database Search Copy
      • The local database copy experienced an index corruption. Please reseed the catalog by using the Update-MailboxDatabaseCopy cmdlet with the -CatalogOnly parameter
    • Public Folder Database Edb Logical Disk Space
      • The database copy is low on database volume space. The volume has reached error levels (16% free)
      • The database copy is low on database volume space. The volume is 25% free
    • Database Copy Edb Logical Disk Performance
      • Collect: Passive database copy read latencies.
      • The passive database copy is experiencing a critically high database read latency. The rate is sustained for at least 5 minutes
      • The mounted database copy is experiencing a critically high database read latency. The rate is sustained for at least 5 minutes
      • Collect: Mounted database read latencies.
    • Public Folder Database Log Logical Disk Space
      • The database copy is low on log volume space. The volume is 50% free
      • The database copy is low on log volume space. The volume has reached critical levels (15% free)
    • Database Copy Submission
      • Collect: Database Copy: Messages Queued For Submission.
    • Cluster File Share Witness
      • The database availability group is experiencing problems that may cause it to eventually fail due to stale security information
    • Database Copy Replay
      • The database copy isn't replaying log files fast enough to keep up or catch up with the changes being made to the active database copy.
      • Collect: Database Copy: Log Replay is Not Keeping Up (Report Collection).
      • The database copy isn't replaying log files fast enough for the last two hours to keep up or catch up with the changes being made to the active database copy
    • Cluster Service
      • The Windows Cluster service is not running
      • The server is having difficulty becoming an active member of its database availability group
    • Network
      • One or more networks supporting the database availability group are not operating properly on this server
    • Cluster Quorum Group
      • The database availability group is experiencing problems that may cause it to fail due to stale security information
  • Hub Transport
    • Transport Queues
      • Collect: Hub Transport: MSExchangeTransport Queues: Retry Remote Delivery Queue Length.
      • Collect: Hub Transport: MSExchangeTransport Queues: Poison Queue Length.
      • Collect: Hub Transport: MSExchangeTransport Queues: Retry Mailbox Delivery Queue Length.
      • Collect: Hub Transport: MSExchangeTransport Queues: Largest Delivery Queue Length.
      • Collect: Hub Transport: MSExchangeTransport Queues: Retry Non-Smtp Delivery Queue Length.
      • Collect: Hub Transport: MSExchangeTransport Dumpster: Dumpster Size
      • Collect: Hub Transport: MSExchangeTransport Queues: Active Remote Delivery Queue Length.
      • Collect: Hub Transport: MSExchangeTransport Queues: Active Non-Smtp Delivery Queue Length.
      • Collect: Hub Transport: MSExchangeTransport Queues: Active Mailbox Delivery Queue Length.
      • Collect: Hub Transport: MSExchangeTransport Queues: Aggregate Delivery Queue Length (All Queues).
      • Collect: Hub Transport: MSExchangeTransport Queues: Submission Queue Length.
      • Collect: Hub Transport: MSExchangeTransport Queues: Unreachable Queue Length.
      • Collect: Hub Transport: MSExchangeTransport Dumpster: Dumpster Item Count
    • Agents
      • Recipient Filter
        • Collect: Hub Transport: MSExchange Recipient Filter Agent: Recipients Rejected by Recipient Validation (Report Collection).
        • Collect: Hub Transport: MSExchange Recipient Filter Agent: Recipients Rejected by Block List (Report Collection).
      • Content Filter
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with SCL 1 (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages that Bypassed Scanning (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with SCL 2 (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with SCL 9 (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with SCL Unknown (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages Deleted (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages Quarantined (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with a Preexisting SCL (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with SCL 8 (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with SCL 6 (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with SCL 3 (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with SCL 0 (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with SCL 7 (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages Scanned (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with SCL 5 (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages with SCL 4 (Report Collection).
        • Collect: Hub Transport: MSExchange Content Filter Agent: Messages Rejected (Report Collection).
      • SMS
        • Collect: Hub Transport: MSExchange Text Messaging Agent: Total number of text messages sent.
        • Collect: Hub Transport: MSExchange Text Messaging Agent: Average text message delivery latency (milliseconds).
        • Collect: Hub Transport: MSExchange Text Messaging Agent: Number of text messages pending delivery.
        • Collect: Hub Transport: MSExchange Text Messaging Agent: Total number of text messages sent via SMTP.
        • Collect: Hub Transport: MSExchange Text Messaging Agent: Total number of text messages sent via Exchange ActiveSync.
        • Collect: Hub Transport: MSExchange Text Messaging Agent: Text messages sent via SMTP/sec.
        • The agent encountered a problem when trying to load the file that lists the supported mobile operators and their capabilities.
        • Collect: Hub Transport: MSExchange Text Messaging Agent: Text messages sent via EAS/sec.
        • Collect: Hub Transport: MSExchange Text Messaging Agent: Text messages sent/sec.
      • Messaging Policies
        • The AD RMS service connection point (SCP) URL doesn't exist or is invalid. Republish the SCP using the AD RMS server
        • The Prelicensing agent didn't retrieve a license because the content was published for an untrusted AD RMS server. Contact the AD RMS administrator
        • Exchange doesn't have the required permissions to access the AD RMS server. Contact the AD RMS administrator for help
        • The Prelicensing agent's Web request failed because the URL was redirected. The Prelicensing agent doesn't support URL redirection
        • The Federated Delivery Encryption agent failed to find the OrganizationFederatedMailbox. Outbound messages to Outlook Live will be affected until this issue is resolved.
        • There was an error loading the journaling agent configuration.
        • Rule collection was not loaded because of configuration errors. Messages will be deferred.
        • Recipient(s) encountered with invalid master account SIDs.
        • Rule collection was not loaded because of transient errors.
        • Federated Delivery Decryption agent can't find federation certificate; can't decrypt token. Inbound messages from Outlook Live affected until resolved.
        • Exchange couldn't authenticate to the Active Directory Rights Management Services (AD RMS) server. Contact the AD RMS administrator for assistance
        • Federated Delivery Encryption agent can't get delegation token from Windows Live. Outbound messages to Outlook Live affected until issue resolved.
        • Federation is not enabled for federated delivery. Federated delivery messages to and from Outlook Live will be affected until this issue is resolved.
        • The Prelicensing agent couldn't acquire a license
        • The Prelicensing agent didn't retrieve a license because the RMS template wasn't found on the AD RMS server. Contact the AD RMS administrator
      • Connection Filter
        • Collect: Hub Transport: MSExchange Connection Filtering Agent: Connections on IP Allow List Providers (Report Collection).
        • Collect: Hub Transport: MSExchange Connection Filtering Agent: Connections on IP Block List Providers (Report Collection).
        • Collect: Hub Transport: MSExchange Connection Filtering Agent: Connections on IP Allow List (Report Collection).
        • Collect: Hub Transport: MSExchangeTransport SmtpReceive: Connections Total (Report Collection).
        • Collect: Hub Transport: MSExchange Connection Filtering Agent: Connections on IP Block List (Report Collection).
      • Sender Id
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a Fail - Not Permitted Result (Report Collection).
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a Neutral Result (Report Collection).
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a TempError Result (Report Collection).
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a SoftFail Result (Report Collection).
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages with No PRA (Report Collection).
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a None Result (Report Collection).
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a PermError Result (Report Collection).
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Missing Originating IP (Report Collection).
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated Per Second.
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated (Report Collection).
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a Pass Result (Report Collection).
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a Fail - Malformed Domain Result (Report Collection).
        • Collect: Hub Transport: MSExchange Sender ID Agent: Messages Validated with a Fail - Non-existent Domain Result (Report Collection).
      • Sender Filter
        • Collect: Hub Transport: MSExchange Sender Filter Agent: Messages Filtered by Sender Filter (Report Collection).
        • Collect: Hub Transport: MSExchange Sender Filter Agent: Messages Evaluated by Sender Filter (Report Collection).
      • Protocol Analysis
        • Collect: Hub Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Remote SRL (Report Collection).
        • Collect: Hub Transport: MSExchange Protocol Analysis Agent: Senders Processed (Report Collection).
        • Collect: Hub Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Local Open Proxy (Report Collection).
        • Collect: Hub Transport: MSExchange Protocol Analysis Agent: Senders Bypass Local SRL calculation (Report Collection).
        • Collect: Hub Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Local SRL (Report Collection).
        • Collect: Hub Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Remote Open Proxy (Report Collection).
    • EdgeSync
      • Couldn't run the Test-EdgeSyncMserv diagnostic cmdlet.
      • EdgeSync MSERV synchronization failures.
      • Credentials used by EdgeSync have either expired or haven't been created. You will need to resubscribe the Edge Transport server
      • An EdgeSync process ended because the Hub Transport server couldn't find a matching direct trust certificate on the Edge Transport server.
      • EdgeSync encountered a permanent error when synchronizing an address to MSERV
      • Unable to execute the Test-EdgeSyncEhf diagnostic cmdlet.
      • Could not run the Test-EdgeSyncMserv diagnostic cmdlet.
      • Synchronization failed to read replication data from the Active Directory.
      • EdgeSync failed to confirm the credentials for a replication account on a subscription server.
      • EdgeSync Enterprise synchronization failures.
      • EdgeSync Enterprise synchronization warnings.
      • An exception occured while loading the required EdgeSync credentials. Run the Test-EdgeSynchronization cmdlet on the Hub Transport server
      • Microsoft Exchange EdgeSync service failed to connect to the AD LDS instance on the Edge Transport server.
      • An exception occurred when the Hub Transport server tried to load the Exchange topology configuration data.
      • EdgeSync EHF synchronization warnings.
      • Failed to sync entries to EHF
      • An EdgeSync synchronization process couldn't start because the configuration data didn't pass validation.
      • EdgeSync EHF synchronization not configured.
      • EdgeSync EHF synchronization failures.
      • EdgeSync MSERV synchronization warnings.
      • EdgeSync MSERV synchronization isn't configured.
      • Failed to execute the Test-EdgeSyncEhf diagnostic cmdlet.
    • Transport DSN
      • Collect: Hub Transport: MSExchangeTransport DSN: Failure DSNs Total.
      • Collect: Hub Transport: MSExchangeTransport DSN: Delay DSNs.
    • Store Driver
      • There are too many mail submission threads on this server
      • The Store Driver transport component failed to submit a store event. It wasn't able to generate NDR because of an exception
      • An error occured while processing a meeting message
      • The Sender isn't valid. The StoreDriver event will be ignored
      • The Exchange transport Store Driver component encountered a poison message during message submission. The submission will be cancelled
      • Unable to load the performance counters for the MSExchange Store Driver Performance object
  • Edge Transport
    • Agents
      • Protocol Analysis
        • Collect: Edge Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Remote SRL (Report Collection).
        • Collect: Edge Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Local Open Proxy (Report Collection).
        • Collect: Edge Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Remote Open Proxy (Report Collection).
        • Collect: Edge Transport: MSExchange Protocol Analysis Agent: Senders Processed (Report Collection).
        • Collect: Edge Transport: MSExchange Protocol Analysis Agent: Senders Blocked Because of Local SRL (Report Collection).
        • Collect: Edge Transport: MSExchange Protocol Analysis Agent: Senders Bypass Local SRL calculation (Report Collection).
      • Attachment Filter
        • An error occured when loading the configuration for the Attachment Filtering Agent. The configuration may be corrupted or AD LDS may be unreachable
        • Collect: Edge Transport: MSExchange Attachment Filtering: Messages Attachment Filtered (Report Collection).
      • Connection Filter
        • Collect: Edge Transport: MSExchange Connection Filtering Agent: Connections on IP Block List Providers (Report Collection).
        • Collect: Edge Transport: MSExchange Connection Filtering Agent: Connections on IP Allow List (Report Collection).
        • Collect: Edge Transport: MSExchange Connection Filtering Agent: Connections on IP Block List (Report Collection).
        • Collect: Edge Transport: MSExchange Connection Filtering Agent: Connections on IP Allow List Providers (Report Collection).
        • Collect: Edge Transport: MSExchangeTransport SmtpReceive: Connections Total (Report Collection).
      • Sender Id
        • Collect: Edge Transport: MSExchange Sender ID: Messages with No PRA (Report Collection).
        • Collect: Edge Transport: MSExchange Sender Id: Messages That Bypassed Validation.
        • Collect: Edge Transport: MSExchange Sender ID: Messages Validated with a Fail - Not Permitted Result (Report Collection).
        • Collect: Edge Transport: MSExchange Sender ID: Messages Validated with a None Result (Report Collection).
        • Collect: Edge Transport: MSExchange Sender ID: Messages Validated with a Fail - Non-existent Domain Result (Report Collection).
        • Collect: Edge Transport: MSExchange Sender ID: Messages Validated with a SoftFail Result (Report Collection).
        • Collect: Edge Transport: MSExchange Sender ID: Messages Validated (Report Collection).
        • Collect: Edge Transport: MSExchange Sender Id: Messages Validated with a PermError Result (Report Collection).
        • Collect: Edge Transport: MSExchange Sender ID: Messages Validated with a Pass Result (Report Collection).
        • Collect: Edge Transport: MSExchange Sender Id: Messages Validated with a Neutral Result (Report Collection).
        • Collect: Edge Transport: MSExchange Sender ID: Messages Validated with a Fail - Malformed Domain Result (Report Collection).
        • Collect: Edge Transport: MSExchange Sender ID: Messages Validated with a TempError Result (Report Collection).
      • Content Filter
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with a Preexisting SCL (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages Quarantined (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages Rejected (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with SCL 0 (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with SCL 7 (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with SCL 2 (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with SCL 6 (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with SCL 4 (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages that Bypassed Scanning (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages Deleted (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with SCL 5 (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages Scanned (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with SCL 3 (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with SCL 9 (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with SCL Unknown (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with SCL 8 (Report Collection).
        • Collect: Edge Transport: MSExchange Content Filter Agent: Messages with SCL 1 (Report Collection).
      • Address Rewrite
        • There was an error loading configuration for the address rewriting agent
      • Sender Filter
        • Collect: Edge Transport: MSExchange Sender Filter Agent: Messages Evaluated by Sender Filter (Report Collection).
        • Collect: Edge Transport: MSExchange Sender Filter Agent: Messages Filtered by Sender Filter (Report Collection).
      • Recipient Filter
        • Collect: Edge Transport: MSExchange Recipient Filter Agent: Recipients Rejected by Recipient Validation (Report Collection).
        • Collect: Edge Transport: MSExchange Recipient Filter Agent: Recipients Rejected by Block List (Report Collection).
    • Transport DSN
      • Collect: Edge Transport: MSExchangeTransport DSN: Delay DSNs.
      • Collect: Edge Transport: MSExchangeTransport DSN: Failure DSNs Total.
    • Transport Queues
      • Collect: Edge Transport: MSExchangeTransport Queues: Submission Queue Length.
      • Collect: Edge Transport: MSExchangeTransport Queues: Poison Queue Length.
      • Collect: Edge Transport: MSExchangeTransport Queues: Aggregate Delivery Queue Length (All Queues).
      • Collect: Edge Transport: MSExchangeTransport Queues: Unreachable Queue Length.
      • Collect: Edge Transport: MSExchangeTransport Queues: Largest Delivery Queue Length.
    • Message Security
      • Failed to read ADLDS SSL port from registry
      • Renewal of EdgeSync credential failed for an Edge Transport server
      • No valid TLS certificate was found. Exchange can't update the Active Directory Lightweight Directory Service (ADLDS) credentials
      • Couldn't find the local server. Exchange can't update the Active Directory Lightweight Directory Services (AD LDS) credentials
      • Microsoft Exchange couldn't read the server configuration. The Microsoft Exchange Credential service will be stopped
      • Microsoft Exchange couldn't read the server configuration because the directory is unavailable
      • Couldn't decrypt EdgeSync credentials. Please unsubscribe and then resubscribe your Edge Transport server
    • Service Monitoring
      • The Microsoft Exchange ADAM service (ADAM_MSExchange) isn't running
      • The Microsoft Exchange Credential service (MSExchangeEdgeCredential) isn't running
  • Monitoring Components
    • Correlation Engine
      • Can't connect to Operations Manager Root Management Server
      • The service failed to start because of a problem with one of its dependencies
      • The specified correlation time window value is less than the minimum allowed value
      • Monitor reset failed
      • The correlation interval value specified is less than the minimum allowed value
      • Transient connection failure with the Operations Manager Root Management Server
      • Failed to release Operations Manager resources