System Center Operations Manager 2012

  1. Target/.$ expressions are not allowed in module references that have 'Target' property specified. Remove the 'Target' property ...
  2. Targeted class should a containment relationship to the service level target class in order for service level tracking to ...
  3. Test display name is invalid. One or more workflows were affected by this. Workflow name: %2 Instance name: %3 Instance ID: ...
  4. The "Dashboard Parameters" configuration for this web part are empty or invalid. Please select "Edit Web Part" and enter ...
  5. The "Enable SSL" selection and SSL configuration for the web site do not match. If you select "Enable SSL", the web site ...
  6. The %5 Event Log on computer '%6' appears to have "wrapped" while the Windows Event Log Provider was not active. This error ...
  7. The %5 Event Log on computer '%6' appears to have been cleared since it was last read. The Windows Event Log Provider may ...
  8. The %5 event log on computer '%7' is still corrupt. The Event Log Provider will attempt to recover by skipping over a possible ...
  9. The %5 Event Log on computer '%8' appears to have "wrapped" or been cleared while the Windows Event Log Provider was not ...
  10. The %5 Event Log on computer '%8' appears to have been cleared since it was last read. The Windows Event Log Provider may ...
  11. The %5 event log on computer '%8' is still corrupt. The Event Log Provider will attempt to recover by skipping over a possible ...
  12. The %5 log on computer '%6' appears to have been cleared while the Windows Event Log Provider was down. One or more workflows ...
  13. The %5 module encountered a %6 exception. The workflow "%2" has been unloaded. Module: %5 Location: %6 Exception type: %7 ...
  14. The %5 module encountered an invalid argument while running the "%2" workload. The module will not be unloaded. Module: %5 ...
  15. The %5 module encountered an unexpected exception. The workflow "%2" has been unloaded. Module: %5 Location: %6 Management ...
  16. The %5 module encountered an unexpected failure. The workflow "%2" has been unloaded. Module: %5 Location: %6 Result: %7 ...
  17. The %5 module encountered an unexpected null pointer exception. The workflow "%2" has been unloaded. Module: %5 Location: ...
  18. The %5 module failed to copy the file "%10" to the host %8:%9. Module: %5 Location: %6 Host: %8 Port: %9 Source file: %10 ...
  19. The %5 module failed to generate the "%8" XML result due to an internal error. Module: %5 Location: %6 Expected result: %8 ...
  20. The %5 module failed while making a remote command request to the host %8:%9. Module: %5 Location: %6 Host: %8 Port: %9 Command: ...
  21. The %5 property cannot be empty. One or more workflows were affected by this. Workflow name: %2 Instance name: %3 Instance ...
  22. The 'Hosted' flag for class type: ID={0} is set to '{1}'. This does not match the 'Hosted' flag for its non-abstract base ...
  23. The 'UnixAgents' folder is missing. Without this folder, Unix/Linux agents cannot be deployed and you have to manually install ...
  24. The .NET monitoring agent was unable to monitor one of the methods. The installed producer has returned a value of an unexpected ...
  25. The account for the UNIX/Linux Action Run As profile associated with the workflow "%2", running for instance "%3" with ID ...
  26. The account for the UNIX/Linux Agent Maintenance Run As profile associated with the workflow "%2", running for instance "%3" ...
  27. The Action Account may have been created during agent installation and therefore its password is not uploaded to the server. ...
  28. The additional error information can be found in the Windows Application Log. We apologize for any inconvenience caused by ...
  29. The Administration tree root node could not be found. Please import the System Center Operations Manager Library MP using ...
  30. The Administration tree root node could not be found. Please import the System Center Operations Manager Library MP using ...
  31. The agent assignment rule for domain %5 and ManagementServer %6 has recovered from previous error condition. The SCPs and ...
  32. The Agent Management Operation %1 failed for remote computer %2. Install account: %3 Error Code: %4 Error Description: %5 ...
  33. The Agent Management Operation %1 failed for remote computer %2. Install account: %3 Error Code: %4 Error Description: %5 ...
  34. The Agent Management operation failed, the Operations Manager Server failed to retrieve host name %2 from a host database. ...
  35. The agent management task received a shutdown request while processing the requested operation for managed computer "%2". ...
  36. The agent management task took %6 seconds and timed out while processing the requested operation for managed computer "%2". ...
  37. The agent on the remote computer failed to uninstall. If the agent has already been uninstalled you can select 'Delete' instead ...
  38. The agents will automatically report to the other management servers in the same management group if their primary management ...
  39. The agents you have selected report to different management servers. Agent uninstall task can only be submitted to one management ...
  40. The APM service will add functions from the specified namespace or class to the list of monitored functions. Namespace and ...
  41. The APM service will add this method to the list of exception handlers. The method name is case sensitive. The method name ...
  42. The APM service will add this method to the list of monitored methods. The method name is case sensitive. The method name ...
  43. The Application Diagnostics database has invalid schema version. Please, run the Configuration Utility and configure Application ...
  44. The Application Diagnostics database has invalid version. Please, run the Configuration Utility and configure Application ...
  45. The Application Monitoring Operator profile includes a set of privileges designed for users that need access to Application ...
  46. The assembly was loaded, but the declared assembly name is not the same as the actual assembly name. Declared Name: {0} Actual ...
  47. The attribute cannot be directly added to the selected type because it belongs to a Sealed Management Pack. In order to add ...
  48. The attribute cannot be directly added to the selected type because it belongs to a Sealed Management Pack. In order to add ...
  49. The authentication data in parameter {0} contains an illegal character at position {1}. Authentication data can only contain ...
  50. The availability monitoring of entity "%2" has been disabled. Entity Id: %1 Management Group Name: %3 Management Group Id: ...
  51. The availability of one or more members of the pool has changed. The ownership for all managed objects assigned to the pool ...
  52. The Backwards Compatibility mapper module was not able to start because discovery has not fully completed for this Health ...
  53. The baseline could not be paused. This could happen for the following reasons: - The baseline was already paused - The target ...
  54. The baseline could not be reset. This could happen for the following reasons: - There was no baseline to reset - The target ...
  55. The baseline could not be resumed. This could happen for the following reasons: - The baseline was already running - The ...
  56. The BIOS settings on the monitored server prevent the accurate time measurement. The event timing may be invalid. Please, ...
  57. The Browser Helper Object is not installed to properly launch the Web Recorder Bar. Please, manually enable that bar before ...
  58. The cabinet file '[2]' required for this installation is corrupt and cannot be used. This could indicate a network error, ...
  59. The cabinet file 2 required for this installation is corrupt and cannot be used. This could indicate a network error, an ...
  60. The call produced inconsistent results. The data on the client does not match the data returned from the server. The most ...
  61. The callback method %5 failed with exception "%6" in the module %7. Workflow: %2 Instance: %3 Instance ID: %4 Management ...
  62. The certificate Common Name (CN) does not match. Please resolve the issue, and then run the Unix/Linux Discovery Wizard again. ...
  63. The certificate specified in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Machine ...
  64. The certificate specified in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Machine ...
  65. The certificate specified in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Machine ...
  66. The certificate used for mutual authentication is expiring on %1 GMT. If this certificate is not updated by this time, this ...
  67. The cmdlet cannot access the database. Ensure that you have connectivity to the System Center Data Access service and to ...
  68. The cmdlet cannot find the binary files that are required to complete this action. Ensure that you are running the cmdlet ...
  69. The cmdlet cannot identify the required database properties. Ensure that the System Center Data Access service is running ...
  70. The COM+ application "[2]" is configured to run as an NT service; this requires COM+ 1.5 or later on the system. Since your ...
  71. The computer group {0} was not found. Please remove the targeted computer group and select a new scoping group, or leave ...
  72. The computer running SQL Server must have the SQL Server Full-Text Search component installed. Please install this component ...
  73. The connector was unable to obtain subject or issuer name from remote certificate structure and converts it to a null-terminated ...
  74. The connector with the given connector id either in the incorrect initialized state for the given operation or does not exist. ...
  75. The console task parameters are not formatted correctly. The parameters must be delimited by either spaces or by quotes. ...