System Center Operations Manager 2007

  1. The Event Policy for the process started at %5 has detected errors in the output. The '%13' policy expression: %14 matched ...
  2. The Event Policy for the process started at %5 has detected errors in the output. The '%13' policy expression: %14 matched ...
  3. The EventLog service reported that the %5 event log on computer '%7' is corrupt. The Windows Event Log Provider will attempt ...
  4. The EventLog service reported that the %5 event log on computer '%7' is corrupt. The Windows Event Log Provider will attempt ...
  5. The EventLog service reported that the %5 event log on computer '%8' is corrupt. The Windows Event Log Provider will attempt ...
  6. The EventLog service reported that the %5 event log on computer '%8' is corrupt. The Windows Event Log Provider will attempt ...
  7. The favorite report cannot be generated for the current application group. Please select another group and reset the favorite ...
  8. The file '[2]' cannot be installed because the file cannot be found in cabinet file '[3]'. This could indicate a network ...
  9. The file 2 cannot be installed because the file cannot be found in cabinet file 3]. This could indicate a network error, ...
  10. The file 2][3 is being held in use{ by the following process: Name: 4], ID: 5], Window Title: 6]}. Close that application ...
  11. The file name specified is invalid. The file name must be the ID of the management pack followed by the file type (.xml). ...
  12. The file you are importing contains one or more duplicate entries. If you continue, duplicate file entries will be ignored. ...
  13. The flag 'Enforced' cannot be set to 'true' for an Override in a sealed Management Pack. This value is available only for ...
  14. The following accounts need to be distributed to the health service '{0}' and the members of the management pool '{1}' in ...
  15. The following address(es) specified as notification recipient(s) are invalid:%r Protocol: %5%r Recipient type: %6%r Address(es): ...
  16. The following address(es) specified as notification recipient(s) are invalid:%r Protocol: %5%r Recipient type: %6%r Address(es): ...
  17. The following applications are using files that need to be updated by this setup. Close these applications and click Retry ...
  18. The following device(s) are the starting point for a network discovery rule and cannot be deleted. Before you can delete ...
  19. The following error occurred connecting to the script data source for management group '%5', target computer '%6', and data ...
  20. The following error occurred connecting to the script data source for management group '%5', target computer '%6', and data ...
  21. The following error occurred submitting data to the script data source for management group '%5', target computer '%6', and ...
  22. The following error occurred submitting data to the script data source for management group '%5', target computer '%6', and ...
  23. The following hardware and software are required to continue. After you resolve the prerequisite problems, click Verify Prerequisites ...
  24. The following is a summary of your configuration for this Exchange 2007 Intra-Organization Mail flow monitoring template. ...
  25. The following problems may affect performance or storage, but Setup can continue. After you resolve the prerequisite problems, ...
  26. The following rules in the XX Management Pack present security risks. To avoid the risk to security, remove the Management ...
  27. The following rules in the {0} Management Pack present security risks. To avoid the risk to security, remove the Management ...
  28. The following Run As Profiles use this Run As Account and the associated target computers that the account is allowed to ...
  29. The Framework version "%1" is unsupported by the current version of the Intercept Agent. Please contact your system administrator. ...
  30. The Framework version "%1" is unsupported by the current version of the Intercept Agent. Please contact your system administrator. ...
  31. The Gateway uses the Action Account to gather operational data from providers, to run responses, and to perform actions such ...
  32. The grooming process removes unnecessary data from the Operations Manager database in order to maintain performance. For ...
  33. The grooming process removes unnecessary data from the Operations Manager database in order to maintain performance. For ...
  34. The group deletion failed because this group is included in the subgroup list of one or more other groups. Remove this group ...
  35. The health of this Component is determined by the health of its members. This monitor rolls up health from each of the members ...
  36. The health of this service is determined by the health of its components. This monitor rolls up health from a particular ...
  37. The health service %1 running on host %2 and serving management group %3 with id %4 is not available because service has ...
  38. The health service %1 running on host %2 and serving management group %3 with id %4 is not available because service has ...
  39. The health service %1 running on host %2 and serving management group %3 with id %4 is not available because the OpsMgr Connector ...
  40. The health service %1 running on host %2 and serving management group %3 with id %4 is not available because the OpsMgr Connector ...
  41. The health service %1 running on host %2 and serving management group %3 with id %4 is not available because the OpsMgr Connector ...
  42. The health service %1 running on host %2 and serving management group %3 with id %4 is not available because the OpsMgr Connector ...
  43. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Action account is invalid. ...
  44. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Action account is invalid. ...
  45. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Alert flow is stalled ...
  46. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Alert flow is stalled ...
  47. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Entity state change flow ...
  48. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Entity state change flow ...
  49. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Health Service failed ...
  50. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Health Service failed ...
  51. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Monitor state change ...
  52. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Monitor state change ...
  53. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Some system rules failed ...
  54. The health service %1 running on host %2 and serving management group %3 with id %4 is not healthy. Some system rules failed ...
  55. The health service %1 running on host %2 and serving management group %3 with id %4 is not reachable due to server being ...
  56. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, action ...
  57. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, action ...
  58. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, alert ...
  59. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, alert ...
  60. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, entity ...
  61. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, entity ...
  62. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, health ...
  63. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, health ...
  64. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, monitor ...
  65. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, monitor ...
  66. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, service ...
  67. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, service ...
  68. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, system ...
  69. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, system ...
  70. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, the OpsMgr ...
  71. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, the OpsMgr ...
  72. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, the OpsMgr ...
  73. The health service %1 running on host %2 and serving management group %3 with id %4 is still not healthy. However, the OpsMgr ...
  74. The health service blocked access to the non-windows credential with ID %2 because it is not authorized on management group ...
  75. The health service blocked access to the non-windows credential with ID %2 because it is not authorized on management group ...