Critical Impact

Critical Impact Events and Alerts


Active Non Smtp Mailbox Delivery Queue For More Than 15 Minutes
    AIS Monitoring Platform has discovered increase in number of messages queued for delivery to a Non-SMTP transport. Active Non-Smtp Delivery Queue Length is the number of items in the active Non-Smtp queues. Non-Smtp Delivery Queue is associated with the queue for Foreign Connectors. A Foreign Connector is added by using the new-ForeignConnector cmdlet or by a third-party Exchange application. This alert indicates that more than 250 messages have been in the Active Non-Smtp Mailbox Delivery Queue for more than 15 minutes.
Checksum Error On A Database Due To Hardware Problems Mail Flow Down
    AIS Monitoring Platform has discovered that the Exchange database has suffered damage at the file system level. The root cause of this problem is frequently because of faulty hardware. This error is caused by a problem in the disk subsystem. The problem in the disk subsystem may be caused by defective disk drives, by outdated or incompatible disk drive firmware, or by outdated or incompatible controller firmware. Sometimes, too much heat around the disk drive subsystem components may cause this error. Damage may occur to the Exchange database in the following three ways: The wrong data is written to the storage media, Data is written to the wrong place on the storage media or Data is damaged or changed after being stored. This impact the mail flow to be down.
Corrupt Page Link Was Detected Mail Flow Down
    AIS Monitoring Platform has discovered that a corrupt page link was detected in a B-Tree. Available space in the Exchange store database is in the form of a list of pages that can be used to store new data. The available space is called a space tree. The space tree is held as a binary tree that is searched whenever a block of new data needs to be added to the database. During an online defragmentation, a problem was discovered in this tree. This is often caused by a hardware failure or antivirus scanning of the database file directory. Impact : This impact exchange performance issue. Users may face slow response from the exchange server while sending and receiving emails. This also impact the mail flow to stop.
Corruption In The Header Of A Log File
    AIS Monitoring Platform has discovered corruption in the header of a log file. You may not be able to mount an Exchange store database due to the corrupted log file because the database has become inconsistent. Impact :This impact the exchange store to dismount and mail flow stops.
Corruption Or Inconsistency In A Table In The Jet Database Mail Flow Down
    AIS Monitoring Platform has discovered that there is a corruption or inconsistency in a table in the Jet database. This may caused due to any errors related to hardware, drives, controllers, or the file system. Database corruption may occur if there is a defective hard disk or a defective hard disk controller, if an antivirus program is scanning folders that are related to Exchange or if there is a corrupted restore operation. Impact : This may impact the mail flow to stop.
Database Engine Unable To Open Log Files
    AIS Monitoring Platform has discovered that the Database engine is unable to open log files. This indicates that an unknown system error has occurred while opening a newly-created log file. Cause : This may be caused due to file permissions and attributes. Impact : This may impact mail flow to stop.
Database File Is Not In An Acceptable Format Mail Flow Issue
    AIS Monitoring Platform has discovered that the designated database file is not in an acceptable format. The designated file is not a database file. The headers of the file may be corrupted. Impact : This impact the mail flow to stop.
Database Recovery Failed Because IT Encountered References To A Database Path And Database Name That Is No Longer Present Database Recovery Failed
    AIS Monitoring Platform has discovered that the Database recovery fails because it encountered references to a database [path\database name] which is no longer present. The database was not brought to a consistent state before it was removed or possibly moved or renamed. The database engine will not permit recovery to complete for this instance until the missing database is re-instated.
Disk (I-and-O) Problem Prevents Exchange From Gaining Write Access To A Requested Page In The Database Or To A Transaction Log Mail Flow Down
    AIS Monitoring Platform has discovered that the database engine denied write access to its own database files or to the checkpoint file. This is a generic error that appears whenever a disk I/O problem prevents Exchange from gaining access to a requested page in the database or to transaction log. A disk or controller failure may have occurred, and access to the entire drive has been lost, sometimes temporarily. When this happens, Exchange may not be able to write, read, delete, open, or create Exchange log, check, or database files. This issue may also occur because the path for the check file is not correct, which may be caused by a drive failure. Impact : This all impact slow performance of exchange server and may also impact the mail flow to stop.
Disk I-and-O Problem Prevented Exchange From Gaining Read Access To A Requested Page In The Database Mail Flow Down
    AIS Monitoring Platform has discovered an unexpected error occurred while reading the file specified in the message. An attempt to read from the file [database file name such as priv1.edb or priv1.stm] failed. This is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database or to a check file. A disk or controller failure may have occurred, and access to the entire drive has been lost, sometimes temporarily. The controller software or firmware may be out of date. Check the system log for I/O or drive errors near the time of this Event. This issue may occur because the path for the check file is not correct, which could be caused by a drive failure. Impact : This all impact slow performance of exchange server and may also impact the mail flow to stop.
Disk I-and-O Problem Prevented Exchange From Gaining Read-and-write Access Possible Mail Flow Stop
    AIS Monitoring Platform has discovered that an attempt to open the file for read/write access failed with system error. The open file operation will fail with error. The file is either a .chk file such as E00.chk or a database file such as priv1.edb or priv1.stm. This is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database or to a check file. A disk or controller failure may have occurred, and access to the entire drive has been lost, sometimes temporarily. This issue may also occur because the path for the check file (such as E00.chk) is not correct, which may be caused by a drive failure. Impact : This impact mail flow to be down.
Disk I-and-O Problem Prevented Exchange To Access To A Requested Page In The Database
    AIS Monitoring Platform has discovered that a new log file could not be created because the database cannot write to the log file drive. This is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database or to a check file. A disk or controller failure may have occurred, and access to the entire drive has been lost, sometimes temporarily. The controller software or firmware may be out of date. This issue may occur because the path for the check file (such as E00.chk) is not correct, which may be caused by a drive failure.
Disk I-and-O Problem Preventing Exchange For Writing Log Files Mail Flow Down
    AIS Monitoring Platform has discovered an unexpected error was encountered while writing to the file specified in the message. If Exchange asks the operating system for a page in the database, and an error occurs instead of the page data being returned. This is a generic error that appears whenever a disk input/output (I/O) problem prevents Exchange from gaining access to a requested page in the database. The most common reason for a -1022 error is a database file that was severely damaged or truncated. If the ESE Error is -1022 and the error is caused by database damage in the file system, you need to verify or repair the file system, and then restore Exchange from a backup. Although repairing the database is still an option, repair is less likely to be successful than with the other errors because a -1022 error often signals extensive damage.
Disk That Contains Transaction Log Files Is Low On Disk Space Store Dismount Due To Low Disk Space
    AIS Monitoring Platform has discovered that the disk that contains the transaction log files of the database engine is full. Possibility of store dismount due to low disk space. This impact mail flow to stop. Deleting log files to recover disk space may prevent the database from starting if the database files are inconsistent. If you remove a log file that contains data that has not yet been written to the database files. Impact : The databases will no longer be mountable after an abnormal stop.
Emails Stuck In Categorizor Queue
    AIS Monitoring Platform has discovered emails Stuck in Categorizor Queue. The SMTP Server\Categorizer Queue Length counter indicates the number of messages in the Simple Mail Transfer Protocol (SMTP) Categorizer queue waiting for directory service attribute searches using global catalog servers. The categorizer performs the following core operations: 1. Resolves and validates all recipients. 2. Determines limits and restrictions for all recipients. 3. Expands distribution lists if that is required. 4. Determines whether the message is for local or remote delivery This error indicates that there may be problems with server or network performance, Directory Service Access (DSAccess), the Active Directory directory service, or outages with key servers in the Exchange Server organization. An increase in the Categorizer Queue Length counter may indicate a either a slow response or no response in consulting Active Directory or in handing off messages for local delivery or SMTP. Impact : This might cause delayed mail delivery.
Emails Stuck In Local Queue
    AIS Monitoring Platform has discovered emails Stuck in Local Queue. This rule will monitor Local Queue on Exchange 2000 2003. The SMTP Server\Local Queue Length counter indicates the number of messages in the SMTP queue for local delivery. As a general guideline, the maximum value should be less than 1,000. The queue should remain steady near its average with a small amount of variance. A buildup of messages in the Local Delivery queue indicates a performance issue or outages on the server, because the server can no longer deliver the incoming mail in a timely manner. Impact : This impact mail flow to be down.
Error Encountered While Trying To Open A File Cannot Access File
    AIS Monitoring Platform has discovered that the exchange file is locked or in use. Another process has locked the file. Antivirus software may mistakenly quarantine a file, or a backup process may temporarily deny access. A flat file backup system or antivirus software may be running against the database or check file directories. This error can also occur if the permissions on the folder that contain the files for the Exchange stores are not sufficient for the stores to function properly. Impact : This impact the mail flow down.
Exchange Dag Replication Issue
    AIS Monitoring agent has detected exchange Dag replication issue. This issue may occure due to, Storage drivers are upgraded resulting in the recognized sector size changing. Storage firmware is upgraded resulting in the recognized sector size changing. New storage is presented or existing storage is replaced with drives of a different sector size. Impact: This mismatch can cause one or more database copies in a DAG to fail.
Exchange Database Size Has Crossed The Defined Size Limit
    Saaz Intelliscript has observed that logical size of the database is greater than the threshold you have configured.
Exchange Email Scanning Antivirus Corruption Detected For Microsoft Exchange Server
    AIS Monitoring Platform has discovered an issue related to Symantec Antivirus for Microsoft Exchange which can further cause mail flow stop and Exchange database corruption.
Exchange Mail Flow To Internet Has Stopped Due To Dns Issue
    AIS Monitoring Platform has discovered mail flow to internet has stopped due to dns issue. This condition will detect Mail queue increasing due to name resolution to ISP DNS Server not working OR ISP DNS server is not configured under DNS configuration – Forwarders TAB.
Exchange Microsoft Exchange System Attendant Service May Not Come Online
    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 Out Of Memory Error Detect On Exchange Database
    Saaz Intelliscript has detect Out of memory error on one of the exchange database store. Make sure there is memory available. If not, use Perfmon or Task Manager to troubleshoot. Check the event log for additional errors.
Exchange The Clustered Mailbox Server Failed Over The Passive Node With Data Loss
    SaazIntellmon has detected Mailbox Server failover with Data loss, some logs were not replicated continously.
Exchange The Exchange Store Is Dismounted Due To JET Error Checkpoint Depth Too Deep
    AIS Monitoring Platform has discovered store dismount due to JET error Checkpoint Depth Too Deep.This error occurs when Exchange store contains more than 1024 uncommitted ESE transaction for Exchange database (Exchange 2000 2003) 5000 uncommitted Extensible Storage Engine (ESE) transaction log files for Exchange 2007.
Exchange The Logfile Sequence Has Been Halted Due To A Fatal Error
    AIS Monitoring Platform has discovered that The logfile sequence in [directory name] has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence.
Exchange Time Skew Issues Detected On Exchange
    AIS Monitoring Platform has discovered time skew issues detected on Exchange. This condition will detect Information Store service failure due to time skew between Exchange Server and domain Controller. The system time on the servers indicated in the alert is not synchronized.
Exchange 2000 Users Not Able To Logon To Mailbox Unless Server Is Rebooted
    AIS Monitoring Platform has discovered that the Users not able to logon to mailbox. This condition will monitor Mailbox logon failure on Exchange 2000 and users may not be able to log on unless you restart the server.
Exchange 2000 2003 Important Transport Errors Rule : 1
    AIS Monitoring Platform has discovered exchange transport errors. This condition will monitor mailflow related problem like emails getting refused, reverse NDR attack i.e. Spam attack etc. This can further cause Exchange Server emails getting queued up under remote queue.
Exchange 2000 -and- 2003 System Attendant Service Failed
    AIS Monitoring Platform has discovered System Attendant Service failure due to imporper security group heirarchy defined in Active Directory. When the System Attendant service starts, it searches for the following groups in only the default Users container: Exchange Enterprise Servers, Exchange Services and Exchange Domain Servers. If these groups are not in the default Users container, the System Attendant service determines that the groups do not exist. Therefore, if these groups are not in the Users container when you start the System Attendant service, the service does not start.
Exchange 2000 -and- 2003 System Attendant Service Failure Due To KDC Stopped On SBS Exchange Running On DC
    AIS Monitoring Platform has discovered System Attendant Service failure because Kerberos Key Distribution Center service is stopped on Small Business Server and Exchange application running on Domain Controller. This issue occurs if the following conditions are true: 1. The Kerberos Key Distribution Center service is not running on the Exchange server. 2. The Exchange server is acting as a domain controller.
Exchange 2000 Standard Database Nearing 16GB Threshold Limit
    This alert condition indicates that the size of the Exchange database is nearing the 16 GB limit. Exchange store databases on Exchange Server 2003 Standard Edition and Exchange 2000 Server Standard Edition cannot exceed 16 GB. Once this limit is reached, the mailbox store will no longer mount and Exchange will become inaccessible.
Exchange 2000-and- 2003 Information Store Service Fails To Starts Due To Corruption In SMTP
    AIS Monitoring Platform has discovered Information Store service failure due to SMTP verbs missing, this problem is normally found when IIS is re-installed on Exchange Server. When Information Store service fails to call Rounting Engine API this problem is detected. OR due to incorrect permission defined in Active Directory.
Exchange 2000-and- 2003 MSExchangeIS Content Engine Fails To Process Emails
    AIS Monitoring Platform has discovered that the Microsoft Exchange Server Information Store content engine is unable to process emails. There are multiple factors that can cause this issue: 1. The Store.exe is consuming lot of process. 2. Emails are stuck in local queue. 3. Message processing failed because there is not enough available memory
Exchange 2000-and-2003 DNS -and- GC Issue Causing Exchange To Go Down
    AIS Monitoring Platform has discovered DNS/GC problem causing exchange to go down. When this condition is detected Exchange Server tries to failover to another GC and DC within network for communication, if Addition domain controller communication fails then exchange services would fail. This will impact exchange mail flow to stop.
Exchange 2003 Mail Flow Stops On Exchange Server Suspected Virus Scanning API Scanners Issue
    AIS Monitoring Platform has observed that Mail flow has stopped on Exchange Server due to antivirus program is configured to include scans of Exchange Server folders and files.
Exchange 2003 OWA Down Due To IIS Application Pool Issue
    AIS Monitoring Platform has discovered that OWA is down due to IIS application Pool issue. This may cause if Exchange virtual directory is either not running in the correct application pool, or when the ExchangeApplicationPool property has the incorrect identity.
Exchange 2003 Store Exe Crashed
    AIS Monitoring Platform has discovered Store.exe crash due to bug in Exchange. This problem occurs because the Microsoft Exchange Information Store service incorrectly calculates the offset value at the end of the header (EOH) for corrupted messages. This behavior causes an access violation. A supported hotfix is available which intend to fix the problem.
Exchange 2003 Std SP2 Database Size Nearing Threshold Limit
    This alert condition indicates that the Exchange 2003 Std SP2 database size is nearing the threshold limit. 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 Information Store Service Fails To Start Due To Default Policy Was Deleted
    Saaz Intelliscript has observed that the Microsoft Exchange Information Store service does not start in Exchange Server 2007 due to Default Policy was deleted from the E-mail Address Policies tab and if it was replaced by a custom e-mail address policy.
Exchange 2007 Mailbox Server Role Not Able To Reach Hub Transport In Local Site
    AIS Monitoring Platform has discovered that the Mailbox Server role not able to reach Hub Transport in local Site. The Messages Queued for Submission performance counter 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 25 for 15 minutes. This 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 2007 Outlook Web Access Proxy Request Failed Because No Outlook Web Access Virtual Directory In The Active Directory Site For The Mailbox Is Configured For Kerberos Authentication
    Saaz IntelliScript has discovered that Outlook Web Access proxy request failed because no Outlook Web Access virtual directory in the Active Directory site for the mailbox is configured for Kerberos authentication. The Outlook Web Access proxy request failed because no Outlook Web Access virtual directory in the Active Directory site for the mailbox is configured for Kerberos authentication.
Exchange 2007 OWA Problem Suspected Due To Net Framework Configuration Problem
    AIS Monitoring Platform has observed .Net Framework configuration problem which can cause Outlook Web Access to go down.
Exchange 2007 -and- 2010 Invalid Virus Scanner Configuration Detected
    SaazIntelliScript has detected an Invalid virus scanner configuration, this Error event can occur when attempting to mount the Microsoft Exchange Information Store service, especially after an antivirus application has been uninstalled. This usually indicates that an exception was generated during a call to the antivirus software installed (or previously installed) on the computer.
Exchange 2007 Services May Not Start On Exchange 2007 With A Global Catalog Server After Restart -and- SBS 2008 Standard, Premium
    AIS Monitoring Platform has discovered Exchange Service failure because Exchange 2007 is installed on a global catalog server. When you install Microsoft Exchange Server 2007 on a global catalog server i.e. Small business Sever. Exchange 2007 services may not start after restart. However, you can start other services manually. Servers in this configuration may take a long time to shut down.
Exchange 2007-and-2010 An Unexpected Error Occurred In The Provider Used By The Autodiscover Service
    Saaz IntelliScript has discovered an unexptected error that indicates that the Microsoft Exchange Autodiscover service was trying to load an assembly on the Microsoft Exchange Client Access server with failure.
Exchange 2007-and-2010 An Unexpected Error Occurred While Data Was Being Retrieved From The Autodiscover Service
    Saaz IntelliScript has discovered that the client request received could not be successfully processed by the Microsoft Exchange Autodiscover service.
Exchange 2007-and-2010 Database Mounts Fails Due To MESO Container Is Deleted From The Active Directory Service
    Saaz IntelliScript has observed that the Microsoft Exchange System Object (MESO) container is deleted from the Active Directory directory service due to this information store database fails to start.
Exchange 2007-and-2010 ESE Call By The Microsoft Exchange Information Store Service And Received An Error
    AIS Monitoring Platform has Extensible Storage Engine (ESE) was called by the Microsoft Exchange Information Store service and received an error from the operating system when the ESE tried to read or write to a file. The file could be a database file, a transaction log file, or a checkpoint file. This event will cause the affected databases to dismount. Users who have mailboxes on the dismounted databases will be unable to send or receive e-mail.
Exchange 2007-and-2010 Failed To Write Transaction Logs To Exchange Database
    AIS Monitoring Platform has discovered that an error occurred while trying to append a new log entry. Make sure that the disk where the specified log file is stored has sufficient space for new log entries. This might be also caused due to Antivirus exclusions not done properly OR Exchange Backup for database in hung state. Make sure that the log file is not in use by any other application.
Exchange 2007-and-2010 Information Store Service And System Attendant Service Fails To Start Due To Incorrect Subnet Information Configured In AD
    Saaz Intelli Script has observed that Information Store Service and System Attendant Service Fails to Start. This issue may occur because a new site has been created in Active Directory Sites and Services, where previously there had only been a Default-First-Site-Name. In addition, the subnet in which the Exchange Server 2007 server resides is not associated with any site in Active Directory Sites and Services.
Exchange 2007-and-2010 Microsoft Exchange Transport Service On An Exchange Server 2007-and-2010 Hub Server Fails To Start
    Saaz IntelliScirpt had detected an issue with Service Microsoft Exchange Transport, you cannot start the Microsoft Exchange Transport service on a Microsoft Exchange Server 2007 Hub server.
Exchange 2007-and-2010 Store Driver Issues On Hub Transport Server
    AIS Monitoring Platform has discovered Store Driver issues on Hub Transport Server. The Store driver on the Hub Transport server places messages from the transport pipeline into the appropriate mailbox. The Store driver on the Hub Transport server also adds messages from the Outbox of a sender on the Mailbox server to the transport pipeline.
Exchange 2010 An Attempt To Move The File Failed With System Error 2 (0x00000002)
    AIS Monitoring Platform has discovered that An attempt to move the file failed with system error 2 (0x00000002): The system cannot find the file specified. . The move file operation will fail with error -1811 (0xfffff8ed).unable to mount EDB (Exchange Database) database file on the MS Exchange Server system that is being used in your organization
Exchange 2010 Anti Virus Email Scan Queue Length Increasing
    AIS Monitoring Platform has observed Anti Virus Email Scan Queue Length increasing this problem can cause delay in mailflow and database store processing slow.
Exchange 2010 Cluster Core Resources Fail To Come Online On Some Exchange 2010 Database Availability Group (DAG) Nodes
    AIS Monitoring Platform has detected cluster core resource failure during failover to another member of DAG.
Exchange 2010 Connectivity Issue Observed Between Mailbox Server To Hub Transport Server
    AIS Monitoring Platform alert has observed connectivity issue between mailbox to Hub Transport Server, users in outlook configured with cached exchange mode would not notice any issues a emails will still leave their Outbox. Online users in this scenario would have thier emails wait in Outbox.
Exchange 2010 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 2010 Message Delivery To The Database May Be Stopped
    AIS Monitoring Platform has discovered that, available disk space for the database drive is low. Impact : New emails will not be delivered to exchange database.
Exchange 2010 Trend Micro ScanMail For Microsoft Exchange Causing Issue With Mail Flow
    AIS Monitoring Platform has observed that Trend Micro ScanMail for Microsoft Exchange is configured for wildcard character searches against the Active Directory directory service
Exchange 2010 Unable To Create A New Logfile Because The Database Cannot Write To The Log Drive
    AIS Monitoring Platform has discovered that Information Store (PID) Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1811.
Exchange Database Corruption Files Mail Flow Down
    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.
Exchange Database Dismount Due To Disk Full For Database OR Transaction Log
    AIS Monitoring Platform has discovered that Exchange database dismount due to disk full for database OR transaction log. This condition will detect graceful dismount of database in case the disk holding database or tranaction log is full. Impact : This will impact the users from sending and receiving emails as the exchange store is dismounted.
Exchange Database Engine Denied Write Access To Its Own Database Files Mail Flow Down
    AIS Monitoring Platform has discovered that Exchange server database service denied write access to its own database files or to the checkpoint file. This happens when the file is locked or in use. Another process has locked the file. Antivirus software may mistakenly quarantine a file, or a backup process may temporarily deny access. A flat file backup system or antivirus software may be running against the database or check file directories. This error can also occur if the permissions on the folder that contain the files for the Exchange stores are not sufficient for the stores to function properly. This impact the mail flow down.
Exchange Database Engine Is Unable To Read The Database Header
    AIS Monitoring Platform has discovered that the database may have moved and therefore may no longer be where the logs expect it to be. It is possible that during recovery of the database, data was missing or moved.
Exchange Database Engine Is Unable To Replay The Log File Sequence Exchange Restore Fails
    AIS Monitoring Platform has discovered Exchange database engine is unable to replay the log file sequence. This condition may occur if the log file is missing or there may be other causes for this error. For example, the current log file may have a mismatching signature between the log and the database. This might also be generated when the Exchange databases and log files are stored on network storage. This is unsupported. In addition, the checkpoint file may be corrupted, or the log drive may have failed. The current log file may have been seized and deleted or quarantined by antivirus software running on the server. There have also been problems creating the temp log file for the storage group. The temp log file may be corrupted.
Exchange Database Engine Is Unable To Replay The Log File Sequence Permission Or Read-and-Write Problem Exchange Restore Fails
    AIS Monitoring Platform has discovered Exchange database engine is unable to replay the log file sequence. This can occur if Exchange database engine is unable to replay the log file sequence during restore process. This can be caused due to permissions issues, space issues, SAN issues, and other issues affecting reads and writes to the disks.
Exchange Database Engine Unable To Open Log Files
    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. This may impact the mail flow to stop.
Exchange Database Files Are Missing And Could Not Be Recovered
    AIS Monitoring Platform has discovered Exchange database files are missing and could not be recovered. The location of log files can change depending on the server configuration. It is highly recommended that the administrator use different storage locations for the log files. This impact the Exchange store to dismount and mail flow can stop.
Exchange Database Is In An Inconsistent State And Cannot Start
    AIS Monitoring Platform has discovered an unexpected error that usually indicates that the database is in an inconsistent state and cannot start. This could also occur during runtime and may indicate that the log drive failed. This Warning event indicates that a file system error was reported when doing I/O operations. If the warning persists, the database file may be damaged.
Exchange Database Recovery Failed Database Restore Fails
    AIS Monitoring Platform has discovered that Exchange Database Recovery Failed. This Warning event indicates that the recovery of the created database was unsuccessful. The database was recreated.
Exchange Database Recovery Failed Due To Log File Set Sequence Issue Exchange Recovery Failed
    AIS Monitoring Platform has discovered that Exchange Database recovery failed due to log file set sequence issue. This indicates that database recovery failed because it encountered references to a database that does not match the current set of logs. This impact the exchange store to dismount and the mail flow stop.
Exchange Database Recovery-and-Restore Failed
    AIS Monitoring Platform has discovered that there is a problem with a restore, or a problem with a soft or hard recovery of an Exchange Information Store database. Exchange has determined that files in the running set of the database are missing, have been replaced with different versions, or are corrupted. This condition also indicates that a database page read failed verification due to a page checksum mismatch. The particular database page referenced within the Exchange store file is corrupt. Users cannot send or receive e-mail messages. You cannot start Microsoft Outlook on your client computer. Online backups fail to complete with a checksum error. Online defragmentation reports a checksum mismatch error.
Exchange Database Repair Process Failed Which May Have Caused Data To Be Lost
    AIS Monitoring Platform has discovered that a database repair process may have caused data to be lost. Although the repair process tries to validate all system tables and indexes, any data that cannot be repaired is discarded. If the database cannot be repaired, an error occurs. When a database is in an inconsistent condition and a repair is performed by using eseutil /p, this error may be logged during the repair operation. The condition indicates that the repair process found a bad page and tried to repair it, but the repair of the page was unsuccessful and the page was discarded. This ESE event is a serious error that frequently indicates that the database is damaged.
Exchange Database Requires Log Files To Continue Mail Flow Down
    AIS Monitoring Platform has discovered that the database requires the designated log file in order to recover successfully. The database requires log files to continue. This impact the exchange store to dismount and mail flow stops.
Exchange Database Unable To Write To Designated Disk Store Dismount Due To Low Disk Space
    AIS Monitoring Platform has discovered that Exchange Database is unable to write to designated Disk. This occurs when the database engine is rejecting update operations due to low free disk space on the log disk. This might also occur due to disk problem on the server. This impact Exchange store dismount and mail flow stop. Impact :This will cause all databases in the affected storage group to go offline
Exchange High Kernel Memory Utilization In NonPaged Bytes
    AIS Monitoring Platform has discovered Kernel Memory Exhaustion on Servers Running Exchange. This might impact exchange server slow performance. Sluggish or unresponsive user interface. Server has message or client processing failures. Server fails to respond to network requests. Nonpaged pool allocation failures. The server was unable to allocate from the system nonpaged pool because the pool was empty.
Exchange High Kernel Memory Utilization In Pool Paged Bytes
    AIS Monitoring Platform has discovered High Kernel Memory utilization in Pool Paged Bytes on exchange server. This impact exchange slow performance issues which may lead to sluggish or unresponsive user interface. Server has message or client processing failures. Paged pool allocation failures which indicates that the server was unable to allocate from the system paged pool because the pool was empty. Several factors may deplete the supply of paged pool memory. Enabling pool tagging and taking poolsnaps at different time intervals may help you to understand which driver is consuming paged pool memory.
Exchange Log File Corruption Mail Flow Down
    AIS Monitoring Platform has discovered log file corruption on exchange. This occurs when the log file is damaged and cannot be used. This impact the Exchange store to dismount and mail flow stop.
Exchange One Or More Log Files Is Missing Store Dismount
    AIS Monitoring Platform has discovered exchange one or more log files is missing. The recovery process of the database requires log files to continue. Information Store Database requires logfiles in order to recover successfully. An online restore fails due to logfiles missing from the temporary folder that is specified in the Windows Backup program under temporary location for log files. A hardware failure causes loss of logfiles in the logfile sequence required for the restore. This impact the exchange store to dismount and mail flow to stop.
Exchange Receiving Out Of Memory Errors From The Operating System Performance Issue
    AIS Monitoring Platform has discovered that the version store instance cannot grow because it is receiving Out-Of-Memory errors from the OS. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transact