System Center Operations Manager 2007

  1. AdtServer encountered the following problem during startup: Task: Open SSPI Package Failure: The SSPI package could not be ...
  2. AdtServer encountered the following problem during startup: Task: Open SSPI Package Failure: The SSPI package could not be ...
  3. AdtServer encountered the following problem during startup: Task: Open SSPI Packages Failure: Credentials could not be acquired ...
  4. AdtServer encountered the following problem during startup: Task: Open SSPI Packages Failure: Credentials could not be acquired ...
  5. AdtServer encountered the following problem during startup: Task: Open SSPI Packages Failure: Credentials could not be acquired ...
  6. AdtServer encountered the following problem during startup: Task: Open SSPI Packages Failure: Credentials could not be acquired ...
  7. AdtServer encountered the following problem during startup: Task: Register SPN Failure: Verification / registration of SPNs ...
  8. AdtServer encountered the following problem during startup: Task: Register SPN Failure: Verification / registration of SPNs ...
  9. AdtServer encountered the following problem during startup: Task: Version Check Failure: ACS Collector is only supported ...
  10. AdtServer encountered the following problem during startup: Task: Version Check Failure: ACS Collector is only supported ...
  11. AdtServer encountered the following problem during startup: Task: Version Check Failure: Error retrieving OS version Error: ...
  12. AdtServer encountered the following problem during startup: Task: Version Check Failure: Error retrieving OS version Error: ...
  13. After a period of time, active alerts which are no longer relevant can be automatically resolved. Once an alert is in a resolved ...
  14. After a period of time, active alerts which are no longer relevant can be automatically resolved. Once an alert is in a resolved ...
  15. Agent failed to communicate with SE-Viewer Server. Please verify SE-Viewer Server location and HTTP connectivity between ...
  16. Agent failed to communicate with SE-Viewer Server. Please verify SE-Viewer Server location and HTTP connectivity between ...
  17. Agent failed to communicate with SE-Viewer Server. Please verify SE-Viewer Server location and HTTP connectivity between ...
  18. Agent failed to communicate with SE-Viewer Server. Please verify SE-Viewer Server location and HTTP connectivity between ...
  19. Agent failed to communicate with SE-Viewer Server. SE-Viewer Web Service URL: %1 Error Message: %2 %3
  20. Agent {0} is currently managed through Active Directory. To change the agent assignment, please update the Active Directory ...
  21. Agents can generate heartbeats at a specific interval to ensure that they are functioning properly. You can specify how the ...
  22. Ajax Post Data and Response Text were not collected because monitored page is considered to have a complex DOM structure. ...
  23. Ajax Response Text was not been collected because monitored page is considered to have a complex DOM structure. See notes ...
  24. Ajax {0} was not collected because Client Side Monitoring has not been enabled on the server. {0} time may be greater than ...
  25. Alert properties on one or more alerts could not be modified due to being out of sync with the server. Please try the operation ...
  26. Alert resolution states allow you to classify alerts into various states, and to define the behavior associated with each ...
  27. Alert subscription data source module configuration was invalid. The following error(s) were encountered: Exception Message: ...
  28. Alert subscription data source module configuration was invalid. The following error(s) were encountered: Exception Message: ...
  29. Alert subscription data source module encountered alert subscriptions that took a long time to execute their database query. ...
  30. Alert subscription data source module encountered alert subscriptions that took a long time to execute their database query. ...
  31. Alert subscription data source module encountered alert subscriptions that were waiting for a long time to receive an acknowledgement. ...
  32. Alert subscription data source module encountered alert subscriptions that were waiting for a long time to receive an acknowledgement. ...
  33. Alert subscription data source module has recovered from the long wait to execute database queries for alert subscriptions. ...
  34. Alert subscription data source module has recovered from the long wait to execute database queries for alert subscriptions. ...
  35. Alert subscription data source module has recovered from the long wait to receive acknowledgements for alert subscriptions. ...
  36. Alert subscription data source module has recovered from the long wait to receive acknowledgements for alert subscriptions. ...
  37. Alert subscription data source module was unable to find alerts that match the subscription because of database errors. The ...
  38. Alert subscription data source module was unable to find alerts that match the subscription because of database errors. The ...
  39. Alert subscription data source module was unable to notify the runtime of errors. The following error(s) were encountered: ...
  40. Alert subscription data source module was unable to notify the runtime of errors. The following error(s) were encountered: ...
  41. Alert subscription data source module was unable to post alerts that match the subscription because of runtime errors. The ...
  42. Alert subscription data source module was unable to post alerts that match the subscription because of runtime errors. The ...
  43. Alert subscription data source module was unable to read the time zone configuration because of errors. Defaulting the local ...
  44. Alert subscription data source module was unable to read the time zone configuration because of errors. Defaulting the local ...
  45. Alert subscription data source module was unable to retrieve the state because of database errors. The state is being set ...
  46. Alert subscription data source module was unable to retrieve the state because of database errors. The state is being set ...
  47. Alert subscription data source module was unable to retrieve the state because of errors. The state is being set from the ...
  48. Alert subscription data source module was unable to retrieve the state because of errors. The state is being set from the ...
  49. Alert subscription data source module was unable to save the state because of database errors. If the module is reset you ...
  50. Alert subscription data source module was unable to save the state because of database errors. If the module is reset you ...
  51. Alert subscription data source module was unable to save the state because of errors. If the module is reset you may see ...
  52. Alert subscription data source module was unable to save the state because of errors. If the module is reset you may see ...
  53. Alert: {0}Source: {1}Path: {2}Last modified by: {3}Last modified time: {4}Alert description: {5}Alert view link: {6}Notification ...
  54. Alerts can be suppressed using properties of the data type that caused the event data to be generated. Usually, these properties ...
  55. Alerts can be suppressed using properties of the data type that caused the event data to be generated. Usually, these properties ...
  56. Alerts from the following management groups cannot be displayed: {0} The management groups might be offline, or access may ...
  57. Alerts from the following management groups cannot be displayed: {0} The management groups might be offline, or access may ...
  58. All required server role services for IIS feature are not installed. In Windows Server 2008 use Server Manager to install ...
  59. All System Center "Service Desk" components have been successfully installed. In order to complete the install process, it ...
  60. All System Center "Service Desk" components have been successfully removed from the system. In order to complete the uninstall ...
  61. Also, consolidate events if the following event data parameters are identical. Enter each parameter as offset into the event ...
  62. An Account specified in the Run As Profile "%7" cannot be resolved. Specifically, the account is used in the Secure Reference ...
  63. An agent assignment rule for the domain "{0}" and management server "{1}" already exist. Proceeding to create this rule will ...
  64. An agent assignment rule for the domain "{0}" and management server "{1}" already exist. Proceeding to create this rule will ...
  65. An agent can report to multiple management groups. If you use Operations Manager integration with Active Directory Domain ...
  66. An agent pending action exists for this computer. This action must be rejected before approving the computer as a gateway. ...
  67. An agent pending action was created. Agent name: %1 Management server name: %2 Pending action type: %3 Pending action data: ...
  68. An agent pending action was created. Agent name: %1 Management server name: %2 Pending action type: %3 Pending action data: ...
  69. An agent was rejected. Current security settings do not allow the automatic insertion of agents. Change either the security ...
  70. An agent was rejected. Current security settings do not allow the automatic insertion of agents. Change either the security ...
  71. An alert couldn't be inserted to the database. This could have happened because of one of the following reasons: - Alert ...
  72. An alert couldn't be inserted to the database. This could have happened because of one of the following reasons: - Alert ...
  73. An application with the name "{0}" has already been added to this application group. To configure "{0}" at "{1}" for monitoring ...
  74. An attempt was made to load the component assembly '{0}' with an unmatched declared qualified name '{1}', the management ...
  75. An Audit Forwarder disconnected. Name: %1 DbId: %2 Value: %3 Reason: Collector disconnected the forwarder because it is busy. ...