System Center Operations Manager 2007

  1. Invalid relationship source specified in the discovery data item. RelationshipSourceBaseManagedEntityId: {0} RuleId: {1} ...
  2. Invalid relationship target role type id specified in the discovery data item. RelationshipTargetRoleTypeId: {0} RuleId: ...
  3. Invalid relationship target role type id specified in the discovery data item. RelationshipTargetRoleTypeId: {0} RuleId: ...
  4. Invalid relationship target specified in the discovery data item. RelationshipTargetBaseManagedEntityId: {0} RuleId: {1} ...
  5. Invalid relationship target specified in the discovery data item. RelationshipTargetBaseManagedEntityId: {0} RuleId: {1} ...
  6. Invalid rule composition. {0} dataSource modules specified for this rule, but the ConditionDetection module {1}, {2} expects ...
  7. Invalid separator. Separator must be either a single character, or a single character surrounded by double quotes Separator ...
  8. Invalid separator. Separator must be either a single character, or a single character surrounded by double quotes Separator ...
  9. Invalid Target - RelationshipType combination. This dependency monitor has a Target {0} which does not inherit from the source ...
  10. Invalid value for alert priority used with configuration of the rule. It was outside of allowed range and had to be adjusted ...
  11. Invalid value for alert priority used with configuration of the rule. It was outside of allowed range and had to be adjusted ...
  12. Invalid value for alert severity used with configuration of the rule. It was outside of allowed range and had to be adjusted ...
  13. Invalid value for alert severity used with configuration of the rule. It was outside of allowed range and had to be adjusted ...
  14. Invalid value for health state was used while overriding monitor property 'DefaultState'. It was outside of allowed range ...
  15. Invalid value specified {0} for the Length of this Property. For a 'decimal' datatype, the value of Length must be between ...
  16. Invalid Workflow Foundation 4.0 module configuration received. Error Details: %6 WF Workflow Name: %5 One or more workflows ...
  17. Invalid XPathSelect specified. This XPath query {0} returned an Xml Fragment. Overrides are only allowed for simple types. ...
  18. Invalid XPathSelector {0} specified. Multiple queries have been specified in a single XPathSelector node. Please specify ...
  19. ISNetAPI.dll is not loaded or there was an error loading the dll. This dll needs to be loaded for this operation. Verify ...
  20. It is recommended that the operational database and data warehouse, if present, be backed up in the case of a potential upgrade ...
  21. Items that match the search criteria are displayed in black text. Items displayed in grey do not match the search criteria ...
  22. Knowledge authoring in Microsoft Operations Manager 2007 requires Office Word 2003 and the sub component .NET Programmability ...
  23. Knowledge authoring in Microsoft Operations Manager 2007 requires Office Word 2003 and the sub component .NET Programmability ...
  24. Large array returned by WMI object. This may indicate an misconfigured module Array size = %5 One or more workflows were ...
  25. Large array returned by WMI object. This may indicate an misconfigured module Array size = %5 One or more workflows were ...
  26. Length attribute can only be specified for 'string' and 'decimal' datatypes. Value {0} cannot be specified for the '{1}' ...
  27. Link to the dashboard you want to display. Copy the URL from your web browser address bar when viewing the dashboard in the ...
  28. List Validation Failure: Item {0} already exists in the list. Item names must be unique. Use a name that doesn't already ...
  29. ListenUploadWA module could not perform the Get Operation. Workflow name: %2 Instance name: %3 Instance ID: %4 Management ...
  30. ListenUploadWA module could not perform the Get Operation. Workflow name: %2 Instance name: %3 Instance ID: %4 Management ...
  31. ListenUploadWA module could not perform the Post Operation. Workflow name: %2 Instance name: %3 Instance ID: %4 Management ...
  32. ListenUploadWA module could not perform the Post Operation. Workflow name: %2 Instance name: %3 Instance ID: %4 Management ...
  33. ListenUploadWA module could not perform the Put Operation. Workflow name: %2 Instance name: %3 Instance ID: %4 Management ...
  34. ListenUploadWA module could not perform the Put Operation. Workflow name: %2 Instance name: %3 Instance ID: %4 Management ...
  35. ListenUploadWA module received on port %5, %6 # of posts and %7 # of puts in last 24 hours. Workflow name: %2 Instance name: ...
  36. ListenUploadWA module received on port %5, %6 # of posts and %7 # of puts in last 24 hours. Workflow name: %2 Instance name: ...
  37. Loading managed module type in assembly "%5" with type name "%6" failed with error "%7". This may be because the type or ...
  38. Loading managed module type in assembly "%5" with type name "%6" failed with error code "%7" in rule "%2" running for instance ...
  39. Local health service is not healthy. Alert flow is stalled with pending acknowledgement. Management Group: %2 Management ...
  40. Local health service is not healthy. Alert flow is stalled with pending acknowledgement. Management Group: %2 Management ...
  41. Local health service is not healthy. Entity state change flow is stalled with pending acknowledgement. Management Group: ...
  42. Local health service is not healthy. Entity state change flow is stalled with pending acknowledgement. Management Group: ...
  43. Local health service is not healthy. Monitor state change flow is stalled with pending acknowledgement. Management Group: ...
  44. Local health service is not healthy. Monitor state change flow is stalled with pending acknowledgement. Management Group: ...
  45. Log file appears to have disappeared Directory = %5 Log File = %6 One or more workflows were affected by this. Workflow name: ...
  46. Log file appears to have disappeared Directory = %5 Log File = %6 One or more workflows were affected by this. Workflow name: ...
  47. Log file directory accessed successfully Directory = %5 One or more workflows were affected by this. Workflow name: %2 Instance ...
  48. Log file directory accessed successfully Directory = %5 One or more workflows were affected by this. Workflow name: %2 Instance ...
  49. Log File directory no longer exists Directory = %5 One or more workflows were affected by this. Workflow name: %2 Instance ...
  50. Log File directory no longer exists Directory = %5 One or more workflows were affected by this. Workflow name: %2 Instance ...
  51. Log file directory opened successfully Directory = %5 One or more workflows were affected by this. Workflow name: %2 Instance ...
  52. Log file directory opened successfully Directory = %5 One or more workflows were affected by this. Workflow name: %2 Instance ...
  53. Login specified as Management Group Writer Login is already specified as writer login for another pending Management Group ...
  54. Make sure you configure the Management Server to allow new manual agent installations. You can change this setting in the ...
  55. Make sure you configure the Management Server to allow new manual agent installations. You can change this setting in the ...
  56. Management group with id '%s' is not a member of this Data Warehouse or you do not have permissions to perform actions for ...
  57. Management groups that have been added using Active Directory Domain Services (AD DS) integration cannot be edited manually. ...
  58. Management groups that have been added using Active Directory Domain Services (AD DS) integration cannot be removed manually. ...
  59. Management Pack ID is either empty, invalid or not unique. Valid ID starts with a letter and may contain only letters and ...
  60. Management pack reference is incorrect. Reference to MP ID: {0}, KeyToken: {1} in file: {2} does not match what is actually ...
  61. Management Pack with id:"%1", version:"%2" has been changed locally. Management Pack cache file will be deleted and re-requested ...
  62. Management Pack with id:"%1", version:"%2" has been changed locally. Management Pack cache file will be deleted and re-requested ...
  63. Management server action account does not have permissions to system temp directory. Problem Management functionality could ...
  64. ManagementPack Version {0} is not upgrade compatible with older version {1}]. Compatibility check failed with {2} errors: ...
  65. ManagementPack Version {0} is not upgrade compatible with older version {1}]. Compatibility check failed with {2} errors: ...
  66. MemberModule ID={0}, TypeID={1} has stateful flag set to 'true'. ProbeActionModuleType cannot be composed of a stateful ConditionDetection ...
  67. MemberModule Reference ID={0}, TypeID={1} is listed as a ConditionDetectionModule reference. It is actually of type {2}] ...
  68. Members of this security role will not automatically have permissions to new views added to this folder. If new views are ...
  69. Members of this security role will not automatically have permissions to new views added to this folder. If new views are ...
  70. Members of this user role can see approved views and dashboards. Limiting access to views and dashboards does not limit access ...
  71. Members of this user role can see approved views. Limiting access to views does not limit access to the underlying data. ...
  72. Membership to user roles is managed by Operations Manager Administrators and determines the level of access users have on ...
  73. Method name is improperly formatted. The full method should be entered, for example: System.Data.SqlClient.SqlCommand.ExecuteReader ...
  74. Microsoft Core XML Services (MSXML) 6.0 is required to install this application. Please see the release notes for more information. ...
  75. Microsoft Operations Manager was unable to use it's event log '%1'. MOM is now dropping events into the Application event ...