System Center Operations Manager 2007

  1. The number of queued events has exceeded %3. New events will be accepted when there are less than %3 events in the queue. ...
  2. The number of session packets which were recieved by the connector and had to be reassembled per second. This can be caused ...
  3. The number of SSPI negotiation packets which were recieved by the connector and had to be reassembled per second. This can ...
  4. The object returned from the provider as type: {0} is not a supported data object collection. Make sure to always use the ...
  5. The object returned from the provider as type: {0} is not a supported type. Make sure to always use the IDataCommandContext ...
  6. The object you want to view is unavailable, either because it has been deleted from the system, it is in a management pack ...
  7. The object {0} is not currently in Maintenance Mode. Would you like to schedule a new Maintenance Mode with the current settings? ...
  8. The operation cannot be performed as the MonitoringSecureData object does not have the AuthenticationKey field populated. ...
  9. The Operations console provides an interface for performing monitoring, administration, authoring, and reporting actions. ...
  10. The Operations Manager 2007 audit collector service encountered a fatal error while attempting to perform a database operation. ...
  11. The Operations Manager 2007 audit collector service encountered a fatal error while attempting to perform a database operation. ...
  12. The Operations Manager 2007 database component requires Microsoft SQL Server 2005 Service Pack 1 or later. The selected instance ...
  13. The Operations Manager 2007 database requires a minimum of 500MB size. To continue setup click Back, change the database ...
  14. The Operations Manager 2007 R2 Operations console or Web console installation is corrupt. Please uninstall and then reinstall ...
  15. The Operations Manager 2007 R2 web console was also detected on this computer and will be uninstalled. The web console cannot ...
  16. The Operations Manager 2007 setup failed to start the Microsoft SQL server services. To continue setup, go back and choose ...
  17. The Operations Manager Administrators user role is created at setup time and cannot be deleted. This role must contain one ...
  18. The Operations Manager Agent control panel can be run by only a user account that is a member of the Administrators group ...
  19. The Operations Manager Agent on this computer is getting repaired. This may take several minutes depending on your network/computer ...
  20. The Operations Manager Report Security Administrators user role is designed to enable the integration of SQL Server Reporting ...
  21. The Operations Manager Report Security Administrators user role is designed to enable the integration of SQL Server Reporting ...
  22. The Operations Manager Reporting feature is not installed.{0}Before you use Application Advisor, you must install the Operations ...
  23. The Operations Manager Reporting feature was installed on this computer. A Management server cannot be installed after Reporting ...
  24. The Operations Manager Server cannot process the install/uninstall request for computer %2 due to failure of operating system ...
  25. The Operations Manager Server could not execute WMI Query "%6" on computer %2. Operation: %1 Install account: %3 Error Code: ...
  26. The Operations Manager Server could not find directory %6. Agent will not be installed on computer %2. Please verify the ...
  27. The Operations Manager Server could not start the MOMAgentInstaller service on computer "%2" in the time. This service is ...
  28. The Operations Manager Server detected that computer "%1" is running an incompatible version of the Operations Manager agent ...
  29. The Operations Manager Server detected that computer %2 has an unsupported operating system or service pack version. The ...
  30. The Operations Manager Server detected that computer %2 may need to be rebooted after this operation. Operation: %1 Install ...
  31. The Operations Manager Server detected that Operations Manager Agent does not exists on remote computer %1. The Operations ...
  32. The Operations Manager Server detected that remote computer %2 has older version of Windows Installer installed. Please update ...
  33. The Operations Manager Server detected that the actual NetBIOS name %6 is not same as the given NetBIOS name provide for ...
  34. The Operations Manager Server detected that the following services on the remote computer are not running. These services ...
  35. The Operations Manager Server detected that the Service Control Manager on computer "%2" already contains MOMAgentInstaller ...
  36. The Operations Manager Server detected that the Windows Installer service (MSIServer) is disabled on computer "%2". This ...
  37. The Operations Manager Server failed to acquire lock to remote computer %2. This means there is already an agent management ...
  38. The Operations Manager Server failed to apply software updates to computer "%1". Error Code: %2 Error Description: %3 Microsoft ...
  39. The Operations Manager Server failed to apply software updates to computer "%2". Operation: %1 Install account: %3 Error ...
  40. The Operations Manager Server failed to copy agent install logs from remote machine %2. Operation: %1 Install account: %3 ...
  41. The Operations Manager Server failed to install the MOMAgentInstaller service on computer "%2". See error details below. ...
  42. The Operations Manager Server failed to open service control manager on computer %2. Therefore, the Server cannot complete ...
  43. The Operations Manager Server failed to perform specified operation on computer %2. Operation: %1 Install account: %3 Error ...
  44. The Operations Manager Server found that the specified computer "%2" is a cluster virtual server. The Operations Manager ...
  45. The Operations Manager server or gateway cannot be installed on a machine that already has AVIcode Intercept Agent installed. ...
  46. The Operations Manager server or gateway cannot be installed on a machine that already has Operations Manager ASP.Net monitoring. ...
  47. The Operations Manager Server successfully applied software updates to computer "%2". The following software updates are ...
  48. The Operations Manager Server successfully completed the operation %1 on remote computer %2. Install account: %3 Error Code: ...
  49. The Operations Manager Server successfully installed an agent remotely on computer %1, but was unable to apply the existing ...
  50. The Operations Manager Server was unable to establish a DCOM connection with the MOMAgentInstaller service on computer %2 ...
  51. The Operations Manager Web console must be installed to an existing site. The selected site is used by Operations Manager ...
  52. The Operations Manager web console requires some additional configuration to be fully functional. Without this configuration, ...
  53. The Operations Manager web console requires that JavaScript be enabled. Enable "Active Scripting" in the Security Settings ...
  54. The Operations Manager Web console was installed on this computer. A Management server cannot be installed after the web ...
  55. The Operations Manager web console was not configured successfully on this computer. Some views in the web console will not ...
  56. The Operator profile includes a set of privileges designed for users that need access to Alerts, Views and Tasks. A role ...
  57. The Ops Mgr database will be upgraded, it is highly recommended that you back it up and make sure the transaction log space ...
  58. The OpsMgr Connector connected to %1, but the connection was closed immediately after authentication occured. The most likely ...
  59. The OpsMgr Connector connected to %1, but the connection was closed immediately after authentication occurred. The most likely ...
  60. The OpsMgr Connector connected to %1, but the connection was closed immediately without authentication taking place. The ...
  61. The OpsMgr Connector connected to %1, but the connection was closed immediately without authentication taking place. The ...
  62. The OpsMgr Connector could not connect to %1 because mutual authentication failed. Verify the SPN is properly registered ...
  63. The OpsMgr Connector could not connect to %1 because mutual authentication failed. Verify the SPN is properly registered ...
  64. The OpsMgr Connector could not connect to %1 because negotiation could not agree on the required level of security. The server ...
  65. The OpsMgr Connector could not connect to %1 because negotiation could not agree on the required level of security. The server ...
  66. The OpsMgr Connector could not connect to %1:%2. The error code is %3(%4). Please verify there is network connectivity, the ...
  67. The OpsMgr Connector could not connect to %1:%2. The error code is %3(%4). Please verify there is network connectivity, the ...
  68. The OpsMgr Connector could not initialize Windows Sockets. The version required is %1.%2, but the version available is %3.%4. ...
  69. The OpsMgr Connector could not initialize Windows Sockets. The version required is %1.%2, but the version available is %3.%4. ...
  70. The OpsMgr Connector could not resolve the IP for %1. The error code is %2(%3). Please verify DNS is working properly in ...
  71. The OpsMgr Connector could not resolve the IP for %1. The error code is %2(%3). Please verify DNS is working properly in ...
  72. The OpsMgr Connector for management group %1 cannot connect to Active Directory to retrieve connection policy. The error ...
  73. The OpsMgr Connector for management group %1 cannot connect to Active Directory to retrieve connection policy. The error ...
  74. The OpsMgr Connector has found a duplicate record for %1 in it's configuration for management group %2. The duplicate record ...
  75. The OpsMgr Connector has found a duplicate record for %1 in its configuration for management group %2. The duplicate record ...