RPC operations for MAPI operation "{4}" account for {0}% of the processor usage devoted to processing RPC requests. When a single MAPI operation type is responsible for a large percentage of the load, this may be an indication that the users are running an application that is behaving poorly.
Routing group connector {3} for routing group {1} has delivery restrictions based on distribution group membership and server ...
Routing group member {4} for routing group '{3}' is not connected to routing group master {2}. This may cause routing failures. ...
RPC Latency average (msec) is the average latency in milliseconds of RPC requests. Average is calculated over all RPCs since ...
RPC Latency total (msec) is the total amount of time in milliseconds spent inside RPC calls. Note that since many threads ...
RPC operations for MAPI operation "{4}" account for {0}% of the processor usage devoted to processing RPC requests. When ...
RPC Requests failed (%) is the percent of failed requests in total number of RPC requests. Here, failed means the sum of ...
RPC Requests Peak is the maximum number of client requests that were processed simultaneously by the information store since ...
rule collection was not loaded because of configuration errors. Messages will be deferred. The description of the configuration ...
Rule synchronization has successfully completed. The mailbox folder is %1 on database "%3". The distinguished name of the ...