Exchange Server 2010

  1. Current transaction log file generation for storage group '{3}' on server {2} is nearing maximum value. Action needs to be ...
  2. Current transaction log generation for storage group '{3}' on server {2} is nearing its maximum allowed value. Action needs ...
  3. Current transaction log generation for storage group '{3}' on server {2} is nearing maximum value. Action must be taken to ...
  4. Current transaction log generation for storage group '{3}' on server {2} is nearing maximum value. Action needs to be taken ...
  5. Current transaction log generation is nearing maximum value. Estimate %DaysLeftForLogGen% days left before reaching the maximum ...
  6. Current Unauthenticated Pilot Number Calls is the number of voice calls to the pilot number that have not yet been authenticated. ...
  7. Current Unique Users is the number of unique users currently signed in to Outlook Web App. This value monitors the number ...
  8. Current Unique Users Light is the number of unique users that are currently signed in to Outlook Web App. This value monitors ...
  9. Current Unique Users Premium is the number of unique users that are currently signed in to Outlook Web App. This value monitors ...
  10. Current User Count is the number of users who are currently signed in to Outlook Web App. This value monitors the number ...
  11. Current User Count Light is the number of users currently signed in to Outlook Web App. This value monitors the number of ...
  12. Current User Count Premium is the number of users that are currently signed in to Outlook Web App. This value monitors the ...
  13. Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3" and received ...
  14. Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3" and received ...
  15. Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3" but the target ...
  16. Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3" but the target ...
  17. Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed ...
  18. Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed ...
  19. Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed ...
  20. Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed ...
  21. Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed ...
  22. Current User: '%1' Client Access server "%2" tried to proxy Web management traffic to Client Access server "%3". This failed ...
  23. Current User: '%1' Client Access server "%2", running Microsoft Exchange version "%3", is proxying Web management traffic ...
  24. Current User: '%1' Client Access server "%2", running Microsoft Exchange version "%3", is proxying Web management traffic ...
  25. Current User: '%1' Exchange Control Panel detected an invalid canary from request for URL '%2'. Canary in cookie: '%3' mismatch ...
  26. Current User: '%1' Exchange Control Panel detected an invalid canary from request for URL '%2'. Canary in cookie: '%3' mismatch ...
  27. Current User: '%1' Microsoft Exchange Control Panel started serving uploading request. Upload Handler: '%2' Parameter: '%3 ...
  28. Current User: '%1' Microsoft Exchange Control Panel started serving uploading request. Upload Handler: '%2' Parameter: '%3 ...
  29. Currently supported authentication types are 'Basic' and 'Nego2' For Basic authentication, user can supply credential or ...
  30. Currently supported authentication types are 'Basic' and 'Nego2' For Basic authentication, user can supply credential or ...
  31. Custom Prompt Download Failures % Base is the base counter for calculating the percentage of failures to download custom ...
  32. Custom Prompt Download Failures % is the percentage of failures to download custom prompts for an auto attendant or a dial ...
  33. Customer Experience Improvement Program for the organization is set to False by your Organization Admin. You can't enable ...
  34. Data inconsistency detected in table %4 of database %5 (%6,%7). For more information, click http://www.microsoft.com/contentredirect.asp. ...
  35. Data inconsistency detected in table %4 of database %5 (%6,%7). For more information, click http://www.microsoft.com/contentredirect.asp. ...
  36. Database "%1" has been subject to a lossy failover. The database may be patched if the Information Store detects it is necessary. ...
  37. Database "%1" has been subject to a lossy failover. The database may be patched if the Information Store detects it is necessary. ...
  38. Database "{0}" has circular logging enabled. It is not possible to add or remove database copies while circular logging is ...
  39. Database "{0}" has multiple copies on other servers. To remove an active database you must first remove all copies from other ...
  40. Database "{0}" has only one copy hosted on server "{1}". The Move-ActiveMailboxDatabase cmdlet can only work with databases ...
  41. Database "{0}" is a public folder database and cannot be managed by this command. Use the public folder database cmdlets ...
  42. Database %1 cannot be incrementally backed up. You must first perform a full backup before performing an incremental backup. ...
  43. Database %1 cannot be incrementally backed up. You must first perform a full backup before performing an incremental backup. ...
  44. Database %1 has been assigned a new replication ID (possibly because it was restored from an older copy). The old replication ...
  45. Database %1 has been assigned a new replication ID (possibly because it was restored from an older copy). The old replication ...
  46. Database %1 has lost %2 committed log files (%3-%4), however lost log resilience has allowed ESE to recover this database ...
  47. Database %1 has lost %2 committed log files (%3-%4), however lost log resilience has allowed ESE to recover this database ...
  48. Database %1 requires log file %2 created at %3 in order to recover successfully. Recovery found the log file created at %4. ...
  49. Database %1 requires log file %2 created at %3 in order to recover successfully. Recovery found the log file created at %4. ...
  50. Database %1 requires log files %2-%3 (%5 - %6) in order to recover successfully. Recovery could only locate log files up ...
  51. Database %1 requires log files %2-%3 (%5 - %6) in order to recover successfully. Recovery could only locate log files up ...
  52. Database %1 requires log files %2-%3 in order to recover all committed data. Recovery could only locate up to log file %4 ...
  53. Database %1 requires log files %2-%3 in order to recover all committed data. Recovery could only locate up to log file %4 ...
  54. Database %1 requires log files %2-%3 in order to recover successfully. Recovery could only locate log files starting at %4. ...
  55. Database %1 requires log files %2-%3 in order to recover successfully. Recovery could only locate log files starting at %4. ...
  56. Database %1: Page %2 failed verification due to a flush-order dependency mismatch. This page should have flushed before page ...
  57. Database %1: Page %2 failed verification due to a flush-order dependency mismatch. This page should have flushed before page ...
  58. Database %1: Page %2 failed verification due to a timestamp mismatch. The expected timestamp was %3, but the actual timestamp ...
  59. Database %1: Page %2 failed verification due to a timestamp mismatch. The expected timestamp was %3, but the actual timestamp ...
  60. Database %4 cannot be incrementally backed-up. You must first perform a full backup before performing an incremental backup. ...
  61. Database %4 cannot be incrementally backed-up. You must first perform a full backup before performing an incremental backup. ...
  62. Database %4 has lost %5 committed log files (%6-%7). However, lost log resilience has allowed ESE to recover this database ...
  63. Database %4 has lost %5 committed log files (%6-%7). However, lost log resilience has allowed ESE to recover this database ...
  64. Database %4 is partially attached. Attachment stage: %5. Error: %6. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  65. Database %4 is partially attached. Attachment stage: %5. Error: %6. For more information, click http://www.microsoft.com/contentredirect.asp. ...
  66. Database %4 requires log files %5-%6 in order to recover all committed data. Recovery could only locate up to log file: %7, ...
  67. Database %4 requires log files %5-%6 in order to recover all committed data. Recovery could only locate up to log file: %7, ...
  68. Database %4 requires logfile %5 created at %6 in order to recover successfully. Recovery found the logfile created at %7. ...
  69. Database %4 requires logfile %5 created at %6 in order to recover successfully. Recovery found the logfile created at %7. ...
  70. Database %4 requires logfiles %5-%6 (%8 - %9) in order to recover successfully. Recovery could only locate logfiles up to ...
  71. Database %4 requires logfiles %5-%6 (%8 - %9) in order to recover successfully. Recovery could only locate logfiles up to ...
  72. Database %4 requires logfiles %5-%6 in order to recover successfully. Recovery could only locate logfiles starting at %7. ...
  73. Database %4 requires logfiles %5-%6 in order to recover successfully. Recovery could only locate logfiles starting at %7. ...
  74. Database %4 was partially detached. Error %5 encountered updating database headers. For more information, click http://w ...
  75. Database %4 was partially detached. Error %5 encountered updating database headers. For more information, click http://w ...