System Center Operations Manager 2012

  1. Data writer successfully performed data maintenance operations. One or more workflows were affected by this. Workflow name: ...
  2. Database files with the same name already exist. Please remove the conflicting files listed below or select another location.{1}{0} ...
  3. Database queue length has dropped below warning thresholds. New Forwarder connections will now be permitted. Current queue ...
  4. Database queue threshold exceeded. New client connections will not be allowed until queue length decreases below the threshold, ...
  5. Database queue threshold exceeded. One or more clients might be disconnected. New connections will not be allowed until queue ...
  6. Database: 2]. MergeDatabase: Unable to write errors to Error table. Could be due to a non-nullable column in a predefined ...
  7. Datasource ModuleType {0} is declared as a composite module type and needs to be composed from at least one DataSourceModule ...
  8. Datatype mismatch in ModuleType composition. InputType {0} of referenced leaf ConditionModule (Type={1},ID={2}) does not ...
  9. Datatype mismatch in ModuleType composition. OutputType {0} of referenced module (Type={1}, ID={2}) does not match expected ...
  10. Datatype mismatch in ModuleType composition. OutputType {0} of referenced module {1} does not match expected data type {2} ...
  11. Datatype mismatch in ModuleType composition. Referenced leaf ConditionModule (Type={1},ID={2}) has more input types than ...
  12. Datatype mismatch in ModuleType composition. Referenced leaf WriteAction Module (Type={1},ID={2}) does not match up with ...
  13. Datatype mismatch in ModuleType composition. Referenced WriteAction Module (Type={0}, ID={1}) has an output datatype ({2}) ...
  14. DataType mismatch. Condition module type {1} outputs {2} data which is not compatible with the input datatype {3} of ProbeActionModule ...
  15. DataType mismatch. Condition module type {1} outputs {2} data which is not compatible with the input datatype {3} of WriteActionModule ...
  16. DB Update Interval received by LearningModule is zero. Module is being unloaded. One or more workflows were affected by this. ...
  17. Default assembly cannot be found. Reason per assemblies: %1 Monitoring will not start. Please be sure that the Microsoft ...
  18. Deleting a Management Pack might affect the scoping of some user roles. Are you sure you want to delete {0} version {1}? ...
  19. Deleting this aggregate monitor will also delete any related child monitors. Are you sure you want to delete this aggregate ...
  20. Dependency monitor depends on a monitor of a related type. Select a relationship type and one of the monitors of the related ...
  21. Dependency rollup monitor can not be created because the target does not have relationships where the target is the source ...
  22. depends on management packs that are not imported but are available in the online catalog. Click Resolve to add the dependent ...
  23. Deployment operation validation failed. Component alrady installed. Operation: '%s'; Component type: '%s'; Component id: ...
  24. Deployment operation validation failed. Component does not exist. Operation: '%s'; Component type: '%s'; Component id: '%s'; ...
  25. Deployment operation validation failed. Component does not support upgrade from previous version. Operation: '%s'; Component ...
  26. Deployment operation validation failed. Configuration xml provided for operation that does not require configuration. Operation: ...
  27. Deployment operation validation failed. Dataset script target dataset type does not match the target specified. Operation: ...
  28. Deployment operation validation failed. Management pack version does not exist. Operation: '%s'; Component type: '%s'; Component ...
  29. Deployment operation validation failed. Target database or dataset does not exist. Operation: '%s'; Component type: '%s'; ...
  30. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentHasServic ...
  31. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentHasServiceComponentItem ...
  32. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentHasServiceComponentItem.Item ...
  33. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentItem.Icon ...
  34. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentReference ...
  35. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentReference ...
  36. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceComponentReferencesServiceComponent ...
  37. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceHasServiceComponent ...
  38. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceHasServiceComponent.ContainsComponent ...
  39. Description for Microsoft.EnterpriseManagement.Internal.UI.Authoring.ServiceDesignerEditor.DSL.ServiceHasServiceComponent.Service ...
  40. Deselect servers that you don't want agents to failover to (if for example, one of servers is a critical management server ...
  41. Diagnostics data of the specified role which are older than %13 GMT have been deleted from the Windows Azure storage table. ...
  42. did not pass the security verification. The management pack cannot be downloaded and the temporary file has been deleted. ...
  43. Disable a monitor: I want to disable monitor for all Windows Computers. Override a diagnostic: I need to override this diagnostic ...
  44. Discovering an unknown system using SSH is a potentially dangerous operation. The discovery process will send the user name ...
  45. Discovery can continue, but Operations Manager will not be able to monitor this computer until the DNS is updated to match ...
  46. Discovery data couldn't be inserted to the database. This could have happened because of one of the following reasons: - ...
  47. Discovery data generated by discovery source id '%1' has invalid topology relationships. The health service id %2 should ...
  48. Discovery data generated by discovery source id '%1' has invalid topology relationships. This can be due to the following ...
  49. Discovery data has been received from a rule targeted at a non-existent monitoring object id. MonitoringObjectId: {0} RuleId: ...
  50. Discovery data has been submitted with both disabled and enabled scopes in a single response by rule %5. This is not supported ...
  51. Discovery data has been submitted with both disabled and enabled scopes in a single response by task %5. This is not supported ...
  52. Discovery data has been submitted with both disabled and enabled scopes in a single response invoked by %5. This is not supported ...
  53. Discovery failed to initialize because in a single day window, the start hour is greater than the end hour. Discovery name: ...
  54. Discovery failed to initialize because some "hour in the day" in the schedule could not be parsed on the HH:mm format. Hour ...
  55. Discovery failed to initialize because some schedule window has a negative start. Discovery name: %2 Instance name: %3 Management ...
  56. Discovery failed to initialize because some schedule window has a non-positive length of time. Discovery name: %2 Instance ...
  57. Discovery failed to initialize because some schedule window has no day of the week set. Discovery name: %2 Instance name: ...
  58. Discovery failed to initialize because some schedule windows overlap with each other. Discovery name: %2 Instance name: %3 ...
  59. Discovery failed to initialize because some value in its schedule configuration is too long. Value: %1 Discovery name: %3 ...
  60. Discovery failed to initialize because the exclude date interval in the schedule failed to parse using the MM/dd format. ...
  61. Discovery failed to initialize because the first schedule window is after the full interval. Discovery name: %2 Instance ...
  62. Discovery failed to initialize because the last and first schedule windows overlap. Discovery name: %2 Instance name: %3 ...
  63. Discovery failed to initialize because the maximum number of schedule windows has been reached. Number of windows: %1 Maximum ...
  64. Discovery failed to initialize because the number of excluded dates in the schedule is greater than the maximum allowed. ...
  65. Discovery failed to initialize because the recurring interval can not be greater than the full re-sync interval for the schedule. ...
  66. Discovery failed to initialize because the specified schedule contains an invalid multiple days interval. The start and end ...
  67. Discovery failed to initialize because the specified schedule interval is greater than the maximum allowed. Interval (seconds): ...
  68. Discovery failed to initialize because the specified schedule interval number is out of range. Interval: %1 Minimum Unit ...
  69. Discovery failed to initialize because the specified schedule is not recognized as a weekly or simple recurring one. Discovery ...
  70. Discovery failed to initialize because the specified schedule spread initialization interval is greater than the maximum ...
  71. Discovery failed to initialize because the specified schedule spread initialization interval number is out of range. Interval: ...
  72. Discovery failed to initialize because there is no schedule window specified. Discovery name: %2 Instance name: %3 Management ...
  73. Discovery failed to initialize due to invalid schedule configuration. Invalid Configuration: %1 Discovery name: %3 Instance ...
  74. Discovery failed to initialize due to invalid schedule configuration. Rejected Item: %1 Rejected Value: %2 Discovery name: ...
  75. Discovery manager has detected an unsupported topology. On demand discovery is being disabled and the health service will ...