Exchange Server 2007

  1. Microsoft Exchange OLEDB was unable to either create an event sink object or get necessary interface(s) from the sink class ...
  2. Microsoft Exchange OLEDB was unable to enable store events in mailbox '%1' after the mailbox was moved. HRESULT = %2. Any ...
  3. Microsoft Exchange OLEDB was unable to initialize event system correctly. Support for store event may have been disabled. ...
  4. Microsoft Exchange OLEDB was unable to initialize the event binding. BindingID = %1. "%2" is an invalid value for the "%3" ...
  5. Microsoft Exchange OLEDB was unable to initialize the event binding. BindingID = %1. The "%2" event binding property is not ...
  6. Microsoft Exchange OLEDB was unable to load event binding since incompatible combination of event methods are specified. ...
  7. Microsoft Exchange Server 2007 Setup Parameter Help Install/Uninstall Server Role Usage: Setup /mode: /roles: -Install/Uninstall ...
  8. Microsoft Exchange Server 2007 Setup Parameter Help Install/Uninstall Server Role Usage: Setup.com /mode: /roles: /OptionalParameters ...
  9. Microsoft Exchange Server enables users to send and receive e-mail, schedule meetings, receive faxes, and receive voice mail. ...
  10. Microsoft Exchange Server has already been installed on this machine. If you want to make changes to the current installation, ...
  11. Microsoft Exchange Server is currently installed on this computer. This wizard will allow you to add Exchange server roles ...
  12. Microsoft Exchange Server is currently installed on this computer. This wizard will allow you to remove Exchange server roles ...
  13. Microsoft Exchange Server is not configured to support details templates in your language (English). Contact your system ...
  14. Microsoft Exchange setup does not support the use of the DisasterRecovery action when running on cluster nodes. See the Microsoft ...
  15. Microsoft Exchange Setup has detected that you are running in a cluster environment. See http://www.microsoft.com/exchange ...
  16. Microsoft Exchange setup has detected that you are running in an environment which is not supported for the number of physical ...
  17. Microsoft Exchange System Attendant detected the name of its Administrative Group has been changed to '%1'. It will restart ...
  18. Microsoft Exchange System Attendant detected the name of its Organization has been changed to '%1'. It will restart all its ...
  19. Microsoft Exchange System Attendant did not find any security key data for Exchange Server '%1'. This is normal for servers ...
  20. Microsoft Exchange System Attendant does not have sufficient rights to read Exchange configuration objects in Active Directory. ...
  21. Microsoft Exchange System Attendant does not have sufficient rights to read Exchange configuration objects in Active Directory. ...
  22. Microsoft Exchange System Attendant failed to add the local computer as a member of the DS group object '%1'. Please stop ...
  23. Microsoft Exchange System Attendant failed to read the membership of group '%1'. Error code '%2'. Please check whether the ...
  24. Microsoft Exchange System Attendant failed to read the membership of the universal security group '%1'; the error code was ...
  25. Microsoft Exchange System Attendant has detected a discrepancy in the published security data for Exchange server '%1'. This ...
  26. Microsoft Exchange System Attendant has detected that the local computer is not a member of group '%1'. System Attendant ...
  27. Microsoft Exchange System Attendant has detected that the password of the legacy exchange service account has been modified. ...
  28. Microsoft Exchange System Attendant has detected that the system attendant object in the DS has been modified. System Attendant ...
  29. Microsoft Exchange System Attendant has generated new security keys for Exchange server '%1'. Any passwords required by this ...
  30. Microsoft Exchange System Attendant is querying for Outlook Anywhere back-ends to reset RPC Proxy Valid Ports. Config DC='%1' ...
  31. Microsoft Exchange System Attendant was unable to find the Exchange server object named '%1' in Active Directory. All known ...
  32. Microsoft Exchange System Attendant was unable to find the Exchange server object named '%1' in the Active Directory. All ...
  33. Microsoft Exchange versions earlier than Exchange Server 2003 do not support Outlook Anywhere. The following servers cannot ...
  34. Microsoft Exchange was unable to initialize the Content Filter agent. Check the access control lists (ACLs) on the files ...
  35. Microsoft Exchange was unable to initialize the Content Filter agent. It could not allocate sufficient memory for an internal ...
  36. Microsoft Exchange was unable to initialize the Content Filter agent. Notification of the file system change could not be ...
  37. Microsoft Exchange was unable to send the following items to your mobile device. These items have not been deleted. You should ...
  38. Microsoft Forefront Security for Exchange Server helps protect your Exchange Servers from viruses, worms, and other malware. ...
  39. Microsoft Internet Information Services Common Files is required. Install the component via Control Panel, Add or Remove ...
  40. Mode in which traces are logged to disk. If SequentialLogging (default) is specified, traces are logged sequentially. If ...
  41. Modified occurrence (StartTime: {0}, EndTime: {1}) is crossing or overlapping an adjacent occurrence (StartTime: {2}, EndTime ...
  42. Monitoring the availability, configuration, and performance of your Exchange servers allows you to proactively solve problems ...
  43. More than %1 single-client RPC error or latency warnings were observed in a %2 second(s) period. No further such warnings ...
  44. More than 500 mailboxes in the entire forest have delivery restrictions set where at least one distribution group is used ...
  45. More than 8 logical processors exist on Exchange server {2}. If this server has more than 8 physical processors installed, ...
  46. More than 8 processors were detected for the Exchange server {2}. If this server has more than 8 physical processors installed ...
  47. More than 8 processors were detected for the Exchange server {2}. If this server has more than 8 physical processors installed, ...
  48. More than 800 address lists exist in the organization. If the Recipient Update Service is responsible for these, severe latencies ...
  49. More than 800 global address lists exist in the organization. If the Recipient Update Service is responsible for these, severe ...
  50. More than one computer account in Active Directory has '{5}' set to '{3}'. This will result in Kerberos authentication failures ...
  51. More than one IIS Web Service Extensions were found with the group ID {0} and the file {1}. Please remove the duplicate entries ...
  52. More than one network interface on server {2} has a default IP gateway listed. Communication errors may occur if these network ...
  53. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to distribution group '{3}'. The number ...
  54. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to server {1}. The number of such ...
  55. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to the mailbox store '{3}'. The number ...
  56. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to the public folder '{3}'. The number ...
  57. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to the public folder store '{3}'. ...
  58. More than {6}% of the messages in the '{4}' queue on server {2} appear to be addressed to user '{1}'. The number of such ...
  59. More than {8} Exchange mailbox stores exist in the organization. To avoid logon issues with Outlook Web Access, install the ...
  60. More than {8} Exchange servers exist in the organization. Exchange is limited to {1} total servers. Current number of Exchange ...
  61. More than {8} messaging connectors exist in the organization. This may cause additional load on Exchange and Active Directory ...
  62. Most common possible causes are 1)The message contains more than 250 attachments. More than 250 attachments cause the MAPI_E_TOO_BIG ...
  63. Most of the RPC load is in the category '{1}'. This category accounts for {2} RPC operations/second, out of the total rate ...
  64. Move Collection Commands/sec is the number of MoveCollection commands that are processed each second. Clients that are running ...
  65. Move Collection Total is the total number of MoveCollections requests that have been processed since the service was started. ...
  66. Move Items Commands/sec is the number of MoveItems commands that are processed each second. Clients use this command to move ...
  67. Move the Edge Subscription file to a directory location on a Hub Transport server in your Exchange organization. Exchange ...
  68. Move the transaction log files from the temporary folder to a safe backup location. These files may be required for full ...
  69. Move the transaction log files from the temporary folder to a safe backup location. These files may be required for full ...
  70. Move the transaction log files from the temporary folder to a safe backup location. These files may be required for full ...
  71. Move the transaction log files from the temporary folder to a safe backup location. These files may be required for full ...
  72. Moving clustered mailbox server '{0}' to '{1}' failed because of a transient communication error with the Windows Cluster ...
  73. Moving mailbox '{0}' to server '{1}' is not supported, because the target server is required to be Exchange 2003 or later. ...
  74. Moving mailbox: {0} ({1}) to database: {2}. The operation can take a long time and the mailbox will be inaccessible until ...
  75. Moving mailbox: {0} ({1}) to database: {2}. This operation will only modify the mailbox's Active Directory configuration. ...