Exchange Server 2007

  1. The log range read from the file "%4" at offset %5 for %6 bytes failed verification due to a range checksum mismatch. The ...
  2. The log signature of the existing logfile %4 doesn't match the logfiles from the backup set. Logfile replay cannot succeed ...
  3. The log version stamp of logfile %4 does not match the database engine version stamp. The logfiles may be the wrong version ...
  4. The logfile sequence in "%4" has been halted due to a fatal error. No further updates are possible for the databases that ...
  5. The logfiles %4 and %5 are not in a valid sequence. Logfile replay cannot succeed if there are gaps in the sequence of available ...
  6. The logon to Outlook Web Access failed. If the problem continues, contact technical support for your organization and tell ...
  7. The mail protocol was unable to handle one or more requests because they were unrecognized or invalid. Please notify your ...
  8. The mailbox database '{0}' is a recovery mailbox database. Only non-recovery mailbox databases are monitored by this task. ...
  9. The mailbox database '{0}' that you specified could not be found. Please refresh the workstation to make sure that the mailbox ...
  10. The mailbox database that you specified already exists as a recovery mailbox database. You cannot create a new mailbox database ...
  11. The mailbox database that you specified is already associated with a recovery mailbox database. Specified mailbox database: ...
  12. The mailbox database that you specified is not from the same storage group as one or more of the recovery mailbox databases ...
  13. The mailbox database you specified is a recovery mailbox database, you cannot apply this task to it. Specified mailbox database: ...
  14. The mailbox for %1 has exceeded the maximum mailbox size. This mailbox cannot send or receive messages. Incoming messages ...
  15. The mailbox GUID of an external system mailbox ('%1') does not match the information in the Active Directory for the mailbox. ...
  16. The mailbox policy '{0}' has users associated with it. Removing the mailbox policy will cause all of these users to have ...
  17. The Mailbox Role provides e-mail storage and advanced scheduling services for Microsoft Office Outlook users. The Mailbox ...
  18. The mailbox server %1 that hosts the mailbox for mobile device user %2 is running version %3]. Exchange ActiveSync only supports ...
  19. The Mailbox Server Role provides e-mail storage and advanced scheduling services for Microsoft Office Outlook users. The ...
  20. The mailbox store '{3}' on server {2} is {9} GB in size. It is recommended that the maximum database size does not exceed ...
  21. The mailbox store '{3}' on server {2} is {9} GB in size. Standard Editions of Microsoft Exchange Server 2003 Service Pack ...
  22. The mailbox store '{3}' on server {2} is {9} GB in size. Standard Editions of Microsoft Exchange Server are limited to a ...
  23. The mailbox that you specified is connected to "{0}". Only disconnected mailboxes can be reconnected. Specified mailbox: ...
  24. The mailbox that you specified resides in a recovery storage group. Mailboxes that reside in a recovery storage group cannot ...
  25. The mailbox you are accessing via Outlook Web Access is not configured to provide access to the type of data that you specified. ...
  26. The major version for routing group '{3}' appears to be changing very rapidly on server {2} ({9} version change(s) detected ...
  27. The major version for routing group '{3}' has been changed on server {2} while the tool was running. Latest major version ...
  28. The major version for routing group '{3}' may be changing rapidly on server {2} ({9} version change(s) detected over {8} ...
  29. The managed folder assistant audit log is enabled, but the path to the audit log is missing in Active Directory. Current ...
  30. The managed folder assistant could not configure the audit log. It will stop processing the current database: '%1'. It will ...
  31. The managed folder assistant detected a cycle among the policies in mailbox %1 that will enforce retention by moving items ...
  32. The managed folder assistant detected a cycle among the policies in mailbox '{0}' that will enforce retention policies by ...
  33. The managed folder assistant did not write to the audit log. It will stop processing the current database: '%1'. It will ...
  34. The Managed Folder Assistant failed to provision mailbox %1 because of corrupt data in the AD. Exception details: %2. To ...
  35. The managed folder assistant skipped processing all databases on the local server because it could not read the audit log ...
  36. The managed folder assistant skipped processing all databases on the local server because the audit log is enabled but the ...
  37. The managed folder assistant was unable to create the managed root folder %1 in mailbox %2 because the mailbox has several ...
  38. The managed folder assistant was unable to provision the managed default folder %1 in mailbox %2 because it was not found ...
  39. The managed folder assistant will not process mailboxes on database %1 because one or more managed folders in Active Directory ...
  40. The managed folder mailbox policy '{0}' for the mailbox '{1}' cannot be retrieved because it is linked to more than one managed ...
  41. The managed folder mailbox policy '{0}' is invalid because it is linked to more than one default managed folder of the same ...
  42. The managed folders, content settings, and policies that you create are applied to users' mailboxes only when the Managed ...
  43. The MAPI interface for Active Directory is disabled on server {2}. Microsoft Office Outlook clients will not be able to contact ...
  44. The max hop count was exceeded for the message. This code may occur if a loop situation exists between a sending server and ...
  45. The Max number of retries to load resolver configuration data on startup has been reached. The Microsoft Exchange Transport ...
  46. The MaxDSNSize registry value has not been set on server {2}. Implementing this option can increase overall performance and ...
  47. The MaxDumpsterSizePerStorageGroup, MaxDumpsterTime, MaxReceiveSize, and MaxRecipientEnvelopeLimit properties are not used ...
  48. The MaxFieldLength HTTP parameter on server {2} has not been set to 32768. In large environments the absence of this value ...
  49. The maximum allowable incoming message size ({8} KB) does not match the outgoing size ({9} KB). These values should be the ...
  50. The maximum Extensible Storage Engine (ESE) cache on server {2} has been increased and may cause low virtual memory conditions. ...
  51. The maximum Extensible Storage Engine (ESE) cache on server {2} is set too high and is causing low virtual memory conditions. ...
  52. The maximum incoming message size maybe set too low. An administrative error may have occurred. Maximum message size is {9} ...
  53. The maximum LDAP page size for the default query policy is set too high and may cause performance problems. The default of ...
  54. The maximum non-paged pool memory on server {2} is over the error threshold of {8} MB. System instability may occur. Current ...
  55. The maximum non-paged pool memory on server {2} is over the error threshold of {8} MB. This may cause system instability. ...
  56. The maximum non-paged pool memory on server {2} is over the warning threshold of {8} MB. System instability may occur. Current ...
  57. The maximum non-paged pool memory on server {2} is over the warning threshold of {8} MB. This may cause system instability. ...
  58. The maximum number of cached views ('msExchMaxCachedViews') for database {3} on server {2} is set too low. This can cause ...
  59. The maximum number of cached views (msExchMaxCachedViews) for database {3} on server {2} is set too high. This can cause ...
  60. The maximum number of Extensible Storage Engine (ESE) open tables for storage group '{3}' on server {2} is hard-coded. This ...
  61. The maximum number of mailboxes that can be moved at the same time has been exceeded. Please select {0} or fewer mailboxes. ...
  62. The maximum outgoing message size maybe set too low. An administrative error may have occurred. Maximum message size is {9} ...
  63. The maximum value of '{0}' is {9}, which is greater than the threshold of {8}. The transaction log drive may be a bottleneck. ...
  64. The MaxRequestBytes HTTP parameter on server {2} has not been set to 32768. In large environments the absence of this value ...
  65. The meeting organizer has chosen not to receive responses for this update. Select your response in order to update your calendar. ...
  66. The memory settings for this server are not optimal for Exchange. For information about how to optimize memory usage in Exchange ...
  67. The message could not be created because one of the contacts could not be found. The contact may have been moved or deleted. ...
  68. The message could not be delivered because the recipient's destination email system is unknown or invalid. Please check the ...
  69. The message could not be delivered because you do not have create permissions on this folder or it is only available to folder ...
  70. The message could not be received from domain-secured domain %1 because of a configuration error on Receive connector %2. ...
  71. The message could not be redirected to an alternate-recipient because that recipient had previously redirected the message ...
  72. The message failed to be submitted because the storage limit for the mailbox that is submitting the message has been exceeded. ...
  73. The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed ...
  74. The message is too large for the local quota. For example, a remote Exchange user may have delivery restrictions set with ...
  75. The message reached the recipient's e-mail system, but delivery was refused. Attempt to resend the message. If it still fails, ...