Critical Non Impact


Access Of Outlook Web Access Cause Exchange Store Exe Process To Stops Respond

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.

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.

Backup Log File Contains A Checksum Error

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.

Calender Meeting Request Issue In OWA Or In Non MAPI Clients

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.

Database Online Maintenance Skipped The Pages Performance Issue May Observed

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.

Database Page Read Failed Verification Due To A Page Checksum Mismatch

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.

E Mail Messages May Be Stuck In The Categorizer Component

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.

EdgeTransport Exe File Of Exchange 2007 Servers Crashes Continuously

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.

Exchange A Single MAPI Session Has Exceeded The Maximum Number Of Objects Of A Given Type

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.

Exchange Defragmentation Required

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.

Exchange Domain Controller Servers In Use Are Not Responding

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.

Exchange Error Updating Public Folder With Free/busy Information On The Server

AIS Monitoring Platform has detected error updating public folder with free/busy information on virtual machine Machine Name. The error number is 0x80070005.

Exchange Evaluation Period For Exchange Server Has Expired

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.

Exchange Named Properties Or Replica Identifiers Are Depleted For An Exchange Database

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.

Exchange Process For Application Pool Encountered An Error

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.

Exchange RPC Errors Or Latency Warnings Is Above Threshold

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.

Exchange The Exchange ActiveSync Doesn't Have Enough Permissions

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.

Exchange Third Party AntiVirus API Transport Scanning On The Exchange Server Interrupting Mail Flow

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.

Exchange 2000 Virtual Memory Fragmentation Issue Detected

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.

Exchange 2000 2003 Important Transport Errors Rule : 2

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.

Exchange 2000 2003 Messages Awaiting Directory Lookup SMTP Queue

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.

Exchange 2000 / 2003 Offline Address Book Failures

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.

Exchange 2000 /2003 Exchange Recipient Update Service Does Not Stamp Proxy Addresses

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.

Exchange 2000/ 2003 WMI Errors On Exchange Server

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.

Exchange 2000/2003 Exchange Security Groups Do No Have Rights To (DSAccess) Component

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.

Exchange 2003 Error While Expanding Public Folder Heirarcy

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.

Exchange 2003 Exchange ActiveSync And OMA Errors Occur When SSL Or Forms Based Authentication

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.

Exchange 2003 Virtual Memory Fragmentation Issue Detected

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.

Exchange 2003 / 2007 No Database Session Was Available To Satisfy A Request

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.

Exchange 2003 Full Backup Not Occurred For Last 07 Days

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.

Exchange 2003 Std SP2 Database Size Nearing Threshold Limit , Defrag Required

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.

Exchange 2007 Outlook Web Access Is Not Available For One Of The Mailboxes In A Mailbox Database

Saaz IntelliScript has discovered that Outlook Web Access is not available for one of the mailboxes in a mailbox database.

Exchange 2007 WebReady Document Viewing Manager Was Unable To Access The Temporary Folder

Saaz IntelliScript has observed that the WebReady Document Viewing manager was unable to access the temporary folder.

Exchange 2007 / 2010 No DNS Servers Could Be Retrieved From Network Adapter

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.

Exchange 2007 Edge Transport Exchange Could Not Read The Server Configuration

AIS Monitoring Platform has discovered that Microsoft Exchange could not read the server configuration. The Microsoft Exchange Credential Service will be stopped.

Exchange 2007/2010 Error In Your Outlook Web Access Configuration

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.

Exchange 2007/2010 Microsoft Exchange Autodiscover Service Configuration Is Not Secure

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/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/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 / 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.

Exchange 2010 The Database Engine Attempted A Clean Write Operation On Page Of Database Drive

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 .

Exchange 2010 The Log File LogFile Path Is Damaged, Invalid, Or Inaccessible And Cannot Be Used

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.

Exchange Backup Has Stopped As Its Not Able To Read All Data In The File Backup Fails

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.

Exchange Backup Has Stopped Because The Database Is Not Responding

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.

Exchange Backup Has Stopped Due Checksum Error In SLV File During Backup Backup Fails

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.

Exchange Backup Has Stopped Due To Antivirus File Level Exclusion Is Not Made Backup 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.

Exchange Backup Has Stopped Due To Corrupt Transaction Log File Backup Fails

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.

Exchange Backup Has Stopped Due To Hardware Problems Related Root Cause Backup Fails

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.

Exchange Database Manual Store Dismount

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.

Exchange Health Check Low Diskspace On Exchange Drive

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.

Exchange High Number Of Outstanding Requests Queued For Virus Scanning

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.

Exchange High Number Of Threads Waiting To Complete An Update To The Database

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.

Exchange Incremental Backup Has Failed Because A Require File Is Missing Backup Failed

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.

Exchange LDAP Read OR Search Time Is Too High

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.

Exchange LDAP Search Timed Out

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.

Exchange Logs Records Cannot Be Written Because The Buffers Are Full

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.

Exchange Messages Queued For Submission

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.

Exchange Online Maintenance Task Interrupted And Terminated

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.

Exchange Public Folder Messages Queued For Submission

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.

Exchange Public Store Database Manual Store Dismount

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.

Exchange RPC Average Latency Is High

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.

Exchange Server Number Of Free Page Table Entries Is Low Which Can Cause System Instability

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.

Exchange Store Named Property Issue For Database

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.

Exchange Suspected Memory Leak Found

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.

Exchange VM Largest Block Size Is Low

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.

Heavier Than Normal Load And That An Increase In RPC Latencies

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.

HIGH Exchange RPC Averaged Latency On Exchange 2007

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.

High MAPI Requests Being Serviced By The Microsoft Exchange Information Store Service

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 RPC calls occur synchronously. Any delay by the server in fulfilling these synchronous requests directly affects user experience and the responsiveness of Outlook. MSExchangeIS\RPC Requests indicates the number of MAPI RPC requests presently being serviced by the Microsoft Exchange Information Store service. The Microsoft Exchange Information Store service can service only 100 RPC requests (the default maximum value, unless configured otherwise) simultaneously before rejecting client requests. Generally, spikes in RPC requests that do not increase RPC operations/sec indicate that there are bottlenecks preventing the store from fulfilling the requests in a timely manner.

HIGH Number Of Messages In The Largest Delivery Queues

AIS Monitoring Platform has discovered high number of messages in the largest delivery queues. The Largest Delivery Queue Length performance counter represents the number of e-mail messages that are queued to a given Exchange Hub Transport server or Edge Transport server. This alert indicates that Largest Delivery Queue Length has exceeded 50 messages for five minutes. When this value is high, the server cannot establish a SMTP session to the other Hub Transport or Edge Transport server. Other symptoms you may experience when this threshold is reached are reduced intra-site, inter-site, and external mail flow. This alert may be caused by one or more of the following conditions: 1. Problem with a specific Hub Transport server or Edge Transport server. For example, one or more required services may not be running. 2. Issues with network connectivity, routers, or firewalls.

High Numbers Of Messages In The Active Mailbox Queues

AIS Monitoring Platform has discovered high numbers of messages in the active mailbox delivery queues. Active Mailbox Delivery Queue Length is the number of items in the active mailbox queues. This alert indicates that more than 50 messages have been in the Active Mailbox Delivery Queue for more than 15 minutes. This indicates that the messages are backing up in one or more queues on a server. This might impact mail flow interruptions in the Exchange environment.

Large Number Of Messages Queued To Receive

AIS Monitoring Platform has discovered that the large number of Messages Queued to receive on exchange server. The Receive Queue Size performance counter indicates the number of replication messages in the public store that have been delivered to the store but are waiting in the receive queue to be processed. This alert indicates that the messages have been waiting in the public store receive queue for a long duration. This may be caused by higher than normal load, or a resource bottleneck. Possible bottlenecks include disk reads or writes, processor time, available memory, and network configuration.

LDAP Operation Takes Longer Than The Specified Threshold To Complete And IT Is Considered A Long Running Operation

AIS Monitoring Platform has discovered that the LDAP Search Time shows the number of Lightweight Directory Access Protocol (LDAP) operations per minute that took longer than the specified threshold. The default threshold is 15 seconds. When an LDAP operation takes longer than the specified threshold to complete, it is considered a long running operation. This alert indicates that there were 50 or more long running LDAP operations per minute for 15 minutes. This alert may be caused by performance problems on your domain controllers or network congestion.

Low Memory Condition Exchange Performance Issue

AIS Monitoring Platform has discovered that there is an unexpected error while reading the file due to this there is no more available memory and the read operation has failed. Users may face delay response from Exchange server due to slow performance issues.

Messages Queue In The Public Store Receive Queue

AIS Monitoring Platform has discovered that the messages are queued in the public store receive queue. The Receive Queue Size indicates the number of replication messages in the public store that have been delivered to the store but are waiting in the receive queue to be processed. This alert indicates that more than 10 messages have been waiting in the public store receive queue for 15 minutes. This alert may be caused by higher than normal load, or a resource bottleneck.

Messages Stay In The Local Delivery Queue On An Exchange Server

AIS Monitoring Platform has discovered increase in local delivery queue on exchange server. There can be several causes for this type of error. What the underlying problem is will be determined by the name of the function indicated in the message and also the error codes noted. You can use the ERROR.EXE program (located in the Support\Utils\I386 folder of the Exchange Server CD) to get more information about the error code. Information store corruption is also suspected.

Microsoft Connector For POP3 Mailboxes Not In Running State

This alert condition indicates that the Microsoft Connector for POP3 Mailboxes service is not running.

Microsoft Connector For POP3 Mailboxes Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Connector for POP3 Mailboxes service terminated unexpectedly.

Microsoft Exchange 2003 Cluster Server POP3 Server Crash

AIS Monitoring Platform has discovered that the SMTP has crashed in the cluster enviorment, this would result into a mail flow issue.

Microsoft Exchange 2003 Store Process Crash Intermittenly

AIS Monitoring Platform has discovered that the exchange information store crashes intermittenly and will also cause mail flow to stop. This issue may occur if you use a character that cannot be used when you configure the value of the AdditionalSafeURLScheme registry entry. For example, you use a comma.

Microsoft Exchange Compliance Service Not In Running State

Microsoft Exchange Compliance Service- Not In Running State

Microsoft Exchange Compliance Service Not In Running State [Unexpected]

Microsoft Exchange Compliance Service- Not In Running State [Unexpected]

Microsoft Exchange DAG Management Not In Running State

Microsoft Exchange DAG Management- Not In Running State

Microsoft Exchange DAG Management Not In Running State [Unexpected]

Microsoft Exchange DAG Management- Not In Running State [Unexpected]

Microsoft Exchange Directory Not In Running State

This alert condition indicates that the Microsoft Exchange Directory service is not running.

Microsoft Exchange Directory Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange Directory service terminated unexpectedly.

Microsoft Exchange Health Manager Recovery Not In Running State

Microsoft Exchange Health Manager Recovery- Not In Running State

Microsoft Exchange Health Manager Recovery Not In Running State [Unexpected]

Microsoft Exchange Health Manager Recovery- Not In Running State [Unexpected]

Microsoft Exchange IMAP4 Backend 2013 Not In Running State

This alert condition indicates that the Microsoft Exchange IMAP4 Backend 2013 service is not running.

Microsoft Exchange IMAP4 Backend 2013 Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange IMAP4 Backend 2013 service terminated unexpectedly.

Microsoft Exchange Mailbox Replication 2013 Not In Running State

This alert condition indicates that the Microsoft Exchange Mailbox Replication 2013 service is not running.

Microsoft Exchange Mailbox Replication 2013 Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange Mailbox Replication 2013 service terminated unexpectedly.

Microsoft Exchange POP3 Not In Running State

This alert condition indicates that the Microsoft Exchange POP3 service is not running.

Microsoft Exchange POP3 Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange POP3 service terminated unexpectedly.

Microsoft Exchange POP3 Backend 2013 Not In Running State

This alert condition indicates that the Microsoft Exchange POP3 Backend 2013 service is not running.

Microsoft Exchange POP3 Backend 2013 Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange POP3 Backend 2013 service terminated unexpectedly.

Microsoft Exchange Replication Not In Running State

This alert condition indicates that the Microsoft Exchange Replication service is not running.

Microsoft Exchange Replication Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange Replication service terminated unexpectedly.

Microsoft Exchange Throttling 2013 Not In Running State

This alert condition indicates that the Microsoft Exchange Throttling 2013 service is not running.

Microsoft Exchange Throttling 2013 Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange Throttling 2013 service terminated unexpectedly.

Microsoft Exchange Unified Messaging Call Router 2013 Not In Running State

This alert condition indicates that the Microsoft Exchange Unified Messaging Call Router 2013 service is not running.

Microsoft Exchange Unified Messaging Call Router 2013 Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange Unified Messaging Call Router 2013 service terminated unexpectedly.

Microsoft Outlook Corrupt HTML Messages Interfere With Searches

AIS Monitoring Platform has discovered the following log error is created ecCorruptData-MAPI_E_CORRUPT_DATA when the store process searching a folder encounters a corrupted HTML message in an Exchange Server 2007. The search only returns values found up to when it encountered the corrupted HTML message. This search logic failure causes fewer search results returned than should be expected.

Monitor Remote Queue Length Exchange 2000 2003

AIS Monitoring Platform has discovered an increase in remote queue length on exchange server. The SMTP Server\Remote Queue Length counter indicates the number of messages in the SMTP queue for remote delivery. As a general guideline, the maximum value should be less than 1,000. The queue should remain steady near its average with small variance. An increase in the remote queue length means that mail is not being sent to other servers. This failure to send mail can be explained by outages or performance issues with the network or remote servers. Those outages or performance issues prevent the network or remote servers from receiving the mail efficiently.

MS Exchange A Request To Write To The File ED/Log Has Not Completed For Long Time

AIS Monitoring Platform has discovered that an Exchange data read took longer than expected. However, The read was successful. Additional input/output (I/O) requests to this disk also take longer than expected to complete. The problem could be faulty hardware or that the server or disk subsystem is not configured correctly. Consequently, the Exchange server performance may slow down. Users may notice a delay in sending and receiving emails.

MS Exchange An Exception Occurred And Was Handled By Exchange ActiveSync

AIS Monitoring agent has discovered an exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case, Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization. Impact : Users will not be able to sync their devices, items will not be updated till the next synchronization.

MS Exchange An Internal Transport Certificate Expired

AIS Monitoring agent has observed issue that indicates the certificate that has expired. This condition indicates that the certificate that was used for internal trust on this computer has expired. Internal trust means that Microsoft Exchange Server uses a self-signed certificate for encryption. Impact : If the certificate is expired, users will still be able to send and receive emails but the emails will be non-encrypted between source and destination.

MS Exchange Backup Not Occurring From Last 7 Days

AIS Monitoring agent detected no exchange backup had occurred in last 7 days. On Exchange server it is important to take backup of Mailbox and Public folder databases. Backup activity also helps in truncating transaction log files which results in saving disk space, regular backup also helps in restore/recovery scenario’s. Impact: If Backup is not regular and circular logging is disabled, transaction logs will not be flushed. Which may result in Low disk space and database dismount related issues.

MS Exchange Cannot Access Their Mailbox Because The User's Mailbox Quota Has Been Exceeded

This alert condition indicates that a user cannot access their mailbox because the user’s mailbox quota has been exceeded.

MS Exchange DAG Failover Unexpectedly

AIS Monitoring agent has detected MS Exchange - DAG failover unexpectedly. Cluster node <###> was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster.

MS Exchange Database Corruption Detected, Unable To Read Pages

AIS Monitoring Platform has discovered that an Exchange Server database has suffered damage at the file system level. This may be caused due to the hardware problems or even due to the old firmware or device drivers. Glitches in hardware or bugs in firmware can cause data to be corrupted. Impact : This may impact the mail flow to stop.

MS Exchange Database Page Read Failed Verification Due To A Page Checksum Mismatch

AIS Monitoring agent 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 : When this problem occurs, you may experience one or more of the following symptoms: * Users cannot send or receive e-mail messages. *You cannot start Microsoft Outlook on your client computer. *Online backups fail to finish, and you receive a -1018 checksum error. *Online defragmentation reports a -1018 checksum mismatch error.

MS Exchange Database Seeding On DAG Fails

AIS Monitoring agent has discovered There were database availability check failures for database ### that may be lowering its availability. Impact : Dag database copy will not update

MS Exchange Eseutil Database Recovery/restore Failed With Unexpected Error

AIS Monitoring agent has detected Eseutil Database recovery/restore failed with unexpected error. The particular database page referenced within the Exchange store file (such as priv1.edb) is corrupt. Impact : Online backups/defragmentation may fail, Users may not be able to send or receive e-mail messages.

MS Exchange Exchange ActiveSync Device Requests For Your Users Are Being Blocked

AIS Monitoring Platform has observed Some Exchange ActiveSync device requests for your users are being blocked. Impact : Unable to sync and send emails form the mobile devices.

MS Exchange Exchange Server DAG Failover Successful

AIS Monitoring agent has detected sucessful failover of Database to passive node.

MS Exchange External Aggregate Delivery Queue Length (All External Queues) Is High

AIS Monitoring system has discovered that External Aggregate Delivery Queue Length (All External Queues) is high. Impact: Mail flow is delayed or stopped.

MS Exchange Installing Exchange On A Domain Controller Is Not Recommended

AIS Monitoring agent detected that the MS Exchange is installed on the domain controller, which is not recommended by Miicroosoft. Impact : MS Exchange may not work properly on the server.

MS Exchange Internal Aggregate Delivery Queue Length (All Internal Queues) Is High

AIS Monitoring system has discovered that Internal Aggregate Delivery Queue Length (All Internal Queues) is high. Impact: Mail flow is delayed or stopped.

MS Exchange Mail Submission Service Is Currently Unable To Contact Exchange Transport Service

AIS Monitoring agent has discovered the Microsoft Exchange Mail Submission Service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time. Impact : Mail flow will be stoped.

MS Exchange Mails May Stuck In Drafts Folder

AIS Monitoring system has discovered that a problem with server component states, mails may stuck in drafts folder. Impact: Mail flow will not work. Cause: Transport component issue.

MS Exchange Mapi Session Exceeded The Maximum Of Limit For Objects Of Type

AIS Monitoring agent has discovered users are Unable to access user mailbox through OWA.Mapi session ##### exceeded the maximum of 32 objects of type session. Cause : This issue occurs because the default maximum number of connections that an account can open was exceeded. Impact : Users will face issues accessing owa

MS Exchange Microsoft Exchange Replication Service, VSS Failure

AIS Monitoring agent has discovered MS Exchange transaction log files are growing rapidly. Impact : Exchange database may go down due to low disk space.

MS Exchange Mobile Users Are Unable To Sync Their Device Using Activesync

AIS Monitoring agent has discovered Exchange ActiveSync doesn’t have sufficient permissions to create the container under Active Directory user Active Directory operation failed. This error is not retriable. Impact : A user cannot synchronize a Microsoft Exchange ActiveSync (EAS) device for the first time.

MS Exchange Multiple Event Generated For Mid Tier Storage

AIS Monitoring agent has discovered Multiple event generated for Mid-Tier Storage. Impact : Users may get affected with client access role

MS Exchange Outlook Express Users Fail To Download An E Mail From Exchange Using POP IMAP Svc

AIS Monitoring agent has discovered that users connection to Exchange Server are failing to download email using Pop3 IMAP3 Service. Third party Anti Virus event sink registration can cause this issue. Impact: Users will face issues downloading emails.

MS Exchange Outstanding RPC Requests Reached Maximum Threshold

AIS Monitoring agent has discovered Outstanding RPC requests reached maximum threshold. The RPC Requests indicates the number of MAPI remote procedure call (RPC), or client, requests that are currently being processed by the Microsoft Exchange Information Store service. The average value of the RPC Requests performance counter should be under 30 at all times. By default, the maximum value for RPC requests is 100. Therefore, unless it is configured otherwise, the Microsoft Exchange Information Store service can service only 100 RPC requests at the same time before all new RPC operations will be rejected and users will not be able to connect to the server until the RPC requests drop below 100. The server will become unresponsive, mail flow may stop. The Outlook users may receive the RPC cancel Request dialog box. This error indicates that the server is experiencing a performance bottleneck or that a process has stopped responding. Impact: Outlook Users may face delayed connectivity problems with Exchange server.

MS Exchange Performance Issue A Request To Read Exchange Data From The Disk Succeeded But Took An Abnormally Long Time

AIS Monitoring agent has discovered that an Exchange data read took longer than expected. However, The read was successful. Additional input/output (I/O) requests to this disk also take longer than expected to complete. The problem could be faulty hardware or that the server or disk subsystem is not configured correctly. Consequently, the Exchange server performance may slow down. Users may notice a delay in sending and receiving emails. Impact : Performance issue may occur

MS Exchange Problem Loading A Certificate To Be Used For STARTTLS Purpose

AIS Monitoring agent has discovered problem loading a certificate to be used for STARTTLS Purpose. Generally this condition occurs if one or both of the following conditions is true: 1. The fully qualified domain name (FQDN) that is specified in the Warning event has been defined on a Receive connector or Send connector on a Microsoft Exchange Server. 2. Ccertificate is not enabled for the SMTP service Impact: SMTP connector may fail to support TLS connection.

MS Exchange The Database Engine Attempted A Clean Write Operation On Page Of Database Drive

AIS Monitoring agent 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 . Impact : Performance Issue is observed on Exchange Server.

MS Exchange The Indexing Of Mailbox Database Encountered An Unexpected Exception

AIS Monitoring agent has discovered that the indexing of mailbox database encountered an unexpected exception. Impact :This causes the search component to fail within mailbox.

MS Exchange The Microsoft Exchange Replication Service Requires The File Path For The Passive Copy Of The Database

AIS Monitoring agent detected that the Microsoft Exchange Replication Service requires the file path for the passive copy of the database. This Condition indicates that the Microsoft Exchange Replication (MSExchangeRepl) service cannot find the path of the database on the local continuous replication (LCR) storage group copy. This alert may occur when an LCR database copy path is accidentally cleared in the Active Directory directory service. The database copy path cannot be deleted through the GUID or by using a cmdlet. The condition is triggered when Microsoft Exchange Replication service starts and cannot find the path of the LCR database copy. Impact: Replication engine will not able to find the path of the LCR database copy.

MS Exchange The Outlook Web Access Proxy Request Failed Because Of A Secure Sockets Layer (SSL) Configuration Issue On The Destination Outlook Web Access Virtual Directory

AIS Monitoring agent hase detected the Outlook Web Access proxy request failed because of a Secure Sockets Layer (SSL) configuration issue on the destination Outlook Web Access virtual directory. This Error event indicates the computer that is running the Client Access server role could not proxy a Microsoft Office Outlook Web Access request from one Client Access server to a Client Access server that is located in a different Active Directory site. Impact : The user referenced in the event description could not use Outlook Web Access to log on to their mailbox through the Client Access server in a different site.

MS Exchange The Setting In The Web Config File Was Not Valid

AIS Monitoring agent has discovered the setting in the Web.Config file was not valid. Impact: The Outlook Web Application (OWA) will be inaccessible to users.

MS Exchange The Transport Process Failed During Message Processing

AIS Monitoring agent has detected the transport process failed during message processing with the following call stack: System.InvalidOperationException: Malware agent is invoking async completion twice. Impact : Mail flow may stop.

MS Exchange The User Mailbox Has Exceeded The Maximum Mailbox Size

AIS Monitoring agent has discovered that the mailbox for #### has exceeded the maximum mailbox size. This mailbox cannot send or receive messages. Incoming messages to this mailbox are returned to sender. Impact: This mailbox cannot send or receive messages.

MS Exchange Transport Authentication Failed With An Error

AIS Monitoring agent has detected Transport authentication failed with an error. Impact : Some e-mail messages are stuck in a remote delivery queue that should have been transferred to another internal Exchange server in the Exchange organization.

MS Exchange Unable To Connect Using Exchange ActiveSync Due To Exchange Resource Consumption

AIS Monitoring system has discovered failed connection using Exchange ActiveSync due to Exchange resource consumption. Impact: Users not being able to synchronize their devices with Exchange.

MS Exchange User Cannot Synchronize Their Mobile Phone

AIS Monitoring Agent has discovered that mobile devices could no longer synchronize with a mailbox. Impact : Users will not be able to sync their mobiles

MS Exchange AntispamUpdate Not In Running State

This alert condition indicates that the MS Exchange AntispamUpdate service is not running.

MS Exchange AntispamUpdate Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange AntispamUpdate service terminated unexpectedly.

MS Exchange EdgeSync Not In Running State

This alert condition indicates that the MS Exchange EdgeSync service is not running.

MS Exchange EdgeSync Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange EdgeSync service terminated unexpectedly.

MS Exchange MailboxAssistants Not In Running State

This alert condition indicates that the MS Exchange MailboxAssistants service is not running.

MS Exchange MailboxAssistants Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange MailboxAssistants service terminated unexpectedly.

MS Exchange Pop3 Not In Running State

This alert condition indicates that the MS Exchange Pop3 service is not running.

MS Exchange Pop3 Not In Running State [Unexpected]

This alert condition indicates that the Microsoft Exchange Pop3 service terminated unexpectedly.

MSExchange AD Process LDAP Read And Search Time Is Too High

AIS Monitoring Platform has discovered that the MSExchange AD Process LDAP read and Search Time is too high. LDAP long running operations/Min is the number of LDAP operations on this domain controller that took longer than the specified threshold per minute (default threshold is 15 seconds).

Number Of Messages In A Retry State In The Remote Delivery Queues

AIS Monitoring Platform has discovered increase in number of messages in a retry state in the remote delivery queues. The Retry Remote Delivery Queue Length performance counter measures the number of messages currently in the retry remote delivery queue. Messages in this queue are in a retry state because an issue prevented their delivery. If the issue is transient, a subsequent reattempt to send the message may be successful. Messages that cannot be successfully delivered are subject to various retry, resubmit, and expiration deadlines based on the message’s source and destination. Retry is a renewed connection attempt with the destination domain, smart host, or Mailbox server. Resubmit is the act of sending messages back to the Submission queue for the categorizer to reprocess. The message is said to time-out, or expire, after all delivery efforts have failed during a specified period of time. After a message expires, the sender is notified of the delivery failure. Then the message is deleted from the queue.

Outlook Web Access Response Time Is HIGH

AIS Monitoring Platform has discovered that the Outlook Web Access Response Time is High. This condition indicates that the average time (in milliseconds) that elapsed between the beginning and end of an OEH or ASPX request. It is used to determine the latency that a client is experiencing.

Outlook Web Access Was Unable To Load Some Of Its Configuration Settings

Outlook Web Access was unable to read the configuration settings of the virtual directory indicated by the error. OR Kerberos authentication has been misconfigured on the target Client Access Server or that the target Client Access server has not been configured to allow Kerberos authentication.

Outstanding RPC Requests Reached Maximum Threshold

AIS Monitoring Platform has discovered Outstanding RPC requests reached maximum threshold. The RPC Requests indicates the number of MAPI remote procedure call (RPC), or client, requests that are currently being processed by the Microsoft Exchange Information Store service. The average value of the RPC Requests performance counter should be under 30 at all times. By default, the maximum value for RPC requests is 100. Therefore, unless it is configured otherwise, the Microsoft Exchange Information Store service can service only 100 RPC requests at the same time before all new RPC operations will be rejected and users will not be able to connect to the server until the RPC requests drop below 100. The server will become unresponsive, mail flow may stop. The Outlook users may receive the RPC cancel Request dialog box. This error indicates that the server is experiencing a performance bottleneck or that a process has stopped responding.

Paging File High Utilization Observed On Exchange

AIS Monitoring Platform has discovered high usage of paging file on exchange server. This indicates that the page file is not set properly on the exchange server or less amount of physical memory (RAM) is installed on the server which might impact slow performance of exchange. To increase the performance of server either size the paging file properly or increase the RAM on the server.

Possible Exchange Mail Flow Issue A Gap In The Transaction Log File Sequence Was Detected

AIS Monitoring Platform has discovered that the Exchange has detected a gap in the log file sequence. This is due to a missing log file which may cause Mail Flow Down. User might face problems while sending and receiving emails.

Read Operation Failed Multiple Times Before Finally Succeeding Performance Issue

AIS Monitoring Platform has discovered that a read operation failed multiple times before finally succeeding. Warnings such as these can be a precursor to a failure in the storage subsystem containing this file. This may impact exchange performance issue. User might face delay in response from exchange server.

Recurring Meeting Request Of Calendar Items Causing EdgeTransport Exe To Crash During MIME Conversion

AIS Monitoring Platform has discovered that on a computer that is running Microsoft Server Exchange 2007 Service Pack 1 (SP1), you have a MIME message that contains iCAL items for a recurring meeting. If the recurring meeting has more than 999 occurrences, the EdgeTransport.exe process crashes.

Reverse Non Delivery Report (NDR) Attack Suspected On Exchange Server

AIS Monitoring Platform has discovered Spam attack on your Exchange Server. This issue occurs if your computer is the target of a reverse non-delivery report (NDR) attack. The Microsoft Exchange Server queues contain many outgoing messages that are waiting to be delivered to external addresses. When you visit the Internet from the Windows computer that is on the local area network (LAN), Internet access is very slow. The Store.exe process and the Inetinfo.exe process use lots of CPU time and lots of available memory. If you stop the Simple Mail Transfer Protocol (SMTP) service, Internet access times are faster, and the Store.exe process and the Inetinfo.exe process return to their typical levels of CPU and memory usage. The drive that contains the BadMail folder runs out of space.

Some Messages Are Stuck In The Outbox Folder Or The Drafts Folder On A Computer That Is Running Exchange Server 2007

AIS Monitoring Platform has discovered that on a computer that is running Exchange Server 2007 Service Pack 1 (SP1), some messages are stuck in the Outbox folder or the Drafts folder, and are not picked up intermittently. There is a corrupted internal folder ID or a message ID in the Exchange Server 2007 SP1- based server that causes this problem.

System Attendant Not Responding During Cluster Failover

AIS Monitoring Platform has discovered that the System Attendant is not responding during Cluster Failover. When the System Attendant resource goes offline, it tries to shut down any child tasks. One child task tries to contact all Public Folder servers in the top level hierarchy. If there are many public folder servers in the Exchange organization, this procedure takes a long time. Therefore, the SA resource times out. Because of this, the SA resource may stay in the Offline Pending state on the failed node of the cluster or it may stay in the Online Pending state on the node to which it is failing over.

System Attendant Task Blocked To Generate Offline Address Book

AIS Monitoring Platform has discovered that Exchange System Attendant tasks has been blocked to generate Offline address book. The System Attendant has been taking too long to perform some task. This problem occurs when the Microsoft Solution for Hosted Messaging and Collaboration deployment tool sets an incorrect registry value. If this registry value is set incorrectly, the Exchange System Attendant Service generates offline address book files continually.

The Retry Mailbox Delivery Queue Length Is Very HIGH

AIS Monitoring Platform has discovered that the Retry Mailbox Delivery Queue Length is very High. The Retry Mailbox Delivery Queue Length performance counter measures the number of messages currently in the retry mailbox delivery queue. Messages in this queue are in a retry state because an issue prevented their delivery. If the issue is transient, a subsequent attempt to send the message may be successful. Messages that cannot be successfully delivered are subject to various retry, resubmit, and expiration deadlines based on the message’s source and destination. Retry is a renewed connection attempt with the destination domain, smart host, or Mailbox server. Resubmit is the act of sending messages back to the Submission queue for the categorizer to reprocess. The message is said to time-out, or expire, after all delivery efforts have failed during a specified period of time. After a message expires, the sender is notified of the delivery failure. Then the message is deleted from the queue. In all three cases of retry, resubmit, or expire, you can manually intervene before the automatic actions are performed on the messages.

The Store Exe Process Crashes When You Use A WebDAV Application To Connect To Exchange Server

AIS Monitoring Platform has discovered that when you use a third-party application that connects to Exchange Server 2007 Service Pack 1 (SP1) by using the WebDAV protocol, the Store.exe process crashes on the Exchange Server 2007 SP1-based server.

There Is An Error In Your Outlook Web Access Configuration

This Error event will occur if the wrong authentication type is specified in the Web.config file. The authentication type must be Windows. This Error event can occur if Internet Information Server (IIS) has been used to configure the authentication settings for the Outlook Web Access virtual directory. Outlook Web Access authentication settings should be configured only by using the Exchange Management Console or the Exchange Management Shell. This Error event will occur if Outlook Web Access was unable to find its configuration in the Active Directory directory service. This could occur because of an error reading from Active Directory or because the object does not exist in Active Directory.

Total Number Of Messages Unreachable

AIS Monitoring Platform has discovered that the messages are increasing in the Unreachable Queue Length. The Unreachable Queue Length performance counter measures the number of messages currently in the retry mailbox delivery queue. Messages in this queue are in a retry state because an issue prevented their delivery. If the issue is transient, a subsequent attempt to send the message may be successful. Messages that cannot be successfully delivered are subject to various retry, resubmit, and expiration deadlines based on the message’s source and destination. Retry is a renewed connection attempt with the destination domain, smart host, or Mailbox server. Resubmit is the act of sending messages back to the submission queue for the categorizer to reprocess. The message is said to time-out, or expire, after all delivery efforts have failed during a specified period of time. After a message expires, the sender is notified of the delivery failure. Then the message is deleted from the queue.

Transport Layer Security Certificate Will Expire In Next 4 Days

Saaz IntelliScript has observed issue that indicates the certificate that is used for Transport Layer Security (TLS) on this computer will expire in next 4 days.

Transport Layer Security Certificate Will Expire Soon Or Already Expired

AIS Monitoring agent has detected an issue that indicates the certificate that is used for Transport Layer Security (TLS) on this computer will expire soon or already expired Impact: The certificate is about to expire. Exchange will continue to work as normal but users will receive an error message when accessing Outlook Web Access (OWA).

Unable To Process All Mailboxes Because Of Insufficient Time

This Condition indicates that one of the time-based Exchange Assistants did not process all the mailboxes for a given database within a specified time window. Each time-based Assistant deploys an Assistants Driver that periodically checks whether the current time is within in a specified time window. When the current time reaches the specified time window, the Assistants Driver invokes the corresponding time-based Assistant. The time-based Assistant then obtains a list of mailboxes from the database and tries to process them within the specified time window. This error may occur when the time-based Assistant does not process all the mailboxes because of insufficient time window. The Ticket description lists the number of mailboxes that were skipped because of insufficient time window

Unexpected Error Occurred While Reading The File Due To Incorrect API Parameter

AIS Monitoring Platform has discovered unexpected error occurred while reading the file due to Incorrect API parameter. This error generally means that the file size of the database is not a multiple of 4,096 bytes. It must be a multiple of 4,096 bytes, or 1 page. If it is not then Exchange performance issues can occur. This impact slow response from the exchange server and user may find delay in sending and receiving emails.

User May Experience Access Violation Error For Exchange Application

AIS Monitoring Platform has discovered that the users may experience Access violation error for Exchange Application. After you install security update 911567 on a server that is running Microsoft Exchange Server 2003, an application may encounter a 0xc0000005 access violation error. This problem occurs when the application uses Collaboration Data Objects for Exchange (CDOEX) and the Person.GetVCardStream method.

Windows Management Instrumentation(wmiprvse Exe) Process For Exchange Is Crashing

AIS Monitoring Platform has discovered that the Wmiprvse.exe process crashes on an Exchange 2003 server. This issue occurs because a thread tries to destroy a data object that is being used by another thread.

Last modified April 17, 2020