System Center Operations Manager 2007

  1. Dependency monitor depends on a monitor of a related type. Select a relationship type and one of the monitors of the related ...
  2. Dependency rollup monitor can not be created because the target does not have relationships where the target is the source ...
  3. depends on management packs that are not imported but are available in the online catalog. Click Resolve to add the dependent ...
  4. Deployment operation validation failed. Component alrady installed. Operation: '%s'; Component type: '%s'; Component id: ...
  5. Deployment operation validation failed. Component does not exist. Operation: '%s'; Component type: '%s'; Component id: '%s'; ...
  6. Deployment operation validation failed. Component does not support upgrade from previous version. Operation: '%s'; Component ...
  7. Deployment operation validation failed. Configuration xml provided for operation that does not require configuration. Operation: ...
  8. Deployment operation validation failed. Dataset script target dataset type does not match the target specified. Operation: ...
  9. Deployment operation validation failed. Management pack version does not exist. Operation: '%s'; Component type: '%s'; Component ...
  10. Deployment operation validation failed. Target database or dataset does not exist. Operation: '%s'; Component type: '%s'; ...
  11. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentHasServic ...
  12. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentHasServiceComponentItem ...
  13. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentHasServiceComponentItem.Item ...
  14. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentReference ...
  15. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentReference ...
  16. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentReferencesServiceComponent ...
  17. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceHasServiceComponent ...
  18. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceHasServiceComponent.ContainsComponent ...
  19. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceHasServiceComponent.Service ...
  20. Deselect servers that you don't want agents to failover to (if for example, one of servers is a critical management server ...
  21. Deserializing the given object into the given ManagementGroup failed because one of the types referenced does not exist in ...
  22. Diagnostics data of the specified role which are older than %13 GMT have been deleted from the Windows Azure storage table. ...
  23. did not pass the security verification. The management pack cannot be downloaded and the temporary file has been deleted. ...
  24. Disable a monitor: I want to disable monitor for all Windows Computers. Override a diagnostic: I need to override this diagnostic ...
  25. Disable a monitor: I want to disable monitor for all Windows Computers. Override a diagnostic: I need to override this diagnostic ...
  26. Discovery data couldn't be inserted to the database. This could have happened because of one of the following reasons: - ...
  27. Discovery data couldn't be inserted to the database. This could have happened because of one of the following reasons: - ...
  28. Discovery data generated by discovery source id '%1' has invalid topology relationships. The health service id %2 should ...
  29. Discovery data generated by discovery source id '%1' has invalid topology relationships. The health service id %2 should ...
  30. Discovery data generated by discovery source id '%1' has invalid topology relationships. This can be due to the following ...
  31. Discovery data generated by discovery source id '%1' has invalid topology relationships. This can be due to the following ...
  32. Discovery data has been received from a rule targeted at a non-existent monitoring object id. MonitoringObjectId: {0} RuleId: ...
  33. Discovery data has been received from a rule targeted at a non-existent monitoring object id. MonitoringObjectId: {0} RuleId: ...
  34. Discovery data has been submitted with both disabled and enabled scopes in a single response by rule %5. This is not supported ...
  35. Discovery data has been submitted with both disabled and enabled scopes in a single response by rule %5. This is not supported ...
  36. Discovery data has been submitted with both disabled and enabled scopes in a single response by task %5. This is not supported ...
  37. Discovery data has been submitted with both disabled and enabled scopes in a single response by task %5. This is not supported ...
  38. Discovery data has been submitted with both disabled and enabled scopes in a single response invoked by %5. This is not supported ...
  39. Discovery data has been submitted with both disabled and enabled scopes in a single response invoked by %5. This is not supported ...
  40. Discovery failed to initialize because in a single day window, the start hour is greater than the end hour. Discovery name: ...
  41. Discovery failed to initialize because some "hour in the day" in the schedule could not be parsed on the HH:mm format. Hour ...
  42. Discovery failed to initialize because some schedule window has a negative start. Discovery name: %2 Instance name: %3 Management ...
  43. Discovery failed to initialize because some schedule window has a non-positive length of time. Discovery name: %2 Instance ...
  44. Discovery failed to initialize because some schedule window has no day of the week set. Discovery name: %2 Instance name: ...
  45. Discovery failed to initialize because some schedule windows overlap with each other. Discovery name: %2 Instance name: %3 ...
  46. Discovery failed to initialize because some value in its schedule configuration is too long. Value: %1 Discovery name: %3 ...
  47. Discovery failed to initialize because the exclude date interval in the schedule failed to parse using the MM/dd format. ...
  48. Discovery failed to initialize because the first schedule window is after the full interval. Discovery name: %2 Instance ...
  49. Discovery failed to initialize because the last and first schedule windows overlap. Discovery name: %2 Instance name: %3 ...
  50. Discovery failed to initialize because the maximum number of schedule windows has been reached. Number of windows: %1 Maximum ...
  51. Discovery failed to initialize because the number of excluded dates in the schedule is greater than the maximum allowed. ...
  52. Discovery failed to initialize because the recurring interval can not be greater than the full re-sync interval for the schedule. ...
  53. Discovery failed to initialize because the specified schedule contains an invalid multiple days interval. The start and end ...
  54. Discovery failed to initialize because the specified schedule interval is greater than the maximum allowed. Interval (seconds): ...
  55. Discovery failed to initialize because the specified schedule interval number is out of range. Interval: %1 Minimum Unit ...
  56. Discovery failed to initialize because the specified schedule is not recognized as a weekly or simple recurring one. Discovery ...
  57. Discovery failed to initialize because the specified schedule spread initialization interval is greater than the maximum ...
  58. Discovery failed to initialize because the specified schedule spread initialization interval number is out of range. Interval: ...
  59. Discovery failed to initialize because there is no schedule window specified. Discovery name: %2 Instance name: %3 Management ...
  60. Discovery failed to initialize due to invalid schedule configuration. Invalid Configuration: %1 Discovery name: %3 Instance ...
  61. Discovery failed to initialize due to invalid schedule configuration. Rejected Item: %1 Rejected Value: %2 Discovery name: ...
  62. Discovery manager has detected an unsupported topology. On demand discovery is being disabled and the health service will ...
  63. Discovery module failed connecting to local cluster and module will unload. Error: %5 Details: %6 Workflow name: %2 Instance ...
  64. Discovery module failed connecting to local cluster while cluster service is registered. Module will try reconnect after ...
  65. Discovery module succeeded connecting to local cluster. Workflow name: %2 Instance name: %3 Instance ID: %4 Management group: ...
  66. Discovery task has been canceled unexpectedly. Discovery name: %2 Instance name: %3 Management group name: %1
  67. Discovery task has been suspended unexpectedly. Discovery name: %2 Instance name: %3 Management group name: %1
  68. Displays the interval during {0}which the image loaded and {0}the elapsed time in ms between {0}TTFB and the load completion. ...
  69. Distributed application exported successfully. This file needs a valid management pack ID and matching file name before it ...
  70. Distributed application exported successfully. This file needs a valid management pack ID and matching file name before it ...
  71. Domain {0} has a functional level of {1}. For AD based assignment the domain functional level should be Windows2000 or Windows2003 ...
  72. Due to an unusually high system load, the threshold for functions processed per second has been exceeded. This may have resulted ...
  73. Due to an unusually high system load, the threshold for functions processed per second has been exceeded. This may have resulted ...
  74. Duplicate Error: More than one language pack item has been specified for the same MP Object: ElementID={1}, SubElementID= ...
  75. Duplicate MonitorTypeStateID {0} specified for OnDemand Detection. This MonitorTypeStateID already has another OnDemand Detection ...