%1 (%2) %3Data inconsistency detected in table %4 of database %5 (%6,%7).

Details
Product: Exchange
Event ID: 448
Source: ESE
Version: 6.5.0000.0
Message: %1 (%2) %3Data inconsistency detected in table %4 of database %5 (%6,%7).
   
Explanation
ESE Event ID: 448 indicates that there is a corruption or inconsistency in a table in the Jet database.Check the Application log carefully for related events and patterns that may relate to this event. Check the System log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system.
   
User Action
  1. Check the Application log carefully for related events and patterns that may relate to this event. Check the System log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system. If there are any such errors, replace the hardware, update the hardware system files, or repair the file system to prevent any future errors. Do this before proceeding to the next step

  2. If the information store database is running, it is suggested that you ExMerge your data to .pst files, delete the database, create a blank database, and then ExMerge your databases to a blank database.

  3. If the database is running, you may also move all the mailboxes to another store, delete the affected database, create a new database, and then move all the mailboxes back.

  4. If the information store database will not mount, the suggested remedy is to restore from online backup before the errors appear in the Application Log.

  5. If the information store database will not mount and there is no backup, the last resort is to repair the database using Eseutil /p and then repeatedly run Isinteg -fix until there are no longer any fixes reported. Then ExMerge out the data, create a blank store, and ExMerge the data back in.

Related:

The specified collation name is not valid. See SQL Server Books Online for valid names.

Details
Product: SQL Server Notification Services
Event ID: 1008
Source: NotificationServices
Version: 2.0.9999.9
Message: The specified collation name is not valid. See SQL Server Books Online for valid names.
   
Explanation
This error maps to SQL Server error 448, which indicates that the specified collation name (generally in the ADF) is not valid.

The event log entry for this error includes the description of the SQL Server error that caused it, which looks similar to the following:

Invalid collation “<collation_name>”.</collation_name>

   
User Action
There are several places in the ADF where collations can be specified. Search for the <collation_name> information noted in the event log entry and replace it with a valid collation name. For more information on sorting collations, see COLLATE in SQL Server Books Online.</collation_name>

Related:

() Data inconsistency detected in table of database (,).

Details
Product: Exchange
Event ID: 448
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>Data inconsistency detected in table <name> of database <name> (<value>,<value>).
   
Explanation

ESE event 448 indicates that there is a corruption or inconsistency in a table in the Jet database.

Check the application log carefully for related events and patterns that may relate to this event. Check the system log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system.

   
User Action
  • Check the application log carefully for related events and patterns that may relate to this event. Check the system log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system. If there are any such errors, replace the hardware, update the hardware system files, or repair the file system to prevent any future errors. Do this before proceeding to the next step
  • If the information store database is running, it is suggested that you ExMerge your data to .pst files, delete the database, create a blank database, and then ExMerge your databases to a blank database.
  • If the database is running, you may also move all the mailboxes to another store, delete the affected database, create a new database, and then move all the mailboxes back.
  • If the information store database will not mount, the suggested remedy is to restore from online backup before the errors appear in the application Log.
  • If the information store database will not mount and there is no backup, the last resort is to repair the database using Eseutil /p and then repeatedly run Isinteg -fix until there are no longer any fixes reported. Then ExMerge out the data, create a blank store, and ExMerge the data back in.

Related:

There is a collation mismatch between the main instance database and the application database.

Details
Product: SQL Server Notification Services
Event ID: 1010
Source: NotificationServices
Version: 2.0.9999.9
Message: There is a collation mismatch between the main instance database and the application database.
   
Explanation
This error maps to SQL Server error 446, which indicates that the specified operation was given objects with mismatched collations.

The event log entry for this error includes the description of the actual error that caused it, which looks similar to the following:

Cannot resolve collation conflict for <operation_name> operation.</operation_name>

   
User Action
Determine the operation that failed from the event log entry and make sure that the arguments to the specified operation have matching collations. For example, if you have two columns in the same table with Greek and Latin collations respectively, a WHERE clause such as the following will cause this error:

WHERE GreekCol = LatinCol

The resulting error will have the following additional description:

Cannot resolve collation conflict for equal to operation.

The problem noted in this error must be resolved for the system to function properly.
For more information, see COLLATE in SQL Server Books Online.

Related:

() Database recovery stopped abruptly while redoing logfile (,). The logs after this point may not be recognizable and will not be processed.

Details
Product: Exchange
Event ID: 446
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>Database recovery stopped abruptly while redoing logfile <file name> (<value>,<value>). The logs after this point may not be recognizable and will not be processed.
   
Explanation

The logs after this point may not be recognizable and will not be processed. Some log files may be damaged because of size mismatching.

   
User Action

If performing a soft recovery, restore from backup media.

If performing a hard recovery, refer to the backup set to determine the affected log files. If the corrupted log file is outside the backup set, remove the files outside the backup set and run restore again. If the corruption is contained in log files, revert to a previous backup in the backup set.

Loss of data may occur. If the problem persists, contact Microsoft Product Support Services.

Related:

%1 (%2) %3Database recovery stopped abruptly while redoing logfile %4 (%5,%6). The logs after this point may not be recognizable and will not be processed.

Details
Product: Exchange
Event ID: 446
Source: ESE
Version: 8.0
Symbolic Name: REDO_END_ABRUPTLY_ERROR_ID
Message: %1 (%2) %3Database recovery stopped abruptly while redoing logfile %4 (%5,%6). The logs after this point may not be recognizable and will not be processed.
   
Explanation

This Warning event indicates that database recovery stopped abruptly. The logs after this point may not be recognizable and will not be processed. Some log files may be damaged.

   
User Action

To resolve this warning, you may have to remove all transaction log files from this point forward. This causes the loss of some data. You can also check log files for problems by using Eseutil /ML log prefix, for example, Eseutil /ML E00 if the log files all start with E00.

If the affected log files were restored with the backup and were not previously on the server, you should restore the backup again or omit the backup if it is an incremental or differential backup.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

{process name} ({process id}) Database recovery stopped abruptly while redoing logfile {file name} ({value},{value}). The logs after this point may not be recognizable and will not be processed.

Details
Product: Exchange
Event ID: 446
Source: ESE98
Version: 6.0
Component: Extensible Store Engine
Symbolic Name: REDO_END_ABRUPTLY_ERROR_ID
Message: {process name} ({process id}) Database recovery stopped abruptly while redoing logfile {file name} ({value},{value}). The logs after this point may not be recognizable and will not be processed.
   
Explanation
Some log files may be damaged because of size mismatching.
   
User Action
If performing a soft recovery, restore from backup media. If performing a hard recovery, refer to the backup set to determine the affected log files. If the corrupted log file is outside the backup set, remove the files outside the backup set and run restore again. If the corruption is contained in log files in the backup set, revert to a previous backup. The loss of data may occur. If the problem persists, contact Microsoft Product Support Services.

Related:

The MAPI call ” failed with the following error:

Details
Product: Exchange
Event ID: 9175
Source: MSExchangeSA
Version: 6.5.6940.0
Component: Microsoft Exchange System Attendant
Message: The MAPI call ‘<value>‘ failed with the following error:<error code>
   
Explanation

This error can be triggered under several conditions as follows:

  • When mounting a mailbox store or public folder store.
  • When the System Attendant is trying to generate an Offline Address Book.
  • When the stores are down and the System Attendant is trying to do its routine management tasks.
  • When attempting to perform a Move Mailbox operation.
  • At the rate of 1 every minute on a clustered Exchange Server.

In essence, this message indicates that the System Attendant process has been unable to log on to the Mailbox Store or Public Store.

This event can have several causes and the ID number in the Description section of the event will be the only difference between the events. Depending on what the underlying cause of the problem is, the ID number will vary. The other ID numbers that could be seen are: 8004011d-0519-0000000, 80040111-0286-00000000, 8004011d-0289-00000000

The main causes to check for ones are as follows:

  • The Microsoft Exchange Information Store service is not running.
  • The Microsoft Exchange Information Store service is running, but one or more databases are not mounted.
  • The Read System Access Control List (SACL) of the Exchange Enterprise Group is lost.
  • The MDBDATA folder has inappropriate permissions.
  • The System Attendant service is running with a different user account than “Local System”.
  • The Default Public Store attribute on an Exchange 2000 server points to an Exchange 5.5 server public store in another domain.
  • The System Mailbox object that is created for this mailbox store exists in the Microsoft Exchange System Objects container
   
User Action

Although the proper resolution will be determined by the ID number that is indicated in the event, you can try the following actions:

  • Verify that the Microsoft Exchange Information Store service is running.
  • Make sure that the default mailbox store is mounted.
  • Run setup /domainprep.
  • Verify the permissions on the MDBDATA folder.
  • Change the properties of the System Attendant service so that it runs in the context of the Local System Account.

Related:

The database “%1” has reached the maximum allowed size. Attempting to unmount the database.

Details
Product: Exchange
Event ID: 1112
Source: MSExchangeIS
Version: 8.0
Symbolic Name: msgidOutOfDatabaseSpace
Message: The database “%1” has reached the maximum allowed size. Attempting to unmount the database.
   
Explanation

This Error event indicates that the disk volume that contains a Microsoft Exchange Server database is either out of disk space or has reached the maximum allowed database size. With Microsoft Exchange Server 2007, you can configure the maximum size of the Exchange 2007 database based on the Exchange version that you have installed.

   
User Action

To resolve this error, do the following:

  • You can configure the maximum size of the Exchange 2007 database. See the topic Database Size Limit Configuration and Management in the Technical Reference Guide for Exchange Server 2003. The Exchange 2003 content describes how to change the value applies to the Exchange 2007 server.

  • If you have not exceeded the database limit, determine whether the specified disk is full. If the disk is full, you must reduce the amount of data on the disk, and then restart the Microsoft Exchange Information Store service. You can take action to free up disk space, such as the following:

    • If the database transaction log files are on the same disk as the Exchange database, it is possible that too many log files have accumulated. This situation can be caused by excessive database usage during a mailbox move or other operation, or it can be caused by incorrectly performing backups. The correct method to remove database transaction log files is to perform an online backup. An online backup commits all of the log files to the database and then removes the log files from the disk. For more information about how to remove the database transaction log files, see Microsoft Knowledge Base article 240145, How to remove the Exchange Server transaction log files.

    • If the database and transaction log files are on the same disk, consider moving the logs to another disk.

    • If the database has become too large for the disk, consider moving the database to a new disk.

    • If there are other files on the disk, consider deleting or moving those files.

    • If there are other Exchange databases on the disk, consider moving those databases.

    • Reclaim disk space in the Exchange database by using the Exchange Server Database Utilities (Eseutil.exe). To determine how much free space is in the database, check event ID number 1221 or 1222. For more information about using Eseutil to defragment the Exchange database, see Eseutil /D Defragmentation Mode.

    • You can use the Database Troubleshooter tool included with Microsoft Exchange 2007 to clean up the database transaction log files or move the Exchange database. You can run the Database Troubleshooter tool from the Toolbox in the Exchange Management Console.

Related:

process name (process id) %3The database name has reached its maximum size of number MB. If the database cannot be restarted, an offline defragmentation may be performed to reduce its size.

Details
Product: Exchange
Event ID: 445
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: process name (process id) %3The database name has reached its maximum size of number MB. If the database cannot be restarted, an offline defragmentation may be performed to reduce its size.
   
Explanation

The disk volume that contains an Exchange database has reached the maximum allowed database size.

Exchange Server 2003 Standard Edition has the following limitations regarding mailbox stores and public folder stores:

  • Four storage groups.
  • Five databases per storage group.
  • One mailbox store database.
  • One public folder store database that is associated with a MAPI clients public folder tree.
  • Additional public folder stores. Each public folder store is associated with a general-purpose public folder tree.
  • Maximum 16-gigabyte (GB) limit per database.

When you exceed the 16-GB limit on any database, the Microsoft Exchange Information Store service shuts down automatically.

   
User Action

If you have exceeded the 16-GB database limit, you can temporarily increase the database size limit to 17 GB, and then restart the Microsoft Exchange Server Information Store service. Temporarily increasing the maximum size of the information store to 17 GB allows the Exchange database to mount while you reduce the amount of data on the database.

Important   To enable this functionality in Exchange Server 2003 Standard Edition, you must create the required new registry value.

For detailed information about how to temporarily increase the database size and resolve this error, see Microsoft Knowledge Base article 828070, “Exchange Server Mailbox Store Does Not Mount When the Mailbox Store Database Reaches the 16-GB Limit” at http://go.microsoft.com/fwlink/?LinkId=3052&kbid=828070.

Related: