Exchange Server 2010

  1. The database engine detected multiple threads illegally using the same database session to perform database operations. SessionId: ...
  2. The database engine detected multiple threads illegally using the same database session to perform database operations. SessionId: ...
  3. The database engine detected multiple threads illegally using the same database session to perform database operations. SessionId: ...
  4. The database engine detected multiple threads illegally using the same database session to perform database operations. SessionId: ...
  5. The database engine detected two different cursors of the same session illegally trying to update the same record at the ...
  6. The database engine detected two different cursors of the same session illegally trying to update the same record at the ...
  7. The database engine detected two different cursors of the same session trying to update the same record at the same time. ...
  8. The database engine detected two different cursors of the same session trying to update the same record at the same time. ...
  9. The database engine does not support the LCMapString() flags %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  10. The database engine does not support the LCMapString() flags %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  11. The database engine encountered an unexpected duplicate key on the table %4. One record has been dropped. For more information, ...
  12. The database engine encountered an unexpected duplicate key on the table %4. One record has been dropped. For more information, ...
  13. The database engine failed with error %1 while trying to log the commit of a transaction. To ensure database consistency, ...
  14. The database engine failed with error %1 while trying to log the commit of a transaction. To ensure database consistency, ...
  15. The database engine failed with error %4 while trying to log the commit of a transaction. To ensure database consistency, ...
  16. The database engine failed with error %4 while trying to log the commit of a transaction. To ensure database consistency, ...
  17. The database engine has begun replaying logfile %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  18. The database engine has begun replaying logfile %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  19. The database engine has completed the backup procedure successfully. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  20. The database engine has completed the backup procedure successfully. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  21. The database engine has stopped backup because it was halted by the client or the connection with the client failed. For ...
  22. The database engine has stopped backup because it was halted by the client or the connection with the client failed. For ...
  23. The database engine has stopped the backup with error %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  24. The database engine has stopped the backup with error %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  25. The database engine has successfully completed index cleanup on database '%4'. For more information, click http://www.mi ...
  26. The database engine has successfully completed index cleanup on database '%4'. For more information, click http://www.mi ...
  27. The database engine has successfully completed recovery steps. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  28. The database engine has successfully completed recovery steps. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  29. The database engine has successfully completed replay steps. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  30. The database engine has successfully completed replay steps. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  31. The database engine has successfully converted the database '%4' from format %5 to format %6. For more information, click ...
  32. The database engine has successfully converted the database '%4' from format %5 to format %6. For more information, click ...
  33. The database engine is converting the database '%4' from format %5 to format %6. For more information, click http://www. ...
  34. The database engine is converting the database '%4' from format %5 to format %6. For more information, click http://www. ...
  35. The database engine is initiating index cleanup of database '%1' as a result of a Windows version upgrade from %2.%3.%4 SP%5 ...
  36. The database engine is initiating index cleanup of database '%1' as a result of a Windows version upgrade from %2.%3.%4 SP%5 ...
  37. The database engine is initiating index cleanup of database '%1' as a result of a Windows version upgrade to %2.%3.%4 SP%5. ...
  38. The database engine is initiating index cleanup of database '%1' as a result of a Windows version upgrade to %2.%3.%4 SP%5. ...
  39. The database engine is initiating index cleanup of database '%4' as a result of a Windows version upgrade from %5.%6.%7 SP%8 ...
  40. The database engine is initiating index cleanup of database '%4' as a result of a Windows version upgrade from %5.%6.%7 SP%8 ...
  41. The database engine is initiating index cleanup of database '%4' as a result of a Windows version upgrade to %5.%6.%7 SP%8. ...
  42. The database engine is initiating index cleanup of database '%4' as a result of a Windows version upgrade to %5.%6.%7 SP%8. ...
  43. The database engine is initiating recovery steps. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  44. The database engine is initiating recovery steps. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  45. The database engine is rejecting update operations due to low free disk space on the log disk. For more information, click ...
  46. The database engine is rejecting update operations due to low free disk space on the log disk. For more information, click ...
  47. The database engine is restoring from backup. Restore will begin replaying log files in folder %1 and continue rolling forward ...
  48. The database engine is restoring from backup. Restore will begin replaying log files in folder %1 and continue rolling forward ...
  49. The database engine is restoring from backup. Restore will begin replaying logfiles in folder %4 and continue rolling forward ...
  50. The database engine is restoring from backup. Restore will begin replaying logfiles in folder %4 and continue rolling forward ...
  51. The database engine is starting a full backup. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  52. The database engine is starting a full backup. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  53. The database engine is starting an incremental backup. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  54. The database engine is starting an incremental backup. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  55. The database engine log disk is full. Deleting logfiles to recover disk space may make your database unstartable if the database ...
  56. The database engine log disk is full. Deleting logfiles to recover disk space may make your database unstartable if the database ...
  57. The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database ...
  58. The database engine lost one bad data record. It is highly recommended that an application-level integrity check of the database ...
  59. The database engine lost one bad data record. It is highly recommended that you run an application-level integrity check ...
  60. The database engine lost one bad data record. It is highly recommended that you run an application-level integrity check ...
  61. The database engine lost one or more bad columns of data in one record. It is highly recommended that an application-level ...
  62. The database engine lost one or more bad columns of data in one record. It is highly recommended that an application-level ...
  63. The database engine lost one or more bad columns of data in one record. It is highly recommended that you run an application-level ...
  64. The database engine lost one or more bad columns of data in one record. It is highly recommended that you run an application-level ...
  65. The database engine lost one page of bad data. It is highly recommended that an application-level integrity check of the ...
  66. The database engine lost one page of bad data. It is highly recommended that an application-level integrity check of the ...
  67. The database engine lost one page of bad data. It is highly recommended that you run an application-level integrity check ...
  68. The database engine lost one page of bad data. It is highly recommended that you run an application-level integrity check ...
  69. The database engine lost one table called %1. We highly recommended that you run an application-level integrity check of ...
  70. The database engine lost one table called %1. We highly recommended that you run an application-level integrity check of ...
  71. The database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database ...
  72. The database engine lost one table called %4. It is highly recommended that an application-level integrity check of the database ...
  73. The database engine repaired corruption on page %4 of database '%5'. Although the corruption has been repaired, the source ...
  74. The database engine repaired corruption on page %4 of database '%5'. Although the corruption has been repaired, the source ...
  75. The database engine started a new instance. You can safely ignore event ID 102 if it isn't logged together with ESE event ...