System Center Operations Manager 2007

  1. CrashListenerPA module encountered an error while processing '%5' for parameter '%6' because the error report has invalid ...
  2. CrashListenerPA module encountered an error while processing '%5' for parameter '%6' because the error report has invalid ...
  3. CrashListenerPA module encountered an error while processing '%5'. Workflow name: %2 Instance name: %3 Instance ID: %4 Management ...
  4. CrashListenerPA module encountered an error while processing '%5'. Workflow name: %2 Instance name: %3 Instance ID: %4 Management ...
  5. CrashListenerPA module encountered an error while querying AD for '%5'. '%6' Workflow name: %2 Instance name: %3 Instance ...
  6. CrashListenerPA module encountered an error while querying AD for '%5'. '%6' Workflow name: %2 Instance name: %3 Instance ...
  7. CrashListenerPA module encountered Hits and Cabs mismatch for bucket '%5', hits = '%6', cabs = '%7'. Workflow name: %2 Instance ...
  8. CrashListenerPA module encountered Hits and Cabs mismatch for bucket '%5', hits = '%6', cabs = '%7'. Workflow name: %2 Instance ...
  9. CrashListenerPA module finds fileShare is not reachable/accessible or validation failed. Workflow name: %2 Instance name: ...
  10. CrashListenerPA module finds fileShare is not reachable/accessible or validation failed. Workflow name: %2 Instance name: ...
  11. CrashListenerPA module has received an unexpected cab '%5' from '%6'. Workflow name: %2 Instance name: %3 Instance ID: %4 ...
  12. CrashListenerPA module has received an unexpected cab '%5' from '%6'. Workflow name: %2 Instance name: %3 Instance ID: %4 ...
  13. Create Registry Key %6 failed with error '%7' Signature ID: %5 Workflow name: %2 Instance name: %3 Instance ID: %4 Management ...
  14. Create Registry Key %6 failed with error '%7' Signature ID: %5 Workflow name: %2 Instance name: %3 Instance ID: %4 Management ...
  15. Creation of module with CLSID "%5" failed with error "%6" in rule "%2" running for instance "%3" with id:"%4" in management ...
  16. Creation of module with CLSID "%5" failed with error "%6" in rule "%2" running for instance "%3" with id:"%4" in management ...
  17. Credentials from less-secure Run As accounts are distributed automatically. Credentials from more-secure Run As accounts ...
  18. Custom action '[2]' has caused an unhandled exception and has been stopped. This may be the result of an internal error in ...
  19. Custom alert fields are used in advanced monitoring scenarios to collect additional information about a problem which can ...
  20. Dashboard cache refresh interval' must be a positive integer and can't be lower than 60 seconds and higher than 30 minutes ...
  21. Data item returned no information for parameter '%5' This usually indicates that the query is incorrect. One or more workflows ...
  22. Data item returned no information for parameter '%5' This usually indicates that the query is incorrect. One or more workflows ...
  23. Data synchronization process successfully obtained state information from the Data Warehouse One or more workflows were affected ...
  24. Data synchronization process successfully obtained state information from the Data Warehouse One or more workflows were affected ...
  25. Data synchronization process successfully written state information to the Data Warehouse database One or more workflows ...
  26. Data synchronization process successfully written state information to the Data Warehouse database One or more workflows ...
  27. Data Warehouse component successfully deployed One or more workflows were affected by this. Workflow name: %2 Instance name: ...
  28. Data Warehouse component successfully deployed One or more workflows were affected by this. Workflow name: %2 Instance name: ...
  29. Data Warehouse object and relationship enumeration (discovery) succeeded One or more workflows were affected by this. Workflow ...
  30. Data Warehouse object and relationship enumeration (discovery) succeeded One or more workflows were affected by this. Workflow ...
  31. Data Warehouse successfully enumerated components to be deployed One or more workflows were affected by this. Workflow name: ...
  32. Data Warehouse successfully enumerated components to be deployed One or more workflows were affected by this. Workflow name: ...
  33. Data Warehouse synchronization data generation operation succeeded One or more workflows were affected by this. Workflow ...
  34. Data Warehouse synchronization data generation operation succeeded One or more workflows were affected by this. Workflow ...
  35. Data was dropped due to too much outstanding data in rule "%2" running for instance "%3" with id:"%4" in management group ...
  36. Data was dropped due to too much outstanding data in rule "%2" running for instance "%3" with id:"%4" in management group ...
  37. Data was found in the output, but has been dropped because the Event Policy for the process started at %5 has detected errors. ...
  38. Data was found in the output, but has been dropped because the Event Policy for the process started at %5 has detected errors. ...
  39. Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations.%rException ...
  40. Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations.%rException ...
  41. Data writer successfully performed data maintenance operations. One or more workflows were affected by this. Workflow name: ...
  42. Database files with the same name already exist. Please remove the conflicting files listed below or select another location.{1}{0} ...
  43. Database queue length has dropped below warning thresholds. New Forwarder connections will now be permitted. Current queue ...
  44. Database queue length has dropped below warning thresholds. New Forwarder connections will now be permitted. Current queue ...
  45. Database queue threshold exceeded. New client connections will not be allowed until queue length decreases below the threshold, ...
  46. Database queue threshold exceeded. New client connections will not be allowed until queue length decreases below the threshold, ...
  47. Database queue threshold exceeded. One or more clients might be disconnected. New connections will not be allowed until queue ...
  48. Database queue threshold exceeded. One or more clients might be disconnected. New connections will not be allowed until queue ...
  49. Database: 2]. MergeDatabase: Unable to write errors to Error table. Could be due to a non-nullable column in a predefined ...
  50. Datasource ModuleType {0} is declared as a composite module type and needs to be composed from at least one DataSourceModule ...
  51. Datasource ModuleType {0} is declared as a composite module type and needs to be composed from atleast one DataSourceModule ...
  52. Datatype mismatch in ModuleType composition. InputType {0} of referenced leaf ConditionModule (Type={1},ID={2}) does not ...
  53. Datatype mismatch in ModuleType composition. OutputType {0} of referenced module (Type={1}, ID={2}) does not match expected ...
  54. Datatype mismatch in ModuleType composition. OutputType {0} of referenced module {1} does not match expected data type {2} ...
  55. Datatype mismatch in ModuleType composition. Referenced leaf ConditionModule (Type={1},ID={2}) has more input types than ...
  56. Datatype mismatch in ModuleType composition. Referenced leaf WriteAction Module (Type={1},ID={2}) does not match up with ...
  57. Datatype mismatch in ModuleType composition. Referenced WriteAction Module (Type={0}, ID={1}) has an output datatype ({2}) ...
  58. DataType mismatch. Condition module type {1} outputs {2} data which is not compatible with the input datatype {3} of ProbeActionModule ...
  59. DataType mismatch. Condition module type {1} outputs {2} data which is not compatible with the input datatype {3} of WriteActionModule ...
  60. DB Update Interval received by LearningModule is zero. Module is being unloaded. One or more workflows were affected by this. ...
  61. DB Update Interval received by LearningModule is zero. Module is being unloaded. One or more workflows were affected by this. ...
  62. Default assembly cannot be found. Reason per assemblies: %1 Monitoring will not start. Please be sure that the Microsoft ...
  63. Deleting a Management Pack might affect the scoping of some user roles. Are you sure you want to delete {0} version {1}? ...
  64. Deleting this aggregate monitor will also delete any related child monitors. Are you sure you want to delete this aggregate ...
  65. Deleting this aggregate monitor will also delete any related child monitors. Are you sure you want to delete this aggregate ...
  66. Dependency monitor depends on a monitor of a related type. Select a relationship type and one of the monitors of the related ...
  67. Dependency rollup monitor can not be created because the target does not have relationships where the target is the source ...
  68. depends on management packs that are not imported but are available in the online catalog. Click Resolve to add the dependent ...
  69. Deployment operation validation failed. Component alrady installed. Operation: '%s'; Component type: '%s'; Component id: ...
  70. Deployment operation validation failed. Component does not exist. Operation: '%s'; Component type: '%s'; Component id: '%s'; ...
  71. Deployment operation validation failed. Component does not support upgrade from previous version. Operation: '%s'; Component ...
  72. Deployment operation validation failed. Configuration xml provided for operation that does not require configuration. Operation: ...
  73. Deployment operation validation failed. Dataset script target dataset type does not match the target specified. Operation: ...
  74. Deployment operation validation failed. Management pack version does not exist. Operation: '%s'; Component type: '%s'; Component ...
  75. Deployment operation validation failed. Target database or dataset does not exist. Operation: '%s'; Component type: '%s'; ...