UI Translation

System Center Operations Manager 2007

  1. The removal of server {0} failed because it is remotely managing devices and/or computers. From the Agent Management view, ...
  2. The removal of server {0} failed because there are agents reporting to it. From the Agent Management view, you must first ...
  3. The removal of server {0} from the management group completed successfully. If you have not already uninstalled the Gateway ...
  4. The Report Operator profile includes a set of privileges designed for users that need access to Reports. A role based on ...
  5. The Report Security Administrator profile includes a set of provileges designed to enable the integration of SQL Server Reporting ...
  6. The Reporting component was not installed or is not being installed. If the reporting component is not installed, Application ...
  7. The Reporting database has invalid schema version. Please, run the Configuration Utility and configure Reporting database. ...
  8. The Reporting feature provides the ability to build and present reports in the Operations Manager console based on data queried ...
  9. The Reporting Service has been disabled in configuration file. Please, run the Configuration Utility to enable Reporting. ...
  10. The request for management pack identified by version independent identity "%2" and version dependent identity "%3" requested ...
  11. The request has been sent to the Operations Manager Server. The Operations Manager Server will retrieve this page for verification. ...
  12. The request to synchronize state for OpsMgr Health Service identified by "%1" failed due to the following exception "%2". ...
  13. The requested event is no longer available because it has been removed from the operational database. A similar event from ...
  14. The requested event is no longer available. Event details may have been requested from an old alert where the underlying ...
  15. The requested ManagementPackElement Type={0}, ID={1} in ManagementPack {2} is not Accessible outside this ManagementPack. ...
  16. The requested ManagementPackElement Type={0}, ID={1} was found in ManagementPack {2} but this ManagementPack is not listed ...
  17. The requested tier does not allow connector initiated connections. Please connect to a different tier or update the tier ...
  18. The requested tier does not allow connector initiated connections. Please connect to a different tier or update the tier ...
  19. The requested view will contain at least {0} objects and may require substantial time to render. Do you wish to continue? ...
  20. The resolution state on one or more alerts could not be modified due to being out of sync with the server. Please try the ...
  21. The response '%5' tried to submit a non-status alert with invalid field values. The alert fields ServerRole, ServerRoleInstance, ...
  22. The response '%5' tried to submit a non-status alert with invalid field values. The alert fields ServerRole, ServerRoleInstance, ...
  23. The response '%5' tried to submit a status alert with invalid field values. The alert fields ServerRole, ServerRoleInstance ...
  24. The response '%5' tried to submit a status alert with invalid field values. The alert fields ServerRole, ServerRoleInstance ...
  25. The restoration of SQL Reporting Services is almost complete, you might have to open the SQL Reporting Services configuration ...
  26. The return address is not valid. Configure the address in the form of "sip:[email protected]". The text "sip:" must be ...
  27. The Root Connector has received bad packets which have been dropped. It received %1 such packet(s) in the last five minutes ...
  28. The Root Connector has received bad packets which have been dropped. It received %1 such packet(s) in the last five minutes ...
  29. The root management server (Healthservice) has stopped heartbeating soon after {0}. This adversely affects all availability ...
  30. The root management server (HealthService) is running but has reported limited functionality soon after {0}. The specific ...
  31. The rule type {0} cannot be created because the UI for the rule type is not defined in the management packs. Please import ...
  32. The rule you are trying to delete cannot be deleted because a service level objective references it. The service level objective ...
  33. The rule {0} cannot be edited because the UI for the rule is not defined in the management packs. Please import the appropriate ...
  34. The Run As account cannot be deleted because it is associated with a Run As profile, please remove the association before ...
  35. The Run As account cannot be deleted because it is associated with a Run As profile. Please delete the Run As profile to ...
  36. The Run As account cannot be deleted because it is associated with a Run As profile. Please remove the association and try ...
  37. The Run As account could not be created. The SDK service may be unavailable. The following steps may resolve this problem: ...
  38. The Run As account you selected was distributed to the proxy agent. Credentials for any less-secure Run As accounts included ...
  39. The Run As account you selected was not distributed to the proxy agent. In order for the wizard to continue, you must distribute ...
  40. The Run As profile could not be created. The error was: {0} The following steps may resolve this problem: - Ensure that all ...
  41. The RunAs account %1\%2 for management group %5 is expiring on %3. If the account expiration is not extended by then, the ...
  42. The RunAs account %1\%2 for management group %5 is expiring on %3. If the account expiration is not extended by then, the ...
  43. The SCE Group identified by '%3' could not synchronize to its associated WSUS Group identified by '%4' because a connection ...
  44. The SCE Group identified by '%3' could not synchronize to its associated WSUS Group identified by '%4' because a connection ...
  45. The SCE Group identified by '%3' could not synchronize to its associated WSUS Group identified by '%4' because a connection ...
  46. The SCE Group identified by '%3' could not synchronize to its associated WSUS Group identified by '%4' because a connection ...
  47. The SCE Group identified by '%3' could not synchronize to its associated WSUS Group identified by '%4' because the SCE Group ...
  48. The SCE Group identified by '%3' could not synchronize to its associated WSUS Group identified by '%4' because the SCE Group ...
  49. The scheduler configuration received by the time filter can not be displayed and might be overwritten upon completition of ...
  50. The scheduler module UI can not understand the loaded configuration. Continue with this operation may cause inconsistent ...
  51. The schema of the Health Service store is out of date or the computer has been renamed. The store will be deleted and recreated. ...
  52. The script data source failed to initialize for management group '%5', target computer '%6', and data type '%7' any rules ...
  53. The script data source failed to initialize for management group '%5', target computer '%6', and data type '%7' any rules ...
  54. The script data source for management group '%5', target computer '%6',and data type '%7' failed to recover any rules using ...
  55. The script data source for management group '%5', target computer '%6',and data type '%7' failed to recover any rules using ...
  56. The script data source for management group '%5', target computer '%6',and data type '%7' failed to transmit the data received ...
  57. The script data source for management group '%5', target computer '%6',and data type '%7' failed to transmit the data received ...
  58. The script data source for management group '%5', target computer '%6',and data type '%7' has recovered from the previous ...
  59. The script data source for management group '%5', target computer '%6',and data type '%7' has recovered from the previous ...
  60. The Script name field must contain a valid script name and extension (i.e. MyScript.vbs) and must not contain any directory ...
  61. The Script name field must contain a valid script name and extension (i.e. MyScript.vbs) and must not contain any of the ...
  62. The SDK could not create or approve a pending action for an agent because it could not validate the data sent by that agent. ...
  63. The SDK could not create or approve a pending action for an agent because it could not validate the data sent by that agent. ...
  64. The SDK provides a data access layer between agents, the consoles, and the database. The Config service distributes Configuration ...
  65. The SDK service is not able to generate auditing events for SDK operations. Verify that the SDK service account has the correct ...
  66. The SDK service is not able to generate auditing events for SDK operations. Verify that the SDK service account has the correct ...
  67. The SDK service was unable to read license information. This is probably due to an incorrectly restored Root Management Server. ...
  68. The SDK was unable to synchronize its snapshot of monitoring object instances with its cached monitoring class information. ...
  69. The secure data to health service reference cannot be inserted. The most common reason for this is the health service id ...
  70. The selected agent was manually installed. Please manually uninstall the agent on the server to remove it and then reject ...
  71. The selected agent was manually installed. Please manually uninstall the agent on the server to remove it and then reject ...
  72. The selected file cannot be opened. The file has an invalid name, please change the name to '{0}' to open the MP. This naming ...
  73. The selected management pack cannot be deleted. This might be because it is currently being deleted or it has already been ...
  74. The selected manual agent will now be approved and moved to the Agents view under the Administration node. Do you want to ...
  75. The selected manual agent will now be approved and moved to the Agents view under the Administration node. Do you want to ...
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)