The ExMon trace was captured for {1} seconds. Since it is normal for some users to use large amounts of CPU for periods of up to a few minutes, a short ExMon capture may incorrectly indicate that users are causing high load. If this tool is analyzing short captures, look for users that are consistently causing high resource utilization for several ExMon captures.
The executable files for all the transport event sinks found in the metabase of server {2} are identified and found on disk. ...
The execution time of agent '%1' exceeded %2 (milliseconds) while handling event '%3'. This is an unusual amount of time ...
The existing appointment with the subject "%1" in mailbox %2 was deleted. The duration of the existing appointment was too ...
The existing appointment with the subject "%1" in mailbox %2 was deleted. The start time, or both the duration and end time ...
The ExMon trace was captured for {1} seconds. Since it is normal for some users to use large amounts of CPU for periods of ...
The extension is invalid or not supported. LDAP_MATCHING_RULE_BIT_AND(1.2.840.113556.1.4.803) and LDAP_MATCHING_RULE_BIT_OR(1.2.840.113556.1.4.804) ...
The external e-mail address can not be changed because it is the primary SMTP dddress. Please promote another SMTP address ...
The fax call from "%1" for "%2" at number "%3" was received but no pages were received. The fax call was %4 seconds long. ...
The fax call has exceeded the configured time for a call. The call was made from %1 for %2 at number %3. The fax contains ...