Exchange Server 2007

  1. The '{4}' registry entry for public folder store '{3}' on server {2} contains data. This database has experienced problems ...
  2. The '{4}' setting for database '{3}' on server {2} is set too high. This can cause excessive server load and client performance ...
  3. The '{4}' setting for database '{3}' on server {2} is set too low. This can cause excessive server load and client performance ...
  4. The '{4}' value for ASP.NET configuration on server {2} is set to '0.0.0.0'. This can cause Microsoft Exchange System Attendant ...
  5. The '{4}' value for mailbox store '{3}' on server {2} is missing. This will cause offline address book errors for {9} users ...
  6. The '{4}' value for public folder store '{3}' on server {2} is missing. This will cause public folder size discrepancies. ...
  7. The '{4}' value for SMTP instance '{3}' on server {2} has been altered from its default of 0. This will cause mail flow problems ...
  8. The '{4}' value for SMTP instance '{3}' on server {2} is greater than the global limit. This may cause oversized messages ...
  9. The '{4}' value for the Microsoft Exchange System Attendant service on server {2} is missing. This will cause reliability ...
  10. The '{5}' registry entry used by {0} is set on server {2} but {0} needs to be updated before this configuration setting will ...
  11. The '{5}' version on cluster node {2} differs from that on node {1} ({9} <> {8}). This may cause cluster failover problems. ...
  12. The .DLL file required for e-mail address generation could not be opened for verification because it could not be found in ...
  13. The accepted domain '{0}' cannot be removed or made external because it is referenced by the e-mail address policy templates ...
  14. The account '%1' provided valid credentials, but it does not have submit permissions on SMTP Receive connector '%2'; failing ...
  15. The account specified for the Microsoft Exchange Server Mailbox Manager Administrator is invalid. No mailboxes will be processed. ...
  16. The action could not be completed because of a conflict with the original item. The conflict may have occurred when an existing ...
  17. The action could not be completed because the Microsoft Exchange Information Store service is unavailable. Be sure the service ...
  18. The action could not be completed. Please try again. If the problem continues, contact technical support for your organization. ...
  19. The action that you attempted could not be performed because you have selected too many items. Select fewer than 500 items ...
  20. The activation of all modules took longer than expected to complete. Total Load Time: %1 Total Start Time: %2 Load Time Breakdown: ...
  21. The Active Clustered Mailbox role provides highly available, redundant e-mail storage and advanced scheduling services for ...
  22. The active directory access rule "{0}" does not contain valid public folder administrative right information. Valid public ...
  23. The Active Directory Application Mode (ADAM) Instance uninstallation process {0} failed with error code {1}. Check the Setup ...
  24. The Active Directory Application Mode (ADAM) LDAP Port on server {2} is not the default value and is listening on TCP/{1}. ...
  25. The Active Directory Application Mode (ADAM) SSL Port on server {2} has been customized and is listening on TCP/{1}. If this ...
  26. The Active Directory Connector (ADC) software on server {2} is from Exchange Server 2003 (initial release). A more recent ...
  27. The Active Directory Connector (ADC) software on server {2} is from Exchange Server 2003 Service Pack 1. A more recent version ...
  28. The Active Directory Connector server {2} is down or unreachable. This error could also be the result of a network or permissions ...
  29. The Active Directory forest functionality level has been raised. A modification to recipient policy '{3}' is required to ...
  30. The Active Directory forest functionality level has been raised. A modification to the system policies is required to avoid ...
  31. The Active Directory forest is prepared for Windows Server 2003. To avoid incorrect e-mail address generation when the forest ...
  32. The Active Directory forest is prepared for Windows Server 2003. To avoid mailbox re-homing issues when the forest is upgraded ...
  33. The Active Directory indicates that the database file %1 exists for the Microsoft Exchange Database "%2", however no such ...
  34. The Active Directory object for Recipient Update Service '{3}' is in conflict with another object. This may cause duplicate ...
  35. The Active Directory object for virtual directory '{1}' on '{0}' could not be created. This might be because the object already ...
  36. The Active Directory property "msExchMetabasePath" for the Mobile Sync virtual directory named "{0}" is set to "{1}" which ...
  37. The Active Directory property "msExchMetabasePath" for the Outlook Web Access virtual directory named "{0}" is set to "{1}" ...
  38. The Active Directory Schema is not up-to-date, and this user account is not a member of the 'Schema Admins' and/or 'Enterprise ...
  39. The Active Directory schema is not up-to-date. You must run setup with the "/ForestPrep" switch. If you have already done ...
  40. The Active Directory schema will be upgraded if you continue. Verify that the organization is ready for Exchange 2007 by ...
  41. The Active Directory schema will need to be upgraded (via the /PrepareSchema switch of Exchange Server 2007 setup) before ...
  42. The Active Directory site for Exchange server %1 was not determined in routing tables with timestamp %2. Recipients will ...
  43. The Active Directory topology service could not discover any route to connector %1 in the routing tables with the timestamp ...
  44. The AD object {0} is not visible to authenticated users. Authenticated users need "Read Properties", "List Object" and "List" ...
  45. The ADAM schema import process {0} failed with error code {1}. No schema has been imported into ADAM. Check the Setup Logs. ...
  46. The address list "{0}" is ambigous in Active Directory. Please make sure that the identity is referencing an unique address ...
  47. The address list '%1' has an invalid filter rule (PurportedSearch). The error is '%2'. No directory entries will belong to ...
  48. The Address List '%1' on directory %2 could not be loaded due to an error. Make sure that the Address List is configured ...
  49. The Address List service on {0} cannot be contacted to calculate proxy addresses or address list membership. {0} must have ...
  50. The address list specified "{0}" does not reference an existing address list. Such an object may not exist, is not yet fully ...
  51. The address space setting cannot contain both a "-" value and a specific domain name. This Send connector is managed by the ...
  52. The address template or display template for locale ID 1 could not be found, ignoring. Please install language support for ...
  53. The administrator for your organization has blocked access to resources that are stored on a Microsoft Windows SharePoint ...
  54. The administrator has paused public folder content replication for the organization. This option should only be set if an ...
  55. The amount of processor time not spent in the store.exe, inetinfo.exe, emsmta.exe, lsass.exe, w3wp.exe, exmgmt.exe, or mad.exe ...
  56. The amount of processor time not spent in the store.exe, inetinfo.exe, emsmta.exe, lsass.exe, w3wp.exe, or mad.exe processes ...
  57. The analyzer has detected problems with RPC health on the server %SERVERNAME% during the time ranges: %PRETTYRPCPROBLEMTIMERANGES%. ...
  58. The attachment you are trying to upload exceeds the maximum size limit for attachments allowed by your organization. For ...
  59. The Audio Compression Manager failed to convert from the audio format "%1" to audio format "%2": "%3". If this conversion ...
  60. The authentication package value (%1) is not supported on server %2. Check the Connections tab on the Connection Agreement. ...
  61. The auto attendant with ID {0} will be disabled. Calls to the numbers associated with this auto attendant will not be answered. ...
  62. The autoattendant should not be changed to have all options disabled. To disable an autoattendant, use the "disable-autoattendant" ...
  63. The Autodiscover service enables users who are running Outlook 2007 to locate the profile settings that are required to connect ...
  64. The average '{0}' is beyond the error threshold of {8}% of the reported capacity. The measured value is {9}. The measured ...
  65. The average value of '{0}' is {9}, which is greater than the threshold of {8}. The transaction log drive may be a bottleneck. ...
  66. The average value of '{0}' is {9}, which is greater than the threshold value of {8}. The log disk drive may be a bottleneck. ...
  67. The average value of '{0}' is {9}, which is greater than the threshold value of {8}. The transaction log drive may be a bottleneck. ...
  68. The average value of '{0}' is {9}, which is higher than the recommended maximum of {8}. This indicates the server has a processor ...
  69. The average value of '{0}' should always be below {8}%, and ideally should average below {7}%. The measured value is {9}%. ...
  70. The average value of '{0}' should always be below {8}%. The measured value is {9}%. This indicates the server has a processor ...
  71. The average value of '{0}' should be less than {8}% on a back-end server. Actual measured processor usage is {9}%. If this ...
  72. The average value of '{0}' should be less than {8}. The measured value is {9}. This indicates the server has a processor ...
  73. The background calendaring agent failed to logon to the MDB, or create a session object on the MDB:%1. The error code is ...
  74. The background calendaring agent failed to retrieve the token required for logon on the MDB:%1. The error code is %2. The ...
  75. The background calendaring agent failed with error code %1 while registering task. The rendering of large calendars with ...