- AIS Monitoring Platform has discovered OWA issue. When the users try to access the Outlook Web Access, the Store.exe process may stop responding. These scenarios can occur when the following conditions are true: An update is applied OR Only one of the files is updated. For example, this problem can occur when only the Store.exe file or the Exoledb.dll file is updated, but not both of the files are updated.
Critical Non Impact
Medium Priority Events
An Address List Has An Invalid Filter Rule Due To Which Directory Entries May Not Belong To This Address List
- AIS Monitoring Platform has discovered that the Address List has an invalid Filter Rule (purportedSearch). No directory entries will belong to this Address List until you correct this problem.
- AIS Monitoring Platform has discovered a checksum error in the log file during backup. This indicates a corrupt transaction log file. A backup cannot be made of a corrupt log file and the backup will fail. A checksum Jet error indicates a hardware root cause usually in the backup hardware, controller, or file system-level problems related to hardware. You may not be able to perform online Exchange store database backups successfully.
- AIS Monitoring Platform has discovered Calender meeting request issue in OWA or in non-MAPI clients. Microsoft Exchange Server 2003 users who uses Outlook Web Access (OWA) may notice that some meetings may not appear in their OWA calendars. However, the meetings will appear in their calendars if they use any version of an Outlook Client.
Database Inconsistency Was Encountered While Performing An Upgrade On The Database Run Isinteg To Detect And Repair Database Inconsistencies
- AIS Monitoring Platform has discovered that the database inconsistency was encountered while performing an upgrade on the database. Run Isinteg to detect and repair database inconsistencies.
- AIS Monitoring Platform has discovered that the background cleanup skipped pages. This message indicates that an offline defragmentation of the Exchange store database should be performed. Offline defragmentation should be performed on each database separately. This impact Exchange performance to slow down.
- AIS Monitoring Platform has discovered that there is a Database page read failed verification due to a page checksum mismatch. This error indicates possible hardware or firmware problem in the hard-disk subsystem on the Exchange server. This failure has caused physical damage to the Exchange database. Impact : This impact Mail flow down where Users cannot send or receive e-mail messages.
- AIS Monitoring Platform has discovered e-mail messages may be stuck in the Categorizer component. To determine whether this issue has occurred, you can use the Message Tracking Center. This problem occurs because some Simple Mail Transfer Protocol (SMTP) virtual servers are deleted from Exchange System Manager. However, entries for these SMTP virtual servers still exist in the Internet Information Services (IIS) metabase.
- AIS Monitoring Platform has discovered that the EdgeTransport.exe file of Exchange 2007 servers crashes continuously. This problem occurs if an Exchange Server 2003 administrator puts duplicate smarthost IP addresses on the properties of a Simple Mail Transfer Protocol (SMTP) connector. Therefore, all mail flow of Exchange 2007 servers is broken until the duplicate IP address is removed.
- AIS Monitoring Platform has discovered that the single MAPI session has exceeded the maximum number of objects. This is caused by a very high usage level by an individual user. If these errors are happening regularly, you can raise the default maximum for the affected object type (for example, to twice its default level). If at this level the specified user is continuing to generate this warning, investigate the user actions that are causing this warning. It can be caused by improper client design or unusual client usage patterns.
Exchange ActiveSync Service Experienced A Transient Error When IT Tried To Access Active Directory Information
- AIS Monitoring Platform has observed Exchange ActiveSync transient error when it tried to access Active Directory information. This Error event indicates that Exchange ActiveSync is temporarily unable to detect the user’s properties in the Active Directory directory service that are required to perform synchronization. This may be caused by a network connectivity issue between the computer that is running the Client Access server role and a domain controller.
Exchange Computer Account For The Exchange Server Has An Explicit Deny Permission For The Receive As Permission Assigned
- AIS Monitoring Platform has observed that computer account for the Exchange server has an explicit Deny permission for the Receive As permission assigned.
- This alert condition indicates that the Exchange Database requires defragmentation. The fragmentation of Exchange data occurs within the Exchange database itself, which is different than regular disk fragmentation. If you run regular disk defragmentation on an Exchange computer, you should do it during off-hours and preferably with Exchange databases stopped. Disk defragmentation is a very I/O intensive process. Therefore, an Exchange database engine could have difficulty accessing the hard drives in a timely manner. By default, Exchange databases run a defragmentation process daily. The defragmentation option makes used storage contiguous, eliminates unused storage, and compacts the database. This reduces the database’s size. Eseutil copies database records to a new database. When defragmentation is complete, the original database is deleted or saved to a user-specified location, and the new version is renamed as the original. If the utility encounters a bad record, the utility will stop and display an error message.
- This alert condition indicates that all domain controller servers in use are not responding. Possible causes: network issues may have rendered all domain controllers unreachable, all domain controllers in the Active Directory topology may not be working, or the Manage Auditing and Security Log right (SeSecurityPrivilege) was removed for Exchange Enterprise Servers or Exchange Servers security groups on some or all domain controllers.
- AIS Monitoring Platform has detected error updating public folder with free/busy information on virtual machine Machine Name. The error number is 0x80070005.
- AIS Monitoring Platform has discovered that the Evaluation period for Exchange server has expired. This will montior and alert when license to use beta version of the Microsoft Exchange Server software has expired.
- AIS Monitoring Platform has detected Named Properties or Replica Identifiers Are Depleted for An Exchange Database. If the database has reached the named property or replica identifier quota limit and an attempt is made to create a new named property or replica identifier. Impact : If attempt to create fails Named Properties or Replica Identifiers will not be created successfully.
- AIS Monitoring agent has discovered that the Exchange - Process for application pool encountered an error. Cause : The Internet Information Services (IIS) does not function correctly when the Microsoft SysPrep process is active. Impact: Dependant exchange featurs will not work.
Exchange Recipient Update Service Issues Detected Exchange Server Cannot Access Address List Configuration Information
- AIS Monitoring Platform has observed that Recipient Update Service is configured to use a Windows domain controller that is either not reachable or demoted. When the Recipient Update Service tries to query the Windows domain controller for an update, it cannot contact it.
- AIS Monitoring Platform has observed that number of client remote procedure call (RPC) errors or latency warnings is greater than the specified threshold.
Exchange System Attendant Generated Error Due To Exchange Server Computer's Distinguished Name Has Been Changed
- AIS Monitoring Platform has discovered errors due to Exchange Server computer’s distinguished name has been changed. When System Attendant starts, it caches the distinguished name of the local computer. The Exchange Server computer’s distinguished name changes when it is moved from one organizational unit to another organizational unit. The new distinguished name is different from the distinguished name that is in the cache.
- AIS Monitoring Platform has observed exchange ActiveSync doesn’t have enough permissions to create container under AD user Active Directory operation failed . Impact : A user cannot synchronize a Microsoft Exchange ActiveSync (EAS) device for the first time.
- AIS Monitoring Platform has detected mail flow issue on Exchange Server caused by Exchange aware Anti Virus (AV API).This error message is generated by Transport AVAPI which is specific to the Virus Scanning Application Programming Interface of Antivirus solution on Exchange Server.
- AIS Monitoring Platform has observed that Virtual memory necessary to run your Exchange server is fragmented in such a way that normal operation may begin to fail. It is highly recommended that you restart all Exchange services to correct this issue.
- AIS Monitoring Platform has discovered exchange transport errors. This condition monitors transport errors relating to local mailflow, following issues are categories for detection. 1. Problem caused by antivirus program on the Exchange computer that uses the Antivirus Application Program Interface (AVAPI), such as McAfee GroupShield 6.0 for Microsoft Exchange. 2. SMTP Disconnected mailbox causing local mailflow problem emails getting stuck in outlook outbox.
- AIS Monitoring Platform has discovered Messages awaiting directory lookup SMTP Queue. This condition occurs when you try to send messages to a Microsoft Exchange 2000 Server computer or to a Microsoft Exchange Server 2003 computer, the messages remain in the Messages awaiting directory lookup queue. However, message delivery to local recipients and to recipients on the Internet is successful. This problem may be caused by one or more reasons. Some of the most common causes are as follows. Cause 1 - This issue may occur if the following conditions are true: You have configured message archiving on the Exchange Server computer. Note Message archiving is also known as message journaling. The mailbox or the public folder that you have configured as the message archive location is no longer a valid location. For example, this issue may occur if the message archive mailbox or the public folder has been deleted. Cause 2 - This issue may occur if one or more of the Exchange 2000 Server computers or the Exchange Server 2003 computers does not have sufficient permissions to obtain the attributes of the recipients.
- AIS Monitoring Platform has discovered offline address book failure in Outlook. Exchange cannot find details, address, or display templates because of an incorrect legacyExchangeDN value. During an unsuccessful installation of or removal of Exchange, orphaned Display- s were left in the container. This issue may also occur if the OAL does not successfully locate a system folder to replicate its contents. This behavior occurs because the address list must be removed from the OAL before the address list object is deleted. When you delete an address list object, the link to the OAL object in the address list is not removed. The event is logged when you try to access a deleted object on the server.
- AIS Monitoring Platform has discovered that the Exchange Recipient Update Service failing to stamp proxy address (email address) on newly created object in Active Directory. The issue can occur because of an invalid or missing third-party e-mail address generator. When the Microsoft Exchange System Attendant service starts, it tries to load an address generation .dll file for each address type that the Recipient Update Service requires to generate the third-party proxy address. If the System Attendant cannot load the .dll file for any address type, the Recipient Update Service does not process the accounts.
- AIS Monitoring Platform has discovered WMI issues on Exchange Server. WMI errors may cause issues related to Admin console not opening and some issues related to service failures. This issue can occur if the Microsoft Exchange 2000 Server namespace or the Microsoft Exchange Server 2003 namespace has become unregistered in Microsoft Windows Management Instrumentation (WMI) on the system.
- AIS Monitoring Platform has observed problem DSACCESS issue becuase Exchange security groups do no have the appropriate user rights to enable the Directory Service Access (DSAccess) component to communicate with Active Directory.
- AIS Monitoring Platform has discovered public folder hierarchy error in Exchange System Manager. This issue occurs if the ExchangeApplicationPool is deleted from the application pools in Internet Information Services (IIS). To resolve this problem, re-create the ExchangeApplicationPool application pool. Then, assign the appropriate virtual directories to use the ExchangeApplicationPool application pool.
- AIS Monitoring Platform has discovered failures for Exchange ActiveSync and OMA when form bases authenticaiton is enabled on Exchange 2003 Server. Exchange Server ActiveSync and Exchange Outlook Mobile Access (OMA) use the Exchange virtual directory to access OWA templates and DAV on Exchange back-end servers on which the user’s mailbox is located. Server ActiveSync and OMA cannot access this virtual directory if either of the following conditions is true: 1. The Exchange virtual directory on an Exchange back-end server is configured to require SSL. 2. Forms-based authentication is enabled. This issue does not occur when you enable these settings on the /Exchange virtual directory on a front-end server.
- AIS Monitoring Platform has observed that Virtual memory necessary to run your Exchange server is fragmented in such a way that normal operation may begin to fail. It is highly recommended that you restart all Exchange services to correct this issue.
- Saaz Intelliscript has observered issue with Exchange 2007 Mailbox database is unable to satisfy session request. This Error event indicates that the parameter msExchESEParamMaxSessions may be set too low for the current level of activity on the server.
- This alert condition indicates that the Exchange Backup Verification check failed. Exchange online backup is an effective instrument to create reserve copies of all emails, contacts, calendar notes and other data stored on Microsoft Exchange servers and transfer all this critical data to secure storage. The recommended method is to back up the Exchange Server online. An online backup can back up the Exchange Server databases, interrupting Exchange services.
- This alert condition indicates that the Exchange 2003 Std SP2 database size is nearing the threshold limit. An Exchange database defragmentation is required. Database Size Limit Configuration and Management Prior to Microsoft Exchange Server 2003 Service Pack 2 (SP2): There was no method to configure database size limits for Exchange Server 2003. Exchange Server 2003 SP2 introduces the following new features: For the Standard Edition, the default configured database size limit will now be 18 GB, a 2 GB addition to the previous limit, with a new maximum size of 75 GB. For the Enterprise Edition, there is no default configured database size limit, and no software set maximum size. Both versions of Exchange Server 2003 with SP2 have the ability to configure a limit, a warning threshold, and a warning interval set through registry keys. A size check done against the database now uses the logical database size. Empty or white space in the database does not count against the configured database size limit. Therefore, no offline defragmenting is required for a recovery exceeding the configured or licensed database limits. Limit checks, done at regular intervals, are now controlled by the store process instead of JET. The default time interval is 24 hours and this interval is configurable through the registry.
- Saaz IntelliScript has discovered that Outlook Web Access is not available for one of the mailboxes in a mailbox database.
- Saaz IntelliScript has observed that the WebReady Document Viewing manager was unable to access the temporary folder.
- AIS Monitoring Platform has discovered DNS communication failures between Exchange Server and domain Controller. This indicates that the Microsoft Exchange server that logged this event is not connected to the local area network. This may occur when the network adapter installed on this server is either disabled or not working. To resolve this error, make sure that the server that logged this event is connected to the local area network. Additionally, make sure that the following Exchange Management Shell cmdlet returns the IP address of one or more DNS servers.
- AIS Monitoring Platform has discovered that Microsoft Exchange could not read the server configuration. The Microsoft Exchange Credential Service will be stopped.
- Saaz Intelli Script has discovered error in your Outlook Web Access configuration. The authentication type specified in the Web.config file is not correct. This Error condition will occur if the wrong authentication type is specified in the Web.config file. The authentication type must be Windows.
- Saaz IntelliScript has observed that the Microsoft Exchange Autodiscover service was unable to process anonymous requests from an Autodiscover client, for example, an Outlook client. An invalid Autodiscover site configuration and an anonymous client request could cause this error. ‘HostName’ in the error message text refers to the Domain Name System (DNS) name of the remote client.
Exchange 2007-and-2010 The Connection Between The Client Access Server And The Mailbox Server Failed
- Saaz Interlliscript has detected connection issue between the Client Access server and the Mailbox server, this Warning indicates that Exchange ActiveSync has temporarily detected a connection problem between the computer that is running the Mailbox server role and the computer that is running the Client Access server role. Exchange ActiveSync will retry ActiveSync operations between the Client Access server and the Mailbox server.
Exchange 2007-and-2010 Edge Transport Exchange Credential Service Was Unable To Read The Server Configuration
- AIS Monitoring Platform has discovered that Microsoft Exchange could not read the server configuration because the directory is unavailable. The Microsoft Exchange Credential Service will be stopped.
Exchange 2010 Average Time For Reading -and- Writing Data To And From The Exchange Active Database File Is Delayed
- AIS Monitoring Platform has observed that average time for reading / Writing data to and from the active database file is delayed these monitoring instances are related to the storage. The focus is generally on storage response times. Impact : Users may experience slow system performance and message delivery delays.
Exchange 2010 The Client Access Server Cannot Proxy The Exchange ActiveSync Client Request To The Exchange Server
- AIS Monitoring Platform has observed the Client Access server cannot proxy the Exchange ActiveSync client request to the Exchange server . For this to work, Integrated Windows authentication must be configured on the Microsoft-Server-ActiveSync virtual directory on the Exchange server.
- AIS Monitoring Platform has detected the database engine attempted a clean write operation of database Drive. This action was performed in an attempt to correct a previous problem reading from the page. Cause : This can also be hardware related. Might be a temporary performance issue if the I/O is overloaded– for example during backups and maintenance or Antivirus scans .
- AIS Monitoring Platform has detected Log File Integrity Check Drive:LogFile path: The log file LogFile Path is damaged, invalid, or inaccessible and cannot be used. If this log file is required for recovery, a good copy of the log file will be needed for recovery to complete successfully.
- AIS Monitoring Platform has discovered that the database backup is ending and not all data in the file has been read. Note the filename and number of bytes that were read successfully. Your database might not have been completely backed up. If restore needs to be performed for any users emails from the latest backup, it wont be available due to exchange backup failure.
- AIS Monitoring Platform has discovered that the backup process stopped because the database is not responding. If restore needs to be performed for any users emails from the latest backup, it wont be available due to exchange backup failure.
- AIS Monitoring Platform has discovered that an error occurred during the online Exchange-aware backup of an Exchange store database. This Error signifies a checksum error in the SLV file during backup, where SLV stands for streaming, or .stm file. If restore needs to be performed for any users emails from the latest backup, it wont be available due to exchange backup failure.
Exchange Backup Has Stopped Due To Account Performing The Backup Does Not Have Enough Permission To Perform The Backup
- AIS Monitoring Platform has discovered that the file Cannot be access - the file is locked or in use. This error can occur if the account performing the backup does not have enough permissions to perform the backup. This impact the backup to fail.
- AIS Monitoring Platform has discovered that Exchange backup has stopped due to Antivirus file level exclusion not made This indicates Backup callout of sequence. This is a generic error with several causes and it has been seen when antivirus software is running on the server and scanning the folder of affected databases. The error has been seen when third-party backup software is running on the server and a problem with the software is causing the error.
- AIS Monitoring Platform has discovered Checksum error in log file during backup. This indicates a corrupt transaction log file. A backup cannot be made of a corrupt log file and the backup will fail. A checksum ESE error indicates a hardware root cause and is caused by hardware, controller, or file system-level problems related to hardware.
- AIS Monitoring Platform has discovered during the online Exchange-aware backup of an Exchange Information Store database where the backup fails due to hardware issues. This error indicates a hardware-related root cause. If restore needs to be performed for any users emails from the latest backup, it wont be available due to exchange backup failure.
- AIS Monitoring Platform has discovered Exchange Database Dismount by administrator. This impact the exchange store to dismount and mail flow stops. This might be also due to the maintainance activity that has been carried by the administrator on the exchange database. Impact : Email flow will be stopped.User will not be able to access their mailboxs.
- This alert condition indicates low disk space on the Exchange server. This may cause Exchange services to stop and the Exchange database to dismount. End users will be unable to send/receive emails and mail flow will stop.
- AIS Monitoring Platform has discovered high number of outstanding requests queued for virus scanning on exchange server. This can cause exchange performance issues. Decreased in server performance, usually caused by a CPU bottleneck. Larger than usual server load. An out-of-date virus scanning engine. An incorrectly configured virus scanning engine. If this is consistently high consider a hardware upgrade.
- AIS Monitoring Platform has discovered high number of threads waiting to complete an update to the exchange database by writing their data to the log. If the value of the Log Threads Waiting performance counter is too high, the log may be a bottleneck for other transactions.
- AIS Monitoring Platform has discovered that the exchange backup failed because a file is missing. If the missing file is a log file, you will not be able to perform an incremental backup. Impact : If restore needs to be performed for any users emails from the latest backup, it wont be available due to exchange backup failure.
- AIS Monitoring Platform has discovered that the LDAP read OR Search Time is too high on the exchange server. The LDAP Read shows the time in milliseconds that a Lightweight Directory Access Protocol (LDAP) read request takes to be fulfilled. The average value should be under 50 milliseconds. Maximum values should not exceed 100 milliseconds. The LDAP Search Time shows the time in milliseconds that a Lightweight Directory Access Protocol (LDAP) search request takes to be fulfilled. The average value should be under 50 milliseconds. Maximum values should not exceed 100 milliseconds.
- AIS Monitoring Platform has discovered that the LDAP Search timed out on exchange server. The LDAP Searches timed out per minute performance counter shows the number of LDAP search requests that timed out during the last minute. The average value should be less than 10 and the maximum value should not exceed 20. This alert indicates that more than 10 LDAP searches per minute timed out for five minutes. This can be caused by a network connectivity loss between the Microsoft Exchange Server computer and the Active Directory directory service domain controller, a problem with the domain controller computer, or severe performance problems.
- AIS Monitoring Platform has discovered that the number of logs records that cannot be written because the buffers are full - Note that Exchange Server 2000 defaults to 84 buffers whilst Exchange Server 2003 defaults to 512. If this is not the case then this might impact the slow exchange performance.
- AIS Monitoring Platform has discovered exchange messages Queued For Submission. The Submission Queue Length performance counter measures the number of messages currently in the submission queue. Messages in this queue are in a retry state because an issue prevented their submission to the categorizer. If the issue is transient, a subsequent attempt to submit the message may be successful. A sustained high Submission Queue Length value may indicate that an excessive amount of inbound messages have over loaded the categorizer. It may also indicate that there is an issue with message categorization. Message resubmission sends undelivered messages back to the Submission queue to be reprocessed by the categorizer.
- AIS Monitoring agent has detected Online Maintenance task Interrupted and Terminated. Exchange has an Online Maintenance task that runs every night. This option is not Online Defragmentation, but is rather Database Checksumming. Cause: Insufficient memory or schedule time. Impact: Database issue may lead to corruption or data loss.
- AIS Monitoring Platform has discovered exchange Public Folder messages queued For submission. The Messages Queued for Submission indicates the number of messages in the mailbox store that are ready to be sent and are waiting to be submitted to a transport server. This alert indicates that that the number of messages in the mailbox store that are queued for submission to a transport server has been greater than 20 for 15 minutes. This alert may be caused by problems with the Microsoft Exchange Mail Submission service on the Mailbox server, higher than normal load on the transport server, or a resource bottleneck on the transport server.
- AIS Monitoring Platform has discovered Exchange Database Dismount by administrator. This impact the Exchange store to dismount. This might be also due to the maintainance activity that has been carried by the administrator on the Exchange database.
- AIS Monitoring Platform has discovered high RPC Average Latency on exchange server. The RPC Averaged Latency performance counter records the average time, in milliseconds (ms), that it takes for the last 1024 packets to be processed. The latency represents how long it takes from the time the Store.exe process received the packet to the time it returned the packet. Although the RPC Averaged Latency performance counter data does not include network transit time, it does provide data about the shortest time period that client computers have waited for a response from the server. If the counter stays greater than 50 ms for more than several seconds, this indicates that the server is having difficulty keeping up with the load. As a result, users may experience delays when accessing their e-mail.
- This alert condition indicates that the system is low on Page Table Entries. Microsoft Windows Server 2003 and Windows 2000 Server can directly address up to 4 gigabytes (GB) of memory address space, regardless of how much physical RAM is installed. From the process perspective, each element of virtual address conceptually refers to a byte of physical memory. It is the responsibility of the Virtual Memory Manager (VMM) (in conjunction with the processor memory management unit (MMU)) to translate or map each virtual address into a corresponding physical address. The VMM performs the mapping by dividing the RAM into fixed-size page frames, creating system PTEs to store information about these page frames, and mapping them. System PTEs are small kernel-mode buffers of memory that are used to communicate with the disk I/O sub-system and the network. Each PTE represents a page frame and contains information necessary for the VMM to locate a page.
- AIS Monitoring Platform has discovered Exchange Store named property issue for Database. In an Exchange Server 2007 environment, a named property that is used to map X-headers during a message is processed at the mailbox store level. However, the named property has a size restriction. When many X-headers are promoted to named properties and the quota limitation is reached, unexpected problems occur.
- AIS Monitoring Platform has discovered suspected Memory Leak issue on exchange server. This indicates that the Exchange Server is running out of Nonpaged pool Memory, due to which the users may face performance issues. As a workaround you may try restarting the server.
Exchange Transaction Log Sequence Numbers For Exchange Instance Have Almost Been Completely Consumed
- This Error event indicates that there are approximately 131,000 log file names remaining. The maximum number of transaction log files that can be generated in a single sequence is 2,147,486,647 (0x7FFFFFFF). Typically, it will take dozens to hundreds of years of operation before this many log files will be generated. You can calculate how long it will take you to exhaust the remaining logs by determining how many logs are generated on a typical day and then dividing 131,000 by that number for an approximate number of days remaining. This calculation will be a very rough estimate and is only valid the first time the event occurs. However, you should immediately schedule a maintenance window where you can resolve the problem and prevent the storage group from disconnecting on its own when the available log file names are exhausted.
- This alert condition indicates that the Exchange VM Largest Block Size is low. This size is determined when AIS Monitoring agent queries the Active Directory directory service to determine the mailbox count for each mailbox store. The count of this attribute represents the number of mailboxes on the mailbox store. If the query finds the value for the VMLargestBlockSize is greater than 0 but less than 50000001 on an Exchange Server computer with more than 20 mailboxes, this error message is displayed. Among other things, Exchange Server uses virtual memory to store messages when you convert them between MIME and MAPI formats, and as a buffer when committing messages from the transaction log and committing to the store. Frequently, these operations require large contiguous chunks of virtual memory to complete quickly and efficiently. If this warning has been displayed, the virtual memory on the Exchange computer is depleted to less than 150 MB of contiguous space. This is known as virtual memory fragmentation. If the virtual memory depletes too much, you may start to see error messages in the event log (Event ID 9582), which are virtual memory errors. If virtual memory is low enough, you will see Event ID 12800, which indicates that messages are not being delivered because there is insufficient memory to process them.
- AIS Monitoring Platform has discovered that the exchange server is experiencing heavier than normal load and that an increase in RPC latencies or RPC thread exhaustion. This issue can manifest itself as mail clients experiencing slowdowns or by the appearance of the Cancel Request dialog box.
- AIS Monitoring Platform has discovered that the RPC averaged latency is high on exchange server. The RPC Averaged Latency counter displays the average time that it takes the server to respond to client requests. The value of the counter is typically less than 50 milliseconds in typical operations. If the value is consistently more than 50 milliseconds with Outlook client when most of the users are in Online Mode, this means that the Information Store is taking a long time to process user requests. If most Outlook users are in Cached Mode, this threshold increases to 100 milliseconds. Typically, if the Information Store is taking a long time, there is a disk bottleneck. Users will experience performance problems.
- AIS Monitoring Platform has discovered High MAPI requests being serviced by the Microsoft Exchange Information Store service. When using Microsoft Office Outlook in MAPI mode, clients actions in Outlook translate to remote procedure calls (RPCs) between the clients and the server. If the user is running in online mode, these