Exchange Server 2007
- The content of this encrypted message cannot be displayed because this version of Microsoft Exchange Server does not support ...
- The content settings that you apply to a managed folder control retention policies that limit the lifespan of items and allow ...
- The contents of the container cannot be seen because the recalculation of the directory hierarchy is not yet complete. Try ...
- The conversion of the Universal Distribution Group "%1" to a Universal Security Group has been aborted on database "%2" because ...
- The CopyEdbFilePath that you specified is not on a fixed drive. Only fixed (non-removable) storage can be used for local ...
- The current Exchange Server installation path does not have sufficient disk space to install the server roles selected. Please ...
- The current processor speed on server {2} is less than the maximum possible speed. Maximum clock speed is {8}. Current clock ...
- The customer name specified does not match the name in data file. Specify the correct customer name, or use a different data ...
- The data files folder or log files folder is not empty. Select an empty folder to store Active Directory Application Mode ...
- The database "%1" cannot be dismounted because a backup of the database is in progress. (Note that if a backup was recently ...
- The database "%3" has been copied from the server %1 to the server %2. In the Microsoft Exchange System Manager, indicate ...
- The database %4 created at %5 was not recovered. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database %4 created at %5 was not recovered. The recovered database was created at %5. For more information, click h ...
- The database %4 has reached its maximum size of %5 MB. If the database cannot be restarted, an offline defragmentation may ...
- The database cannot be moved until continuous replication is suspended. Please use the Suspend-StorageGroupCopy cmdlet in ...
- The database could not be opened because a log file is missing or corrupted. The Microsoft Exchange Transport service is ...
- The database could not be opened because the checkpoint file (.chk) is missing or corrupted. The Microsoft Exchange Transport ...
- The database could not be opened because the database file does not match the log files. The Microsoft Exchange Transport ...
- The database could not be opened because the log file path that was supplied is invalid. The Microsoft Exchange Transport ...
- The database disk is full. Deleting logfiles to recover disk space may make the database unstartable if the database file(s) ...
- The database engine (%5.%6.%7.%8) started a new instance (%4). For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine could not access the file called %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine could not find the entrypoint %4 in the file %5. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine could not find the file or folder called %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine detected multiple threads illegally using the same database session to perform database operations. SessionId: ...
- The database engine detected two different cursors of the same session illegally trying to update the same record at the ...
- The database engine does not support the LCMapString() flags %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine encountered an unexpected duplicate key on the table %4. One record has been dropped. For more information, ...
- The database engine failed with error %4 while trying to log the commit of a transaction. To ensure database consistency, ...
- The database engine has begun replaying logfile %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine has completed the backup procedure successfully. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine has stopped backup because it was halted by the client or the connection with the client failed. For ...
- The database engine has stopped the backup with error %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine has successfully completed index cleanup on database '%4'. For more information, click http://www.mi ...
- The database engine has successfully completed recovery steps. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine has successfully completed replay steps. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine has successfully converted the database '%4' from format %5 to format %6. For more information, click ...
- The database engine is converting the database '%4' from format %5 to format %6. For more information, click http://www. ...
- The database engine is initiating index cleanup of database '%4' as a result of a Windows version upgrade from %5.%6.%7 SP%8 ...
- The database engine is initiating index cleanup of database '%4' as a result of a Windows version upgrade to %5.%6.%7 SP%8. ...
- The database engine is initiating recovery steps. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine is rejecting update operations due to low free disk space on the log disk. For more information, click ...
- The database engine is restoring from backup. Restore will begin replaying logfiles in folder %4 and continue rolling forward ...
- The database engine is starting a full backup. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine is starting an incremental backup. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine log disk is full. Deleting logfiles to recover disk space may make your database unstartable if the database ...
- The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database ...
- The database engine lost one or more bad columns of data in one record. It is highly recommended that an application-level ...
- The database engine lost one page of bad data. It is highly recommended that an application-level integrity check of the ...
- The database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database ...
- The database engine stopped the instance (%4) with error (%5). For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine stopped the instance (%4). For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database engine updated %4 index entries in database %5 because of a change in the NLS version. This message is informational ...
- The database engine was unable to updated index entries in database %5 because the database is read-only. For more information, ...
- The database file %2 for %1 is missing. Re-seeding of this storage group is now required. Use the Update-StorageGroupCopy ...
- The database file for mailbox store '{3}' on Exchange server {2} appears to be stored on a network share. This is not recommended ...
- The database file for public store '{3}' on Exchange server {2} appears to be stored on a network share. This is not recommended ...
- The database file path that you specified for the local continuous replication copy is in use by another database on the ...
- The database files for mailbox store '{3}' on server {2} appear to be located on the same disk volume as the transaction ...
- The database files in this store were replaced with older versions by an offline restore. To use the restored files, open ...
- The database page read from the file "%4" at offset %5 (database page %10) for %6 bytes failed verification due to a page ...
- The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification because it contains ...
- The database page read from the file "%4" at offset %5 (database page %8) for %6 bytes failed verification. Bit %7 was corrupted ...
- The database page read from the file "%4" at offset %5 (database page %9) for %6 bytes failed verification. Bit %8 was corrupted ...
- The database page read from the file "%4" at offset %5 for %6 bytes failed verification due to a page number mismatch. The ...
- The database signature does not match the log signature for database %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- The database that you specified is a public folder database and cannot be enabled for local continuous replication because ...
- The database that you specified is not enabled for local continuous replication. Therefore, you cannot use "-CopyEdbFilePath ...
- The database that you specified is the last mailbox database in the server and cannot be removed. A mailbox server must have ...
- The database to be accessed from the server is not mounted or is not available. Please see inner exception for more information. ...
- The databases have not been restored to this machine. You cannot restore an incremental backup until a full backup has been ...
- The Date Received search property is the only property can access the Greater than or Less than symbols. Any other property ...
- The dedicated heartbeat connection on cluster {2} is not set to priority {8}. Use the 'Cluster Administrator' program to ...
- The default certificate attribute for local Edge server has been updated. If this Edge server is subscribed, you must subscribe ...
- The default certificate for the local server was corrupted or missing in the Active Directory. The problem has been fixed. ...