Exchange Server 2010

  1. An incoming replication message was processed Type: %1 Message ID: %2 Database "%10". CNSET: %3 CNSET(FAI): %4 RFIs: %5 %6 ...
  2. An incoming replication message was processed. Type: %1 Message ID: %2 Database "%10". CN min: %3 CN max: %4 RFIs: %5 %6 ...
  3. An incoming replication message was processed. Type: %1 Message ID: %2 Database "%6". CNSET: %3 CNSET(FAI): %4 Server: %5 ...
  4. An incoming replication message was processed. Type: %1 Message ID: %2 Folder: %3 Database "%10". CN min: %4 CN max: %5 MIDs: ...
  5. An incoming replication message was processed. Type: %1 Message ID: %2 Folder: %3 Database "%10". CNSET: %4 CNSET(FAI): %5 ...
  6. An incoming replication message was processed. Type: %1 Message ID: %2 Folder: %3 Database "%7". CN min: %4 CN max:%5 Server: ...
  7. An incoming replication message was processed. Type: %1 Message ID: %2 Folder: %3 Database "%7". CNSET: %4 CNSET(FAI): %5 ...
  8. An inconsistency in the Active Directory was detected: {0} This may be a defect in the product and this should be reported ...
  9. An installation for 2 is currently suspended. You must undo the changes made by that installation to continue. Do you want ...
  10. An internal conflict occured while attempting a {1} on database {0} because a {2} was already in progress. If in Third Party ...
  11. An internal copy (for seeding or analysis purposes) is starting. The streaming ESE backup APIs are being used for the transfer ...
  12. An internal error has occurred during directory replication. Stop and then restart the directory service. Then try directory ...
  13. An internal error has occurred when trying to access the Discovery system mailbox, which contains internal information about ...
  14. An internal processing error due to a bad parameter has occurred. Try restarting the Exchange Management Console or the Microsoft ...
  15. An internal processing error due to a bad parameter has occurred. Try restarting the Microsoft Exchange Information Store ...
  16. An internal processing error has occurred while administering the information store. Try restarting the Exchange Information ...
  17. An internal processing error has occurred while administering the information store. Try restarting the Microsoft Exchange ...
  18. An internal processing error has occurred. There's a problem with the information store. Try restarting the Administrator ...
  19. An internal processing error has occurred. Try restarting the Exchange Information Store service. Examine the Application ...
  20. An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information ...
  21. An internal processing error has occurred: there is a problem with the Information Store. Try restarting the Microsoft Exchange ...
  22. An internal processing error occurred. A subordinate class is referencing itself as a superclass. Try restarting the Microsoft ...
  23. An internal processing error occurred. No attribute values were found. Try restarting the Microsoft Management Console, the ...
  24. An internal processing error occurred. No directory attributes were found. Try restarting the Microsoft Management Console, ...
  25. An internal processing error occurred. No directory service entries were found. Try restarting the Microsoft Management Console, ...
  26. An internal processing error occurred. No directory service entry was found. Try restarting the Microsoft Management Console, ...
  27. An internal processing error occurred. No value was found for the attribute type. Try restarting the Microsoft Management ...
  28. An internal processing error occurred. The RDN attribute was not found for an object in the schema. Try restarting the Microsoft ...
  29. An invalid '{1}' value ({4}) was found for server {2}. This may prevent the '{0}' service from resolving DNS names correctly. ...
  30. An invalid character '{0}' was found at index {1} of "{2}" at index {3} of property {4}. Only ASCII characters are allowed ...
  31. An invalid checksum record in logfile %4 was patched using its shadow sector copy. For more information, click http://ww ...
  32. An invalid custom response for message rejections is configured on server {2}. Responses must start with '{7}'. Current response: ...
  33. An invalid event history watermark has been detected by background cleanup. The watermark will be deleted. Database: '%1'. ...
  34. An invalid parameter was encountered during directory replication. Stop and then restart the directory service. Then try ...
  35. An invalid time range was specified. The value in the StartDate parameter must be earlier than the value in the EndDate parameter. ...
  36. An invalid update has been made to the comment field on Managed Folder '{0}'. The MustDisplayComment field has been set on ...
  37. An invalid value for the UnscopedTopLevel parameter was specified. Either specify $True to create an unscoped top level role ...
  38. An issue with the '{0}' service on {2} was found. This service is required for local transport submission from the Mailbox ...
  39. An item conflict occurred in public folder %1. Message ID: %2 From: %3 Subject: %4 Received: %5 Database "%7". Notification(s): ...
  40. An item conflict occurred in public folder %1. Message ID: %2 From: %3 Subject: %4 Received: %5 Database "%8". Notification(s): ...
  41. An OCS User Event Notification session with end point %1 (Call-ID: %2) will be terminated due to a signaling error. Additional ...
  42. An older seed request for database '%1' that had finished processing has been automatically cleaned up after a period of ...
  43. An older version of '{5}' is present in the Windows 'system32' folder on server {2}. This may cause problems with upgrades. ...
  44. An older version of a software time zone update for Windows has been detected. Uninstall the update from Microsoft Knowledge ...
  45. An older version of Active Directory Application Mode (ADAM) is already installed on this computer. You must update to ADAM ...
  46. An open proxy test tries to connect to the sender's originating IP address with an SMTP request. If the Exchange Edge Transport ...
  47. An operation has encountered a fatal error. The database may be corrupted. The Microsoft Exchange Transport service is shutting ...
  48. An operation has encountered a fatal error. The database may be fragmented and manual offline defragmentation using ESEUTIL ...
  49. An operation has encountered a fatal error. There wasn't enough disk space to complete the operation. The Microsoft Exchange ...
  50. An outbound call to "%1" couldn't be established because the UM IP gateway that UM attempted to use for this call, "%2", ...
  51. An outbound call to %1 couldn't be established. The selected outbound gateway "%2" returned the error "%3". The caller ID ...
  52. An outgoing replication message resulted in a non-delivery report. Type: %1 Message ID: %2 Database "%6". NDR recipients: ...
  53. An outgoing replication message resulted in a non-delivery report. Type: %1 Message ID: %2 Database "%8". NDR recipients: ...
  54. An outgoing replication message resulted in a non-delivery report. Type: %1 Message ID: %2 Database "%8". NDR recipients: ...
  55. An outgoing replication message resulted in a non-delivery report. Type: %1 Message ID: %2 Folder: %3 Database "%7". NDR ...
  56. An outgoing replication message resulted in a non-delivery report. Type: %1 Message ID: %2 Folder: %3 Database "%9". NDR ...
  57. An outgoing replication message resulted in a non-delivery report. Type: %1 Message ID: %2 Folder: %3 Database "%9". NDR ...
  58. An outgoing replication message was issued. Type: %1 Message ID: %2 Database "%10" CN min: %3, CN max: %4 RFIs: %5 %6 IDCN ...
  59. An outgoing replication message was issued. Type: %1 Message ID: %2 Database "%10". CNSET: %3 CNSET(FAI): %4 RFIs: %5 %6 ...
  60. An outgoing replication message was issued. Type: %1 Message ID: %2 Folder: %3 Database "%10". CN min: %4, CN max: %5 Message ...
  61. An outgoing replication message was issued. Type: %1 Message ID: %2 Folder: %3 Database "%10". CNSET: %4 CNSET (FAI): %5 ...
  62. An Outlook Web App virtual directory with Name {0}, WebSite {1}, VirtualDirectory {2}, ApplicationRoot {3}, and Identity ...
  63. An unexpected error has occurred in the application. An event has been logged for the system administrator. If you continue ...
  64. An unexpected error occurred while attempting to open the IIS metabase root with write access. The error returned was: {0} ...
  65. An unexpected error occurred while closing a handle after modifying the forms-based authentication setting for path {0}. ...
  66. An unexpected error occurred while modifying the forms authentication settings for path {0}. The error returned was {1}. ...
  67. An unexpected error occurred while opening the metabase key for modifying forms-based authentication settings for path {0}. ...
  68. An unexpected error occurred while querying the metabase path {0} for the forms authentication property. The error returned ...
  69. An unexpected error occurred while searching for virtual directories enabled for forms authentication (metabase property ...
  70. An unexpected error occurred while searching for virtual directories in the {0} application pool. The error returned was ...
  71. An unexpected error occurred while trying to close the IIS metabase root. The error was: {0} Please verify that forms-based ...
  72. An unexpected error occurred while trying to contact the Information Store service. The server and the database may be down. ...
  73. An unexpected error occurred while trying to delete the forms-based authentication property (metabase property ID 45054) ...
  74. An unexpected error occurred while trying to query an IIS path for its forms-based authentication setting (metabase property ...
  75. An unexpected exception occurred while pinging RpcProxy. The most common reason for this occurring is that the IIS DefaultAppPool ...