System Center Operations Manager 2012 R2

  1. ISNetAPI.dll is not loaded or there was an error loading the dll. This dll needs to be loaded for this operation. Verify ...
  2. It is recommended that the operational database and data warehouse be backed up in the case of a potential upgrade failure. ...
  3. Items that match the search criteria are displayed in black text. Items displayed in grey do not match the search criteria ...
  4. Length attribute can only be specified for 'string' and 'decimal' datatypes. Value {0} cannot be specified for the '{1}' ...
  5. Link to the dashboard you want to display. Copy the URL from your web browser address bar when viewing the dashboard in the ...
  6. List Validation Failure: Item {0} already exists in the list. Item names must be unique. Use a name that doesn't already ...
  7. Login specified as Management Group Writer Login is already specified as writer login for another pending Management Group ...
  8. Management group with id '%s' is not a member of this Data Warehouse or you do not have permissions to perform actions for ...
  9. Management Pack ID is either empty, invalid or not unique. Valid ID starts with a letter and may contain only letters and ...
  10. Management pack reference is incorrect. Reference to MP ID: {0}, KeyToken: {1} in file: {2} does not match what is actually ...
  11. Management server action account does not have permissions to system temp directory. Problem Management functionality could ...
  12. ManagementPack Version {0} is not upgrade compatible with older version {1}]. Compatibility check failed with {2} errors: ...
  13. Managing Alert Rules enables you to determine which rules Operational Insights uses to perform checks and generate alerts. ...
  14. Managing Alert Rules enables you to determine which rules System Center Advisor uses to perform checks and generate alerts. ...
  15. Max Heap is the maximum amount of memory (in bytes) available to the Java virtual machine. Note: this may or may not be available. ...
  16. MemberModule ID={0}, TypeID={1} has stateful flag set to 'true'. ProbeActionModuleType cannot be composed of a stateful ConditionDetection ...
  17. MemberModule Reference ID={0}, TypeID={1} is listed as a ConditionDetectionModule reference. It is actually of type {2}] ...
  18. Members of this security role will not automatically have permissions to new views added to this folder. If new views are ...
  19. Members of this user role can see approved views and dashboards. Limiting access to views and dashboards does not limit access ...
  20. Membership to user roles is managed by Operations Manager Administrators and determines the level of access users have on ...
  21. Method name is improperly formatted. The full method should be entered, for example: System.Data.SqlClient.SqlCommand.ExecuteReader ...
  22. Microsoft Update offers security and important updates for Windows and other Microsoft Products including this product. Updates ...
  23. Microsoft Update offers security updates and other important updates for Windows and other Microsoft software, including ...
  24. MinLength attribute cannot be set on a non-key attribute. This attribute can only be set on Key properties (where Key='true'). ...
  25. Mismatched Stateful flag specified in composition. ConditionDetectionModuleType {0} has its Stateful flag set to 'false'. ...
  26. Mismatched Stateful flag specified in composition. ConditionDetectionModuleType {0} has its Stateful flag set to 'true'. ...
  27. Module reference Target={0} cannot be the same as the workflow Target={1}. Please remove the target specification against ...
  28. Module sequence error. Module ID={0}, Type={1} does not have a Target attribute. But the previous module (in the same workflow) ...
  29. Module target error. Only one unique Target location is currently supported by the MOM Runtime. Module ID={0}, TypeID={1}, ...
  30. ModuleType composition error. ConditionDetection Module ({0}) cannot be a leaf node on this Composite DataSourceModule. DataSourceModule ...
  31. ModuleType composition error. ProbeAction Module (Type={0}, ID={1}) cannot be a leaf node in this composition. The composition ...
  32. ModuleType composition error. writeaction Module ({0}) cannot be a leaf node on this Composite DataSourceModule. DataSourceModule ...
  33. MomADAdmin failed to create a container, please make sure momadadmin is running under domain administrator priviledge: {0} ...
  34. MomAdAdmin was unable to revert changes made under OperationsManager. Please manually delete {0}({1}) under OperationsManager ...
  35. Monitoring class in user role scope is not allowed for this user role. The profile associated with this user role does not ...
  36. Monitoring class property value already exists in the discovery data item. Check for duplicate property values. MonitoringClassPropertyName: ...
  37. Monitoring object is not allowed for this user role scope. The profile associated with this user role does not allow monitoring ...
  38. Monitoring task in user role scope is not allowed for this user role. The profile associated with this user role does not ...
  39. Monitoring tests will be performed against the target servers you select. Target servers must be agent-managed Exchange 2007 ...
  40. Monitoring view in user role scope is not allowed. The profile associated with this user role does not allow view to be specified. ...
  41. Monitors the health of the computer. The service may be configured to monitor the health of other computers in addition to ...
  42. More than one default LanguagePack found in this ManagementPack. Only one LanguagePack can be marked with IsDefault attribute ...
  43. More than one Operational State cannot be associated with same HealthState {0}]. Failed to verify Operational State {1}]. ...
  44. More than one Operational State cannot be associated with same MonitorTypeState {0}]. Failed to verify Operational State ...
  45. MPXmlLoader cannot load a management pack with version number= null through this interface method. Call the version independent ...
  46. MSXML 6.0 is required for installing this Component. MSXML 6.0 setup will be launched; please complete it before installing ...
  47. Multiple hosting relationships found for ClassType={0} - Relationship {1} is a hosting relationship defined on this Class ...
  48. Naming Conflict : Cannot import the {0} management pack. A management pack with the same ID {1} is currently in the import ...
  49. Net Framework 3.5 Service Pack 1 failed to install. Please install .Net Framework 3.5 Service Pack 1 and restart the install. ...
  50. Network devices, Agentless Windows computers and non-Windows computers are managed by a "proxy" Agent (on a Windows computer) ...
  51. New views cannot be opened for connected alerts. To open this view, open a new console window and connect to the other management ...
  52. No operational state has been mapped to a critical health state. Please select 'The monitor is in a warning health state' ...
  53. No operational state has been mapped to a warning health state. Please select 'The monitor is in a critical health state' ...
  54. Note: If additional management server(s) are added you will need to run this wizard if you want agent to failover to it. ...
  55. Note: If you do not see all of the computers you expect to see, you can obtain information on troubleshooting discovery issues ...
  56. Note: Monitoring will take effect when the agents receive the updated monitoring rules and discover the appropriate objects. ...
  57. Note: SQL authentication has to be enabled explicitely on the SQL Server instance. Also, the special SQL user 'sa' cannot ...
  58. Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides ...
  59. Note: The ID shown is the unique identifier for this report operator role. To control access to reports using this report ...
  60. Note: The Management Servers list contains only servers on which Client Monitoring is not enabled. To modify or disable Client ...
  61. Note: The MOMADAdmin.exe command line tool must be run by a domain administrator before running this wizard. This tool can ...
  62. Note: There are additional settings that can be used to suppress alerts. Click the "Advanced" button to configure more suppression ...
  63. Note: These changes will not take effect until you run repair on the agents. Follow the steps listed in the Operations Manager ...
  64. Note: This setting applies only when scanning Active Directory. You can configure how these objects will be discovered, on ...
  65. Note: When selecting the local account option, the agent installation task will be run as the local account, while the Discovery ...
  66. Note: Your changes will not take effect until you restart IIS. You can do it on completion of the template process or restart ...
  67. Object of type {0} did not read its entire buffer during deserialization. This is most likely an inbalance between the writes ...
  68. of Performance violations/sec. This counter records the total number of entry points that have exceeded their threshold. ...
  69. of the items in the groups you have selected for approval are already approved for deployment. These approvals will be replaced ...
  70. On the dialog 2 the next control pointers do not form a cycle. There is a pointer from 3 to 4], but there is no further pointer. ...
  71. On the dialog 2 the next control pointers do not form a cycle.There is a pointer from 3 to 4], but there is no further pointer ...
  72. Once you have identified the problem and taken corrective action, you can select 'Closed' which will remove the Alert from ...
  73. Once you have identified the problem and taken corrective action, you can select 'Closed' which will remove the Alert from ...
  74. One or more computers you are trying to manage are already in the process of being managed. Please resolve these issues via ...
  75. One or more objects selected in this profile may not be monitored if Run As credentials are not distributed to the appropriate ...