Exchange Server 2010

  1. The copy of mailbox database "{0}" on server "{3}" has been removed. If necessary, manually delete the database copy's files ...
  2. The CopySystemFolderPath has to be the same as the CopyLogFolderPath. CopySystemFolderPath: '{0}'; CopyLogFolderPath: '{1}' ...
  3. The CSV file contains more than {0} contacts. Please split the CSV file into two or more CSV files that contain the header ...
  4. The CSV file contains one or more unrecognizable columns. Please remove these columns and re-submit the file. Unknown columns: ...
  5. The CSV file is too large. The maximum file size is 10 MB. Please divide it into two or more files and submit them separately. ...
  6. The CSV file you submitted contains both the Password and the FederatedIdentity columns. The CSV file can contain only one ...
  7. The current count of messages received and acknowledged before relay completed. This provides the current count of queued ...
  8. The current Exchange Server installation path does not have sufficient disk space to install the server roles selected. Please ...
  9. The current organization is a forest-wide organization. Please specify the Identity parameter to select the tenant you want ...
  10. The current processor speed on server {2} is less than the maximum possible speed. Maximum clock speed is {8}. Current clock ...
  11. The Customer Experience Improvement Program (CEIP) is set to False by your organization's administrator. As a result, this ...
  12. The Customer Experience Improvement Program (CEIP) isn't specified for this server. For more information, see the Privacy ...
  13. The Customer Experience Improvement Program collects information about computer hardware and how you use Exchange, without ...
  14. The Customer Experience Improvement Program has been set to True by your organization administrator, but /customerfeedbackenabled:true ...
  15. The customer name specified does not match the name in data file. Specify the correct customer name, or use a different data ...
  16. The data collected from each server is written to a file named "CounterData. . .csv". The summary report will be written ...
  17. The data marked with a yellow exclamation mark may be inaccurate due to errors that happened while the data was being collected. ...
  18. The data move replication constraint cannot be set to {0} on mailbox database {1} because there is only one database copy ...
  19. The database "%1" cannot be dismounted because a backup of the database is in progress. (Note that if a backup was recently ...
  20. The database "%1" cannot be dismounted because a backup of the database is in progress. (Note that if a backup was recently ...
  21. The database "%3" has been copied from the server %1 to the server %2. In the Exchange Management Console, indicate that ...
  22. The database "%3" has been copied from the server %1 to the server %2. In the Exchange Management Console, indicate that ...
  23. The database "{0}" is currently hosted on server "{1}". Use Move-ActiveMailboxDatabase to move the active copy of the database ...
  24. The database %1 has reached its maximum size of %2 MB. If the database cannot be restarted, an offline defragmentation may ...
  25. The database %1 has reached its maximum size of %2 MB. If the database cannot be restarted, an offline defragmentation may ...
  26. The database %4 created at %5 was not recovered. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  27. The database %4 created at %5 was not recovered. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  28. The database %4 created at %5 was not recovered. The recovered database was created at %5. For more information, click h ...
  29. The database %4 created at %5 was not recovered. The recovered database was created at %5. For more information, click h ...
  30. The database %4 has reached its maximum size of %5 MB. If the database cannot be restarted, an offline defragmentation may ...
  31. The database %4 has reached its maximum size of %5 MB. If the database cannot be restarted, an offline defragmentation may ...
  32. The database '{0}' isn't within the current user's management scope. At least one server with a copy of the database must ...
  33. The database '{0}' was not mounted because errors occurred either while validating database copies for possible activation, ...
  34. The database availability group has the same witness server and alternate witness server {0}, but the witness directory is ...
  35. The database availability group member {0} was removed, but cleanup didn't complete. Please verify that the Cluster service ...
  36. The database configuration is invalid and needs to be re-created. Use the Remove-MailboxDatabase cmdlet to remove the existing ...
  37. The database copy '{0}' could not be suspended because the operation is not applicable for a copy that is in Seedingsource ...
  38. The database copy was successfully suspended, but the SuspendComment could not be set. Please retry the command to set SuspendComment ...
  39. The database could not allocate memory. Please close some applications to make sure you have enough memory for Exchange Server. ...
  40. The database could not allocate memory. Please close some applications to make sure you have enough memory for Exchange Server. ...
  41. The database could not be opened because a log file is missing or corrupted. The Microsoft Exchange Transport service is ...
  42. The database could not be opened because a log file is missing or corrupted. The Microsoft Exchange Transport service is ...
  43. The database could not be opened because it does not belong with the current set of log files. The Microsoft Exchange Transport ...
  44. The database could not be opened because it does not belong with the current set of log files. The Microsoft Exchange Transport ...
  45. The database could not be opened because the checkpoint file (.chk) is missing or corrupted. The Microsoft Exchange Transport ...
  46. The database could not be opened because the checkpoint file (.chk) is missing or corrupted. The Microsoft Exchange Transport ...
  47. The database could not be opened because the database file does not match the log files. The Microsoft Exchange Transport ...
  48. The database could not be opened because the database file does not match the log files. The Microsoft Exchange Transport ...
  49. The database could not be opened because the log file path that was supplied is invalid. The Microsoft Exchange Transport ...
  50. The database could not be opened because the log file path that was supplied is invalid. The Microsoft Exchange Transport ...
  51. The database could not be opened because there is another process using it. The Microsoft Exchange Transport service is shutting ...
  52. The database could not be opened because there is another process using it. The Microsoft Exchange Transport service is shutting ...
  53. The database could not be opened because there is no such database found. The Microsoft Exchange Transport service is shutting ...
  54. The database could not be opened because there is no such database found. The Microsoft Exchange Transport service is shutting ...
  55. The database could not be started because a critical database file has the read-only attribute set. The Microsoft Exchange ...
  56. The database could not be started because a critical database file has the read-only attribute set. The Microsoft Exchange ...
  57. The database could not be started because the distinguished name (DN) %2 of mailbox database "%3" does not match the DN of ...
  58. The database could not be started because the distinguished name (DN) %2 of mailbox database "%3" does not match the DN of ...
  59. The database disk is full. Deleting log files that are on the disk containing the database in order to recover disk space ...
  60. The database disk is full. Deleting log files that are on the disk containing the database in order to recover disk space ...
  61. The database disk is full. Deleting logfiles to recover disk space may make the database unstartable if the database file(s) ...
  62. The database disk is full. Deleting logfiles to recover disk space may make the database unstartable if the database file(s) ...
  63. The database drive for path {0} doesn't have enough free space for incremental reseed. Free space needed is {1}. Free space ...
  64. The database engine (%5.%6.%7.%8) is starting a new instance (%4). For more information, click http://www.microsoft.com/contentredirect.asp. ...
  65. The database engine (%5.%6.%7.%8) is starting a new instance (%4). For more information, click http://www.microsoft.com/contentredirect.asp. ...
  66. The database engine attempted a clean write operation on page %4 of database %5. This acton was performed in an attempt to ...
  67. The database engine attempted a clean write operation on page %4 of database %5. This acton was performed in an attempt to ...
  68. The database engine attempted a clean write operation on page %4 of database %5. This was performed in an attempt to correct ...
  69. The database engine attempted a clean write operation on page %4 of database %5. This was performed in an attempt to correct ...
  70. The database engine could not access the file called %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  71. The database engine could not access the file called %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  72. The database engine could not find the entrypoint %4 in the file %5. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  73. The database engine could not find the entrypoint %4 in the file %5. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  74. The database engine could not find the file or folder called %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  75. The database engine could not find the file or folder called %4. For more information, click http://www.microsoft.com/contentredirect.asp. ...