System Center Operations Manager 2012

  1. The OpsMgr Connector could not connect to %1 because negotiation could not agree on the required level of security. The server ...
  2. The OpsMgr Connector could not connect to %1:%2. The error code is %3(%4). Please verify there is network connectivity, the ...
  3. The OpsMgr Connector could not initialize Windows Sockets. The version required is %1.%2, but the version available is %3.%4. ...
  4. The OpsMgr Connector could not resolve the IP for %1. The error code is %2(%3). Please verify DNS is working properly in ...
  5. The OpsMgr Connector for management group %1 cannot connect to Active Directory to retrieve connection policy. The error ...
  6. The OpsMgr Connector has found a duplicate record for %1 in its configuration for management group %2. The duplicate record ...
  7. The OpsMgr Connector has found both an Agent and a Server Management Group with the name '%1'. The Server Management Group ...
  8. The OpsMgr Connector has found multiple primary relationships in Active Directory for management group %1. The primary relationship ...
  9. The OpsMgr Connector has received a bad packet from the device at %1. The first bytes in the packet are in the binary data ...
  10. The OpsMgr Connector has received an oversized package from IP %1. OpsMgr prevents large packages from being delivered to ...
  11. The OpsMgr Connector negotiated the use of Kerberos based mutual authentication with %1, but Active Directory is not available ...
  12. The OpsMgr Connector negotiated the use of mutual authentication with %1, but Active Directory is not available and no certificate ...
  13. The OpsMgr Connector successfully retrieved policy from Active Directory for management group %1. However, that policy is ...
  14. The OpsMgr SDK Client threw an unknown exception while processing a monitoring object membership change notification: %1 ...
  15. The OpsMgr SDK Client threw an unknown exception while processing a type cache refresh notification. The cache was not updated ...
  16. The override session ticket encryption key '{0}' is not found. Please verify the application configuration to ensure that ...
  17. The page {1} in the assembly {0} could not be loaded. Please make sure that the account you are running under has sufficient ...
  18. The page {1} in the assembly {0} could not load the inputs or configuration supplied to it. Please make sure that the inputs ...
  19. The parameter '{0}' contains an invalid IP '{1}'.{2}The parameter should be a list of IP addresses separated by commas ','.{2}An ...
  20. The parameter is not set by a custom override or by a management pack. The effective value of this parameter is the default ...
  21. The password for RunAs account %1\%2 for management group %5 is expiring on %3. If the password is not updated by then, the ...
  22. The password used to discover network devices is called a "community string". Please specify your network device community ...
  23. The password you entered is weak. It is recommended that you enter a strong password by using a combination of A-Z. a-z, ...
  24. The pool member cannot send a lease request to acquire ownership of managed objects assigned to the pool because half or ...
  25. The pool member has initialized. Management Group: %1 Management Group ID: %2 Pool Name: %3 Pool ID: %4 Pool Version: %5 ...
  26. The pool member no longer owns any managed objects assigned to the pool because half or fewer members of the pool have acknowledged ...
  27. The PowerShell script could not be started because the following data item reference could not be resolved. $Data/%8$ Please ...
  28. The PowerShell script failed failed to collect script output with below exception %7 Script Name: %5 One or more workflows ...
  29. The PowerShell script failed with below exception %7 Script Name: %5 One or more workflows were affected by this. Workflow ...
  30. The PowerShell script will be dropped because the it has been waiting in the queue for more than %7 minutes. Script Name: ...
  31. The process could not be created because the maximum number of asynchronous responses (%12) has already been reached, and ...
  32. The process could not be started because some data items could not be resolved. Please check the configured application, ...
  33. The Process Information Probe could not collect process information. Error: %5 : %6 One or more workflows were affected by ...
  34. The process started at %5 failed failed to initialize %8 with error: %10 Please verify that this process is creating %8. ...
  35. The process started at %5 failed to create %8, no errors detected in the output. The process exited with %10 Command executed: ...
  36. The process started at %5 failed to create %8. Errors found in output: %10 Command executed: %6 Working Directory: %7 One ...
  37. The process started at %5 was terminated because the HealthService requested the workflow to stop, some data may have been ...
  38. The process started at %5 was terminated due to a failure in collecting output due to error '%10', some data may have been ...
  39. The process will be dropped because the it has been waiting in the queue for more than %11 minutes. Command executed: %6 ...
  40. The program collects data about how all console users in the management group use this product without interrupting them. ...
  41. The program collects information about computer hardware and how all of the users of this local console in this management ...
  42. The properties for this object cannot be viewed because the management pack containing this object does not have UI information. ...
  43. The property value type '{0}' is not supported. Only primitive types, strings or arrays of primitive types can be used as ...
  44. The propetry value type '{0}' is not supported. Only primitive types, strings or arrays of primitive types can be used as ...
  45. The provided Discovery Scope value is invalid. The value needs to be either a valid IP address, a valid DNS name or two valid ...
  46. The provided DiscoveryResult cannot be added to the SelectedDiscoveryResults because it does not exist in the DiscoveryResults ...
  47. The provided older version of ManagementPack {0} - Version-{1} is actually a higher version than 'newer' ManagementPack {2}] ...
  48. The public key token is null for the management pack loaded from file: {0} and it does not match the expected public key ...
  49. The public key token KeyToken={0} of the management pack loaded from file: {1} does not match the expected public key token ...
  50. The rate at which items are being purged from the queue because they have not been sent within the queue expiration time. ...
  51. The rate at which the process is reading and writing bytes in I/O operations. This counter counts all I/O activity generated ...
  52. The rate of items which are scheduled to re-send because they have not been acknowledged and are marked as requiring guarenteed ...
  53. The recommended prerequisites for installation have not been met. You may continue to install Operations Manager, but you ...
  54. The recovery status notification was not setup correctly. The notification for recovery job with id '%1' will not be processed. ...
  55. The reference to MPElement ID={0} is incorrect. This element is of type {1} which does not have the accessibility flag and ...
  56. The Registry Probe could not collect the following attributes from the registry of the computer '%5'. %6 One or more workflows ...
  57. The Registry Probe could not connect to the registry of the computer '%5'. Error: %6 One or more workflows were affected ...
  58. The Registry Probe successfully re-connected to the registry of the computer '%5'. One or more workflows were affected by ...
  59. The remote name could not be resolved: '%7'. Please check the connection to the remote server or the proxy setting in the ...
  60. The removal of server {0} failed because it is remotely managing devices and/or computers. From the Agent Management view, ...
  61. The removal of server {0} failed because there are agents reporting to it. From the Agent Management view, you must first ...
  62. The removal of server {0} from the management group completed successfully. If you have not already uninstalled the Gateway ...
  63. The Report Operator profile includes a set of privileges designed for users that need access to Reports. A role based on ...
  64. The Report Security Administrator profile includes a set of privileges designed to enable the integration of SQL Server Reporting ...
  65. The Reporting component was not installed or is not being installed. If the reporting component is not installed, Application ...
  66. The Reporting database has invalid schema version. Please, run the Configuration Utility and configure Reporting database. ...
  67. The Reporting feature provides the ability to build and present reports in the Operations Manager console based on data queried ...
  68. The Reporting Service has been disabled in configuration file. Please, run the Configuration Utility to enable Reporting. ...
  69. The request has been sent to the Operations Manager Server. The Operations Manager Server will retrieve this page for verification. ...
  70. The requested event is no longer available because it has been removed from the operational database. A similar event from ...
  71. The requested event is no longer available. Event details may have been requested from an old alert where the underlying ...
  72. The requested ManagementPackElement Type={0}, ID={1} in ManagementPack {2} is not Accessible outside this ManagementPack. ...
  73. The requested ManagementPackElement Type={0}, ID={1} was found in ManagementPack {2} but this ManagementPack is not listed ...
  74. The requested view will contain at least {0} objects and may require substantial time to render. Do you wish to continue? ...
  75. The response '%5' tried to submit a non-status alert with invalid field values. The alert fields ServerRole, ServerRoleInstance, ...