Event ID : 1205

Issue : An attempt to create a mailbox failed. Insufficient permissions, a Jet error, or a memory error may have caused the problem.

Event Source : MSExchangeIS Mailbox Store

Cause : This Error event indicates that a mailbox for the user account specified in the event description could not be created.
This event may occur when moving the mailbox from one mailbox database to another mailbox database. One or more of the following conditions may occur.

1. The mailbox for this user already exists in the mailbox tombstone table.
2. The user account specified in the event description was deleted but the changes were not replicated to all the domain controllers in Active Directory.
3. There are logical corruptions in the database.

You may also see an Error event 1022 in the Application log.

Description : Failed to create the mailbox of "{mailbox name}" with error "{error code}".

Action Required :

• Try creating a mailbox again. Use the error returned to help determine a course of action.
• Review the event log for related entries.
• If this error occurred during a move mailbox operation, make sure that the move was successful.
• If not, try to move the mailbox again. Make sure both the source and target mailbox database stores are in Mounted state.

Event ID : 454 , 494

Issue : Hard page faults on exchange database, database can be down or can go down.

Event Source : ESE

Cause :
This behavior occurs because the Extensible Storage Engine (ESE) attempts to bring all databases in a storage group to a consistent state during recovery. To accomplish this, ESE keeps track of all databases in the log files for the storage group. If a database is missing, ESE returns the error -1216, and does not start the storage group.
Event ID 454 is a generic event that indicates a problem either with a restore operation or with the recovery of an Exchange 2000 Information Store database. Generally, Event ID 454 means that Exchange 2000 has determined that:

• Files in the database's running set are missing.
• Files in the database's running set have been replaced with different versions.
• Files in the database's running set are corrupted.

Description : Information Store (976) Database recovery/restore failed with unexpected error Error Number -1216.

Action Required :

1. To resolve this problem, either locate the missing databases and move them to the appropriate folders, or restore the missing databases from backup.
2. If the missing database was deleted or lost, restore the missing database from a backup. While you are restoring this database, you can mount and access the other databases in the storage group by completing the following steps:

• Run eseutil /r Log Base Name /I. This allows ESE to take the databases that are present to a consistent state while ignoring the missing databases. After you run this command, any databases that are not present will require restoring from backup. You can specify the location of the log files with the /l option and the location of system files with /s option.
• Mount the databases in the storage group that are now present and consistent.
• Allow the users on the running database to access their mail.

Ref.Link :

1. http://support.microsoft.com/kb/810198
2. http://support.microsoft.com/kb/823168

Event ID : 447

Issue : Outlook will not open for end-users. The information store terminated abnormally .

Event Source: ESE

Cause : This problem is frequently caused by a hardware failure or by antivirus scanning of the database file directory. Event ID 447 indicates that the logical database structure has become corrupted. This may occur for one or more of the following reasons:

1. Disk caching has not committed transactions to the hard disk and the server has stopped responding (crashed).
2. Incorrect log files were replayed during a database restoration.
3. The server has a defective hard disk controller.
4. Database log files have been removed that were not fully committed to the database.

E.g.
Information Store (nnnn) A bad page link (error -338) has been detected in a B-Tree (ObjectId: 70950, PgnoRoot: 157120) of database e:\Program Files\exchsrvr\mdbdata\priv1.edb (157120 => 296404, 296403).

Action Required :
If you receive these errors in your application log, it is best if you restore from an online backup as soon as you can.The restore must be performed by using a backup that was created before this error occurred. In a worst-case scenario where no good backup exists, you may have to do a hard repair by running the "eseutil.exe /p" command (original database is preserved). After the hard repair, do an offline defragmentation of the database by running the "eseutil /d" command, and then run the " isinteg -fix " command (Repair information store.) on the database.This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Ref Link:

http://support.microsoft.com/kb/810190/en-us

Event ID : 478

Issue : The streaming database specified in the message is corrupted.

Event Source: ESE

Cause : When you perform an online backup of a storage group, a mailbox store, or a public folder store, the operation may be unsuccessful.

Description : This Warning event indicates that the streaming database specified in the message is corrupted.The .edb and .stm files may be out of sync. An older copy of the .stm file may be in use, and the checksum table in the .edb file is therefore out of date. A program may have altered the .stm file without updating the checksums in the .edb file. There could be problems with the hard disk subsystem or controllers of the system.
E.g.
Information Store (308) The streaming page read from the file "C:\Program Files\Exchsrvr\
mdbdata\prv1.stm" at offset 130646016 (0x0000000007c98000) for 4096 (0x00001000) bytes faled verification due to a page checksum mismatch. The expected checksum was 18463398 (0x000000000af895a6) and the actual checksum was 184063406 (0x000000000af95ae). The read operation will fail with error -613 (0xfffffd9b). If this condition persists then please restore the database from a previous backup.

Action Required :
Take full exchange database backup if database is online, if successfull then restore same from backup immediately, if back is failing then take offline backup of database and perform following.

1. Repair database using eseutil /p
2. defrag database using eseutil /d
3. Run isinteg -s -fix -test alltests

OR

If exchange version is enterprise then move all mailboxes to new database and repair old database.
Ref.Link :

http://support.microsoft.com/kb/314917/en-us

"We have observed physical errors on the database. It is strongly recommended to repair the database. We will be performing following activities on the server :

1. Repair database using eseutil /p
2. Defrag database using eseutil /d
3. Run isinteg -s -fix -test alltests

Ref.Link :

1. http://support.microsoft.com/?id=318429
2. http://support.microsoft.com/?id=814891
3. http://support.microsoft.com/kb/840013/en-us

Event ID : 205

Issue : Microsoft Exchange server that logged this event is not connected to the local area network.

Event Source: MSExchange Common

Cause : This Error event indicates that the Microsoft Exchange server that logged this event is not connected to the local area network. This event may occur when the network adapter installed on this server is either disabled or not working.

Description : No DNS servers could be retrieved from network adapter. Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results.

Action Required :
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.
Command : Get-NetworkConnectionInfo

Event ID : 1503

Issue : Outlook Mobile Access users cannot access their mailboxes on a heavily-loaded Exchange Server 2003 computer.

Event Source: MSExchangeOMA

Cause : On a heavily-loaded Microsoft Exchange Server 2003 computer, users in your organization may not be able to access their mailboxes by using Microsoft Outlook Mobile Access.
In this scenario, an Outlook Mobile Access user may receive an error message that is similar to the following:
" A system error has occurred, please see your system administrator. "

This problem may occur if Exchange Server 2003 is running on a Microsoft Windows 2000-based computer. In this scenario, virtual memory fragmentation may occur if Exchange Server 2003 is under a heavy load. You may experience this problem during stress-testing of your Exchange Server environment.

Description : An unknown error occurred while processing the current request: Exception of type System.OutOfMemoryException was thrown.Outlook Mobile Access users cannot access their mailboxes on a heavily-loaded Exchange Server 2003 computer.

Action Required : To work around this problem, restart the World Wide Web Publishing service on the Exchange Server computer.

Ref Link:
http://support.microsoft.com/kb/842119/en-us

Event ID : 9549

Issue : Not able to send email to a perticular mailbox OR not able to open mailbox using OWA.

Event Source: MSExchangeIS

Cause : This issue may occur if another account exists that has the same e-mail address. The same SMTP proxy address has been assigned to more than one object in Microsoft Windows 2000 Active Directory. Event 9514 indicates which objects have the same SMTP address.

In Exchange 2000, you may experience one of the following symptoms:

1. When you try to send a message, you receive a non-delivery report (NDR) that includes an "ambiguous recipient" error message or a Simple Mail Transfer Protocol (SMTP) delivery status notification code 5.1.4.
2. You receive the following message when you add a proxy address to a user account:
   This e-mail address already exists in this organization. ID no. c10312e7 Microsoft Active Directory - Exchange Extension.

Description: An ambiguous SMTP proxy user1@domain.com was found on 0x2 mailboxes in the DS. The store cannot map this SMTP proxy to a unique Mailbox GUID.

Action Required :

1. To resolve this issue, locate the user account that has an ambiguous address or an address that already exists (to find the address, view the E-mail Addresses tab in the user account properties), and then change one or more of the accounts so that they do not have the same e-mail address.To locate the user account that has an ambiguous address or an address that already exists, use either of the methods that are described in this section.
2. To resolve this problem, find the objects that have duplicate SMTP addresses using event 9514, and then modify the SMTP address.

Ref Link:
http://support.microsoft.com/kb/286792/en-us

http://support.microsoft.com/kb/269498/en-us