System Center Operations Manager 2007

  1. The installer must restart your system before configuration of 2 can continue. Click Yes to restart now or No if you plan ...
  2. The instrumentation of function '%1' failed. This function will not be monitored. "%2", code: %3 raise in %4, catch in %5 ...
  3. The instrumentation of function '%1' failed. This function will not be monitored. "%2", code: %3 raise in %4, catch in %5 ...
  4. The item you are trying to delete cannot be deleted because another object references it. The object must be deleted before ...
  5. The keypair that the health service uses to receive secure messages is expiring on %1. The health service will be recycled ...
  6. The keypair that the health service uses to receive secure messages is expiring on %1. The health service will be recycled ...
  7. The last timed-out query has succeeded. Subscription ID: %5 Service name: %6 Deployment slot: %7 Role name: %8 Storage account: ...
  8. The LDAP query returned no results. This may be expected, or may indicate a bad configuration Domain: %5 Query: %6 One or ...
  9. The LDAP query returned no results. This may be expected, or may indicate a bad configuration Domain: %5 Query: %6 One or ...
  10. The Licensing Wizard was unable to successfuly apply the licensing because the resulting number of licenses would exceed ...
  11. The limit for the total number of collected functions in the event has been reached. Some functions may not be collected. ...
  12. The Log file folder location does not contain enough disk space for a database of this size. The required disk space for ...
  13. The Management Group %1 failed to start. The error message is %2(%3). A previous message with more detail may have been logged. ...
  14. The Management Group %1 failed to start. The error message is %2(%3). A previous message with more detail may have been logged. ...
  15. The Management Group %1 found in Active Directory has not been approved on this Health Service and will not be started. To ...
  16. The Management Group %1 found in Active Directory has not been approved on this Health Service and will not be started. To ...
  17. The Management Group %1 has no configured parents and most monitoring tasks cannot be performed. This can happen if a management ...
  18. The Management Group %1 has no configured parents and most monitoring tasks cannot be performed. This can happen if a management ...
  19. The Management Group %1 which was originally discovered via Active Directory has been removed from Active Directory and will ...
  20. The Management Group %1 which was originally discovered via Active Directory has been removed from Active Directory and will ...
  21. The management group cannot be upgraded when Operations Manager 2007 R2 features are present. Upgrade the features to System ...
  22. The management group name cannot contain a leading or trailing space, and it cannot contain the following characters: ( ) ...
  23. The management group name cannot contain the following characters:, ( ) ^ ~ : ; . ! ? " , ' ` @ # % \ / + = $ | < > { }, ...
  24. The management group provided to the Reconnect call does not match the management group this object was originally connected ...
  25. The management pack was retrieved from the database and cannot be reimported. In order to import this management pack, please ...
  26. The management server could not be deleted because it is hosting the RMS Emulator role. At the Operations Manager Shell prompt, ...
  27. The management server could not be deleted because some devices are reporting to it. Reassign all devices to a different ...
  28. The Management server has been uninstalled. To remove references to this Management server from the operational databases, ...
  29. The Management Server name is either blank or contains special characters. The Management Server name should not contain ...
  30. The Management Server uses the Management Server Action Account to gather operational data from providers, to run responses, ...
  31. The Management Server uses the SDK Account to log on to the SC database server. It is recommended that you do not use the ...
  32. The Management Server you specify here will be used to collect and forward error reports and Customer Experience Improvement ...
  33. The Microsoft .NET Framework 3.0 (formerly known as WinFX), is the new managed code programming model for Windows. This application ...
  34. The Microsoft Management Pack Catalog Web Service cannot be contacted at this time. There is either a problem with your Internet ...
  35. The Microsoft Operations Manager Computation Module could not convert the received value to the requested type. Property ...
  36. The Microsoft Operations Manager Computation Module could not initialize properly. The passed in expression could be invalid. ...
  37. The Microsoft Operations Manager Computation Module could not parse a regular expression provided for filtering. Expression: ...
  38. The Microsoft Operations Manager Computation Module could not parse a wildcard expression provided for filtering. Expression: ...
  39. The Microsoft Operations Manager Computation Module failed to evaluate the date time expression because the passed in property ...
  40. The Microsoft Operations Manager Computation Module failed to process a data item and dropped it. Error: %5 One or more workflows ...
  41. The Microsoft Operations Manager Computation Module failed to query the delivered item, item was dropped. Property Expression: ...
  42. The Microsoft Operations Manager Computation Module failed with an arithmetic division by zero error. Operation Summary: ...
  43. The Microsoft Operations Manager Computation Module failed with an arithmetic overflow error. Operation Summary: %5 Error: ...
  44. The Microsoft Operations Manager Computation Module found an inexisting property xpath query for the processing data item. ...
  45. The Microsoft Operations Manager Computation Module has some invalid configuration. Config Context: %5 Error: %6 One or more ...
  46. The Microsoft Operations Manager Condolidator Module can not be configured with weekly schedule and have consolidated properties ...
  47. The Microsoft Operations Manager Condolidator Module could not initialize properly. Error: %5 One or more workflows were ...
  48. The Microsoft Operations Manager Condolidator Module did not recognize the scheduling option type, make sure to specify Generic ...
  49. The Microsoft Operations Manager Condolidator Module ecountered an internal fatal error and must be unloaded. Error: %5 One ...
  50. The Microsoft Operations Manager Condolidator Module failed during the garbage collection phase. Error: %5 One or more workflows ...
  51. The Microsoft Operations Manager Condolidator Module failed to initialize because in a single day window, the start hour ...
  52. The Microsoft Operations Manager Condolidator Module failed to initialize because on a multiple days interval, the start ...
  53. The Microsoft Operations Manager Condolidator Module failed to initialize because some "hour in the day" could not be parsed ...
  54. The Microsoft Operations Manager Condolidator Module failed to initialize because some schedule window has a negative start. ...
  55. The Microsoft Operations Manager Condolidator Module failed to initialize because some schedule window has a non-positive ...
  56. The Microsoft Operations Manager Condolidator Module failed to initialize because some schedule windows overlap with each ...
  57. The Microsoft Operations Manager Condolidator Module failed to initialize because some value in its configuration is too ...
  58. The Microsoft Operations Manager Condolidator Module failed to initialize because some window has no day of the week set. ...
  59. The Microsoft Operations Manager Condolidator Module failed to initialize because the exclude date interval failed to parse ...
  60. The Microsoft Operations Manager Condolidator Module failed to initialize because the first schedule window is after the ...
  61. The Microsoft Operations Manager Condolidator Module failed to initialize because the last and first schedule windows overlap. ...
  62. The Microsoft Operations Manager Condolidator Module failed to initialize because the maximum number of schedule windows ...
  63. The Microsoft Operations Manager Condolidator Module failed to initialize because the number of excluded dates is greater ...
  64. The Microsoft Operations Manager Condolidator Module failed to initialize because the recurring interval can not be greater ...
  65. The Microsoft Operations Manager Condolidator Module failed to initialize because the specified compare count is less than ...
  66. The Microsoft Operations Manager Condolidator Module failed to initialize because the specified schedule interval is greater ...
  67. The Microsoft Operations Manager Condolidator Module failed to initialize because the specified schedule interval number ...
  68. The Microsoft Operations Manager Condolidator Module failed to initialize because the specified schedule is not recognized ...
  69. The Microsoft Operations Manager Condolidator Module failed to initialize because there is no window specified. One or more ...
  70. The Microsoft Operations Manager Condolidator Module failed to initialize due to an out of range configuration. Setting: ...
  71. The Microsoft Operations Manager Condolidator Module failed to initialize due to invalid configuration. Invalid Configuration: ...
  72. The Microsoft Operations Manager Condolidator Module failed to initialize due to invalid configuration. Rejected Item: %5 ...
  73. The Microsoft Operations Manager Condolidator Module failed to process a delivered item, item was dropped. Function: %5 Error: ...
  74. The Microsoft Operations Manager Condolidator Module failed to save the state after processing and might loose data. Error: ...
  75. The Microsoft Operations Manager Condolidator Module has some invalid configuration. Config Context: %5 Error: %6 One or ...