Inconsistent timestamp detected on page %1 of flush map file "%2" (empty if flush map persistence in disabled). The maximum timestamp on the flush map is %3, but database page %4 has a timestamp of %5. If flush map persistence is enabled, this problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
Includes performance counters that diagnose and provide usage statistics when Unified Messaging is creating a voice mail ...
Includes performance counters that diagnose and provide usage statistics when Unified Messaging is handling calls that require ...
Includes performance counters that indicate the availability of the Microsoft Exchange Unified Messaging service and its ...
Incoming Proxy Requests Total is the total number of HTTP requests received from ASP.NET and proxied to another Exchange ...
Inconsistent timestamp detected on page %1 of flush map file "%2" (empty if flush map persistence in disabled). The maximum ...
Inconsistent timestamp detected on page %4 of flush map file "%5" (empty if flush map persistence in disabled). The maximum ...
Incorrect combination of parameters passed to ADSessionSettings ctor. An AD session bound to partition '{1}' cannot be scoped ...
Incremental reseed encountered an error in the database copy configuration in Active Directory, specifically with the property ...
Incremental seeding for database %1 has completed copying the divergent database pages and log files from the source copy. ...