Exchange Server 2010
- The database engine detected multiple threads illegally using the same database session to perform database operations. SessionId: ...
- The database engine detected multiple threads illegally using the same database session to perform database operations. SessionId: ...
- The database engine detected multiple threads illegally using the same database session to perform database operations. SessionId: ...
- 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 detected two different cursors of the same session illegally trying to update the same record at the ...
- The database engine detected two different cursors of the same session trying to update the same record at the same time. ...
- The database engine detected two different cursors of the same session trying to update the same record at the same time. ...
- The database engine does not support the LCMapString() flags %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
- 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 encountered an unexpected duplicate key on the table %4. One record has been dropped. For more information, ...
- The database engine failed with error %1 while trying to log the commit of a transaction. To ensure database consistency, ...
- The database engine failed with error %1 while trying to log the commit of a transaction. To ensure database consistency, ...
- The database engine failed with error %4 while trying to log the commit of a transaction. To ensure database consistency, ...
- 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 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 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 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 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 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 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 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 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 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 '%1' as a result of a Windows version upgrade from %2.%3.%4 SP%5 ...
- The database engine is initiating index cleanup of database '%1' as a result of a Windows version upgrade from %2.%3.%4 SP%5 ...
- The database engine is initiating index cleanup of database '%1' as a result of a Windows version upgrade to %2.%3.%4 SP%5. ...
- The database engine is initiating index cleanup of database '%1' as a result of a Windows version upgrade to %2.%3.%4 SP%5. ...
- 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 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 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 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 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 log files in folder %1 and continue rolling forward ...
- The database engine is restoring from backup. Restore will begin replaying log files in folder %1 and continue rolling forward ...
- The database engine is restoring from backup. Restore will begin replaying logfiles in folder %4 and continue rolling forward ...
- 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 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 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 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 bad data record. It is highly recommended that an application-level integrity check of the database ...
- The database engine lost one bad data record. It is highly recommended that you run an application-level integrity check ...
- The database engine lost one bad data record. It is highly recommended that you run an application-level integrity check ...
- 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 or more bad columns of data in one record. It is highly recommended that an application-level ...
- The database engine lost one or more bad columns of data in one record. It is highly recommended that you run an application-level ...
- The database engine lost one or more bad columns of data in one record. It is highly recommended that you run 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 page of bad data. It is highly recommended that an application-level integrity check of the ...
- The database engine lost one page of bad data. It is highly recommended that you run an application-level integrity check ...
- The database engine lost one page of bad data. It is highly recommended that you run an application-level integrity check ...
- The database engine lost one table called %1. We highly recommended that you run an application-level integrity check of ...
- The database engine lost one table called %1. We highly recommended that you run an application-level integrity check of ...
- The database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database ...
- The database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database ...
- The database engine repaired corruption on page %4 of database '%5'. Although the corruption has been repaired, the source ...
- The database engine repaired corruption on page %4 of database '%5'. Although the corruption has been repaired, the source ...
- The database engine started a new instance. You can safely ignore event ID 102 if it isn't logged together with ESE event ...