System Center Service Manager 2012 R2

  1. The DataWarehouseEnum being referred to is not found, make sure the MP that the enum is defined in has been deployed in the ...
  2. The diagnostic status notification was not setup correctly. The notification for diagnostic job with ID "%1" will not be ...
  3. The dimension property targeted by the ManagementPack element was not found. The property must exist in the target entity ...
  4. The dimension targeted by the named calculation was not found. Dimension : {0}. The deployment of the cube may still succeed ...
  5. The dimension targeted by the user-defined measure was not found. Dimension : {0}. The deployment of the cube may still succeed ...
  6. The Encryption Key Backup or Restore Wizard is unable to complete the backup operation at this time. Please see additional ...
  7. The Encryption Key Backup or Restore Wizard is unable to complete the restore operation at this time. Please see additional ...
  8. The encryption keys in the registry were either not valid or not present. The System Center Data Access service will not ...
  9. The Enforced flag cannot be set to 'true' for Override in a sealed management pack. This value is available only for unsealed ...
  10. The file name of the management pack must match its identity (specified in the Manifest section). MP identity: {0} File path: ...
  11. The following dimension changes require cube schema revision. If other cubes depend on these dimensions, then they will be ...
  12. The following management packs are invalid for the Operations Manager connector configuration: {0} Valid management pack ...
  13. The following resource files are referenced by management packs in the bundle but have not been added through the -Resources ...
  14. The following workflow rules cannot be compiled. The workflow sources (*.xoml,*.xomlx, *.cs) of the rules are missing. {0} ...
  15. The For Each Loop activity takes as an input an array (collection) of objects and repeats the set of activities within the ...
  16. The form base is not valid. Form {0} specifies both an assembly and a base form. It can only specify one of the two attributes. ...
  17. The group could not be deleted. Possible reasons: 1. There could be other management pack elements referring to this group. ...
  18. The group expansion workflow for connector %1 has ended. %2 groups were processed successfully. %3 users were processed successfully. ...
  19. The group name must meet the following condition: Must be Unique, only alphabet letters and numbers, and contain no spaces! ...
  20. The group name {0} is not valid. Valid groups (classes deriving from Microsoft.SystemCenter.ConfigItemGroup) include: {1} ...
  21. The group object could not be deleted because it is either not contained in the management pack or has been otherwise modified ...
  22. The Hosted flag for class {0} is set to {1}. This does not match the Hosted flag for its non-abstract base class ID={2} which ...
  23. The hosting relationship ID={0} specified a target class ID={0} in a different management pack. All hosting relationship ...
  24. The IAsyncResult value was not valid. Either it was not from the proper Begin method or from a Begin method on a different ...
  25. The identifier {0} used with type {1} is not valid. There is already another element defined with the same identifier in ...
  26. The Implied Config Item Custodian profile includes a set of privileges designed to enable the config item's custodian to ...
  27. The Implied Incident Affected User profile includes a set of privileges designed to enable the incident's affected user to ...
  28. The Implied Primary Computer User profile includes a set of privileges designed to enable the computer's primary user to ...
  29. The Implied Reviewer profile includes a set of privileges designed to enable the reviewer to vote and comment. Explicit user ...
  30. The Implied User Preference profile includes a set of privileges designed to enable the user to read and update his/her preference. ...
  31. The inbound e-mail processor cannot process EML file %1. The attempt to move the bad file to %2 failed. Exception message: ...
  32. The inbound e-mail processor failed to add file attachments for file %1. An incident has been created without the full e-mail ...
  33. The inbound e-mail processor has created an e-mail incident for %1. However, we encountered problems while trying to delete ...
  34. The inbound e-mail processor has received an e-mail incident originating from an e-mail address not found among database ...
  35. The installed version of the Service Manager console cannot be upgraded to Microsoft System Center 2012 R2 Service Manager. ...
  36. The Intermediate Measure Group was not found or is invalid : {0}. The deployment of the cube may still succeed because not ...
  37. The Length attribute can only be specified for 'string' and 'decimal' data types. The value '{0}' cannot be specified for ...
  38. The management group provided to the Reconnect call does not match the management group this object was originally connected ...
  39. The management group provided was either missing or not valid. If you are using functionality specific to a product, ensure ...
  40. The management pack could not be loaded correctly from the database. Author level security validation could not proceed. ...
  41. The management pack could not be loaded. It is possible that a management pack file with the same name, public key and token ...
  42. The management pack schema version (SchemaVersion attribute) is not valid. The only accepted values are '1.0' and '1.1'. ...
  43. The management pack synchronization process has not completed. You will be unable to view reports or administer the Data ...
  44. The management pack to which this class belongs has not been deployed yet. Try to resubmit the data once the ManagementPack ...
  45. The management pack was retrieved from the database and cannot be reimported. In order to import this management pack, use ...
  46. The management pack you are attempting to export contains image or assembly resources. Do you want to create a management ...
  47. The management pack you are attempting to import contains one or more missing image or assembly resources. Please create ...
  48. The management pack {0} must contain a class that derives from Microsoft.SystemCenter.DataWarehouse.DataSource class. It ...
  49. The management packs that are new to Service Manager are marked as such and the configuration items from Operations Manager ...
  50. The management server which is currently designated to run the workflows must be upgraded before this management server can ...
  51. The management service was unable to log on the action account. Check the event log on the root management server for more ...
  52. The many-to-many dimension is not unique. A cube dimension can only have one many-to-many relationship for a targeted measure ...
  53. The member monitor specified ({0}) is not valid. A dependency monitor can only have a UnitMonitor or AggregateMonitor type ...
  54. The member monitor specified is not valid. Target class mismatch. The member monitor ID={0} has target {1}. This target is ...
  55. The Microsoft System Center 2012 R2 Service Manager Authoring Tool enables customizing and extending Service Manager functionality ...
  56. The MinLength attribute cannot be set on a non-key attribute. This attribute can only be set on properties where Key='true'. ...
  57. The mode in which the authorization manager object is opened incorrect. It should be opened for "create" and/or "write" for ...
  58. The mode in which the authorization manager object is opened incorrect. It should be opened for "read" for you to call this ...
  59. The mode in which the authorization manager object is opened incorrect. It should be opened only for "read" or for "write" ...
  60. The module reference target ({0}) cannot be the same as the workflow target ({1}). Remove the target specification against ...
  61. The module type used in this recovery ({0}) is not valid. Only module types that accept one input data type can be used here. ...
  62. The MOM Administrator user role cannot have multiple users assigned to it. It must have exactly one user assigned to it. ...
  63. The MP version is null for the management pack loaded from file '{0}' and it does not match the expected public key token ...
  64. The MP version Version={0} of the management pack loaded from file '{1}' does not match the expected MP version Version={2}]. ...
  65. The named calculation is not unique. The property defined already exists in the entity or another named calculation with ...
  66. The notification endpoint is either missing a PrimaryServer or the DeviceEnumerationIntervalSeconds property. One of these ...
  67. The object could not be added to the combination class because the parent is not of the proper class as specified by the ...
  68. The object returned from the provider as type: {0} is not a supported data object collection. Make sure to always use the ...
  69. The object returned from the provider as type: {0} is not a supported type. Make sure to always use the IDataCommandContext ...
  70. The object you are creating or updating needs to be stored in an unsealed management pack. Select an existing unsealed management ...
  71. The operation {0} in the profile {1} is already restricted to the same type or its base type. Hence there is no need to restrict ...
  72. The Operations Manager Web console URL is not configured. Contact your administrator to configure it as part of Incident ...
  73. The output of every prompt should be mapped to a property, assigned to a relationship, or consumed by a subsequent prompt. ...
  74. The override specified is not valid. The override TypeID={0} does not refer to a valid module or monitor type in this management ...
  75. The parameter is bound to an Activity property. Any changes to this will invalidate the Binding. Do you want to proceed? ...