UI Translation

System Center Operations Manager 2007

  1. ModuleType composition error. ConditionDetection Module ({0}) cannot be a leaf node on this Composite DataSourceModule. DataSourceModule ...
  2. ModuleType composition error. ProbeAction Module (Type={0}, ID={1}) cannot be a leaf node in this composition. The composition ...
  3. ModuleType composition error. writeaction Module ({0}) cannot be a leaf node on this Composite DataSourceModule. DataSourceModule ...
  4. MomADAdmin failed to create a container, please make sure momadadmin is running under domain administrator priviledge: {0} ...
  5. MomAdAdmin was unable to revert changes made under OperationsManager. Please manually delete {0}({1}) under OperationsManager ...
  6. monitor failed to obtained work item statistics due to the following exception Workflow name: %2 Instance name: %3 Instance ...
  7. monitor successfully obtained work item statistics One or more workflows were affected by this. Workflow name: %2 Instance ...
  8. Monitoring class in user role scope is not allowed for this user role. The profile associated with this user role does not ...
  9. Monitoring class property value already exists in the discovery data item. Check for duplicate property values. MonitoringClassPropertyName: ...
  10. Monitoring class property value already exists in the discovery data item. Check for duplicate property values. MonitoringClassPropertyName: ...
  11. Monitoring is currently disabled due to a previous automatic shutdown. Please go to the Intercept Management Console to enable ...
  12. Monitoring is currently disabled due to a previous automatic shutdown. Please go to the Intercept Management Console to enable ...
  13. Monitoring object is not allowed for this user role scope. The profile associated with this user role does not allow monitoring ...
  14. Monitoring task in user role scope is not allowed for this user role. The profile associated with this user role does not ...
  15. Monitoring tests will be performed against the target servers you select. Target servers must be agent-managed Exchange 2007 ...
  16. Monitoring view in user role scope is not allowed. The profile associated with this user role does not allow view to be specified. ...
  17. Monitors the health of .NET applications on this computer. If this service is stopped detection of application failures may ...
  18. Monitors the health of the computer. The service may be configured to monitor the health of other computers in addition to ...
  19. More than 1 discovery data packet was returned by the PowerShell script, please review your script to ensure only one packet ...
  20. More than half of the members of the pool have acknowledged the most recent initialization check request. The pool member ...
  21. More than one default LanguagePack found in this ManagementPack. Only one LanguagePack can be marked with IsDefault attribute ...
  22. More than one Operational State cannot be associated with same HealthState {0}]. Failed to verify Operational State {1}]. ...
  23. More than one Operational State cannot be associated with same MonitorTypeState {0}]. Failed to verify Operational State ...
  24. More than" estimate used because some Resource file(s){0} size has not been calculated (see appropriate row(s) for details). ...
  25. More than" estimate used because some Resource file(s){0} size has not been calculated (see appropriate row(s) for details). ...
  26. MPXmlLoader cannot load a management pack with version number= null through this interface method. Call the version independent ...
  27. MSXML 6.0 is required for installing this Component. MSXML 6.0 setup will be launched; please complete it before installing ...
  28. MSXML 6.0 is required for installing this MOM Component, the MSXML 6.0 setup will be launched, please complete it before ...
  29. MultiByteToWideChar conversion failure Offset = %5 Buffer Length = %6 Directory = %7 Log File = %8 Error Code = %9 One or ...
  30. MultiByteToWideChar conversion failure Offset = %5 Buffer Length = %6 Directory = %7 Log File = %8 Error Code = %9 One or ...
  31. Multiple hosting relationships found for ClassType={0} - Relationship {1} is a hosting relationship defined on this Class ...
  32. Naming Conflict : Cannot import the {0} management pack. A management pack with the same ID {1} is currently in the import ...
  33. Net Framework 3.5 Service Pack 1 failed to install. Please install .Net Framework 3.5 Service Pack 1 and restart the install. ...
  34. Network devices, Agentless Windows computers and non-Windows computers are managed by a "proxy" Agent (on a Windows computer) ...
  35. New Management Pack with id:"%1", version:"%2" conflicts with cached Management Pack. Condition indicates wrong server configuration. ...
  36. New Management Pack with id:"%1", version:"%2" conflicts with cached Management Pack. Condition indicates wrong server configuration. ...
  37. New views cannot be opened for connected alerts. To open this view, open a new console window and connect to the other management ...
  38. Next call failed Namespace %5 Query %6 HRESULT %7 Details %8 One or more workflows were affected by this. Workflow name: ...
  39. Next call failed Namespace %5 Query %6 HRESULT %7 Details %8 One or more workflows were affected by this. Workflow name: ...
  40. No certificate could be loaded or created. This Health Service will not be able to communicate with other health services. ...
  41. No certificate could be loaded or created. This Health Service will not be able to communicate with other health services. ...
  42. No certificate was specified. This Health Service will not be able to communicate with other health services unless those ...
  43. No certificate was specified. This Health Service will not be able to communicate with other health services unless those ...
  44. No fields specified in Fields header Offset = %5 Directory = %6 Log File = %7 One or more workflows were affected by this. ...
  45. No fields specified in Fields header Offset = %5 Directory = %6 Log File = %7 One or more workflows were affected by this. ...
  46. No Management Group could be started. See previous errors for more specific details. If no errors are present, verify the ...
  47. No Management Group could be started. See previous errors for more specific details. If no errors are present, verify the ...
  48. No management groups were started. This may either be because no management groups are currently configured or a configured ...
  49. No management groups were started. This may either be because no management groups are currently configured or a configured ...
  50. No notification devices/servers configured or located for '%5' protocol One or more workflows were affected by this. Workflow ...
  51. No notification devices/servers configured or located for '%5' protocol One or more workflows were affected by this. Workflow ...
  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. No primary recipients were specified for the notification or all recipients are unavailable according to the schedules. Notification ...
  55. No primary recipients were specified for the notification or all recipients are unavailable according to the schedules. Notification ...
  56. No primary recipients were specified for the notification or all recipients are unavailable according to the schedules. Notification ...
  57. No primary recipients were specified for the notification or all recipients are unavailable according to the schedules. Notification ...
  58. Non-empty incremental data submitted and will be dropped. Discovery name: %2 Instance name: %3 Management group name: %1 ...
  59. Note that if you choose to recover the auto-saved documents, you must explicitly save them to overwrite the original documents. ...
  60. Note: by using a logon type of Service or Batch, some monitoring activities which access system resources requiring administrator ...
  61. Note: If you do not see all of the computers you expect to see, you can obtain information on troubleshooting discovery issues ...
  62. Note: Monitoring will take effect when the agents receive the updated monitoring rules and discover the appropriate objects. ...
  63. Note: SQL authentication has to be enabled explicitely on the SQL Server instance. Also, the special SQL user 'sa' cannot ...
  64. Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides ...
  65. Note: The ID shown is the unique identifier for this report operator role. To control access to reports using this report ...
  66. Note: The Management Servers list contains only servers on which Client Monitoring is not enabled. To modify or disable Client ...
  67. Note: The MOMADAdmin.exe command line tool must be run by a domain administrator before running this wizard. This tool can ...
  68. Note: The MOMADAdmin.exe command line tool must be run by a domain administrator before running this wizard. This tool can ...
  69. Note: The System Center "Service Desk" Setup Wizard will automatically install Service Desk reporting on an existing Microsoft ...
  70. Note: There are additional settings that can be used to suppress alerts. Click the "Advanced" button to configure more suppression ...
  71. Note: These changes will not take effect until you run repair on the agents. Follow the steps listed in the Operations Manager ...
  72. Note: This setting applies only when scanning Active Directory. You can configure how these objects will be discovered, on ...
  73. Note: When selecting the local account option, the agent installation task will be run as the local account, while the Discovery ...
  74. Note: When selecting the local account option, the agent installation task will be run as the local account, while the Discovery ...
  75. Note: Your changes will not take effect until you restart IIS. You can do it on completetion of the template process or restart ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)