System Center Operations Manager 2007

  1. Operations Manager will discover the devices that you specify and all devices that are connected to the devices that you ...
  2. OperationsManager container doesnt exist in domain %5 or the Run As Account associated with the AD based agent assignment ...
  3. OperationsManager container doesnt exist in domain %5 or the Run As Account associated with the AD based agent assignment ...
  4. OpsMgr Config Service configuration state has become invalid. This maybe a temporary issue that may be recovered from automatically. ...
  5. OpsMgr Config Service could not retrieve a consistent state from the OpsMgr database due to too frequent database changes. ...
  6. OpsMgr Config Service failed to adjust the privileges at start up. It is not recommended to run the service with unnecesarry ...
  7. OpsMgr Config Service failed to send the dirty state notifications to the dirty OpsMgr Health Services. This may be happening ...
  8. OpsMgr Config Service has lost connectivity to the OpsMgr database, therefore it can not get any updates from the database. ...
  9. OpsMgr has received configuration for management group %1 from the Configuration Service, but failed to process the configuration. ...
  10. OpsMgr has received configuration for management group %1 from the Configuration Service, but failed to process the configuration. ...
  11. OpsMgr has received confirmation for management group %1 from the Configuration Service that our existing configuration is ...
  12. OpsMgr has received confirmation for management group %1 from the Configuration Service that our existing configuration is ...
  13. OpsMgr has received new configuration for management group %1 from the Configuration Service. The new state cookie is "%2" ...
  14. OpsMgr has received new configuration for management group %1 from the Configuration Service. The new state cookie is "%2" ...
  15. OpsMgr Health Service "%3" running on "%1" has contacted OpsMgr Config Service to synchronize its configuration state. The ...
  16. OpsMgr running for management group %1 failed to accept connection from health service %2 (%3). It is connecting with different ...
  17. OpsMgr running for management group %1 failed to start HTTPS server. Required dependency feature (WWSAPI) is missing or not ...
  18. OpsMgr was unable to set up a communications channel to %1 and there are no failover hosts. Communication will resume when ...
  19. OpsMgr was unable to set up a communications channel to %1 and there are no failover hosts. Communication will resume when ...
  20. OpsMgr was unable to set up a communications channel to %1. Communication will resume when %1 is available and communication ...
  21. OpsMgr was unable to set up a communications channel to %1. Communication will resume when %1 is both available and allows ...
  22. OpsMgr's configuration may be out-of-date for management group %1, and has requested updated configuration from the Configuration ...
  23. OpsMgr's configuration may be out-of-date for management group %1, and has requested updated configuration from the Configuration ...
  24. Options: Option Description - - -collector: DNS name of AdtServer machine (If the -collector option is omitted, AdtAdmin ...
  25. Out of disk space - Volume: '[2]'; required space: 3 KB; available space: 4 KB. If rollback is disabled, enough space is ...
  26. Out of disk space - Volume: 2]; required space: 3 KB; available space: 4 KB. If rollback is disabled, enough space is available. ...
  27. Output Queue Length is the length of the output packet queue (in packets). If this is longer than two, there are delays and ...
  28. Override {0} is a duplicate to Override {1} defined within the same ManagementPack. Please remove any one of the duplicate ...
  29. Overrides are used to change the monitor, diagnostic and recovery configuration. You can also view all overrides applied ...
  30. Overrides are used to change the monitor, diagnostic and recovery configuration. You can also view all overrides applied ...
  31. Overrides are used to modify the {0} configuration. You can override the configuration by choosing one of the options below: ...
  32. Overwrite the existing query, or type another name to save a new query. Each query consists of criteria, as well as sorting ...
  33. Parameter replacement during creation of the alert failed causing unexpected suppression used. Alert: %6 Workflow: %2 Instance: ...
  34. Parameter replacement during creation of the alert failed causing unexpected suppression used. Alert: %6 Workflow: %2 Instance: ...
  35. Parameter replacement during creation of the alert failed. Alert: %3 Workflow ID: %2 Management Group ID: %1 Failing replacement: ...
  36. Parameter replacement during creation of the alert failed. Alert: %6 Workflow: %2 Instance: %3 Instance ID: %4 Management ...
  37. PDB Storage configuration failed. Please, run PdbImport.exe utility from Utilities directory manually after installation ...
  38. PDBStorage.config has ivalid format. To recover it use PdbImport.exe from Utilities folder. Use /? key to call PdbImport ...
  39. Pending actions cannot be performed for agents that report to different management servers. Please select a single management ...
  40. Performance Aggregator Module was not able to aggregate performance data due to the following exception.: Error Details: ...
  41. Performance Aggregator Module was unloaded due to insufficient permissions. Error Details: %5 One or more workflows were ...
  42. Performance data couldn't be inserted to the database. This could have happened because of one of the following reasons: ...
  43. Performance data couldn't be inserted to the database. This could have happened because of one of the following reasons: ...
  44. Performance data from the Health Service could not be collected since opening the shared data failed with error %1 (%2). ...
  45. Performance data from the Health Service could not be collected since required registry keys could not be read, the error ...
  46. Performance data from the Health Service could not be collected since required registry keys could not be read, the error ...
  47. Performance data from the OpsMgr connector could not be collected since required registry keys could not be read, the error ...
  48. Performance data from the OpsMgr connector could not be collected since required registry keys could not be read, the error ...
  49. PerformanceCounters in the module configuration is invalid. One or more workflows were affected by this. Workflow name: %2 ...
  50. Phone number must start with + or 0 and contain only numbers after that and include country code, area code, number such ...
  51. Phone number must start with + or 0 and contain only numbers after that and include country code, area code, number such ...
  52. Please either turn off the Windows firewall or configure it for proper functioning of this component. Please see the documentation ...
  53. Please enter a number from {0} to {1} to reduce performance data collection. The number represents the sampling rate for ...
  54. Please follow the steps provided in the link below to download .NET Framework 3.0 Runtime for X86 and X64 bit systems. X86 ...
  55. Please follow the steps provided in the link below to download Windows PowerShell for X86 and X64 bit systems. http://ww ...
  56. Please follow the steps provided in the link below to download Windows PowerShell for X86 and X64 bit systems. http://ww ...
  57. Please follow the steps provided in the links below to download .Net Framework 2.0 for X86 and x64 bit systems X86 version: ...
  58. Please follow the steps provided in the links below to download .Net Framework 2.0 for X86 and x64 bit systems X86 version: ...
  59. Please follow the steps provided in the links below to download .Net Framework 3.5 SP1 http://go.microsoft.com/fwlink/?LinkId=131605 ...
  60. Please install Microsoft SQL Server 2005 Reporting Services ServicePack 1. Please use the provided link for more information: ...
  61. Please install the required operating system or its service pack. You can download the latest service packs from http://download.microsoft.com ...
  62. Please install the required operating system or its service pack. You can download the latest service packs from http://download.microsoft.com ...
  63. Please install WS-Management from http://www.microsoft.com/downloads/details.aspx?familyid=845289ca-16cc-4c73-8934-dd46b5ed1d33displaylang=en ...
  64. Please make sure the Operations Manager SDK service is running on Root Management Server, the user running setup is MOM Administrator. ...
  65. Please make sure the Operations Manager SDK service is running on Root Management Server, the user running setup is Operations ...
  66. Please move all agents, gateway servers, and any devices directly reporting to the Root Management Server to another Management ...
  67. Please move your Operations Manager Data Warehouse to a SQL instance with a supported collation. Consult the deployment guide ...
  68. Please move your Operations Manager Operational Database to a SQL instance with a supported collation. Consult the deployment ...
  69. Please provide a location to which you want the encryption key backed up, or from which you want the encryption key restored. ...
  70. Please provide a location to which you want the encryption key backed up, or from which you want the encryption key restored. ...
  71. Please provide a name for your management group. The name of your management group could represent your company name, organization ...
  72. Please read the license agreement carefully. Press the PAGE DOWN key to see the rest of the agreement. You must accept the ...
  73. Please specify a value for either ExecuteOnDiagnostic attribute or ExecuteOnState attribute. One of them MUST be specified ...
  74. Please specify a value ONLY for ExecuteOnDiagnostic attribute or ExecuteOnState attribute. Both attributes cannot be specified ...
  75. Please specify an external Application Advisor Console Address (not containing localhost or 127.0.0.1) before creating a ...