System Center Service Manager 2012

  1. The object returned from the provider as type: {0} is not a supported type. Make sure to always use the IDataCommandContext ...
  2. The object you are creating or updating needs to be stored in an unsealed management pack. Select an existing unsealed management ...
  3. 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 ...
  4. The Operations Manager Web console URL is not configured. Contact your administrator to configure it as part of Incident ...
  5. The output of every prompt should be mapped to a property, assigned to a relationship, or consumed by a subsequent prompt. ...
  6. The override specified is not valid. The override TypeID={0} does not refer to a valid module or monitor type in this management ...
  7. The parameter is bound to an Activity property. Any changes to this will invalidate the Binding. Do you want to proceed? ...
  8. The product key entered is Evaluation Version. Upgrade from Licensed to Evaluation version is unsupported. Please enter a ...
  9. The property with path '{0}' is not valid in the context of an outrigger. The only allowed property types are 'string' and ...
  10. The propetry value type '{0}' is not supported. Only primitive types, strings or arrays of primitive types can be used as ...
  11. The public key token is null for the management pack loaded from file '{0}' and it does not match the expected public key ...
  12. The public key token KeyToken={0} of the management pack loaded from file '{1}' does not match the expected public key token ...
  13. The QualifiedName attribute value is not valid. Element {0} does not specify a valid value for the assembly qualified name ...
  14. The query resulted in %1 rows. This may cause high memory consumption, and affect server performance. Consider using buffered ...
  15. The queue could not be deleted. Possible reasons: 1. There could be other management pack groups or queues referring to this ...
  16. The recovery status notification was not set up correctly. The notification for recovery job with ID "%1" will not be processed. ...
  17. The reference to the element with ID {0} is incorrect. This element is of class {1} which does not have the accessibility ...
  18. The relationship source role class ID specified in the discovery data item is not valid. Relationship source role class ID: ...
  19. The relationship source specified in the discovery data item is not valid. Relationship source ID: {0} Rule ID: {1} Instance: ...
  20. The relationship target specified in the discovery data item is not valid. Relationship target ID: {0} Rule ID: {1} Instance: ...
  21. The remote SQL Server is not accessible. Make sure that Windows Firewall on the remote SQL Server has the appropriate ports ...
  22. The report deployment process is in progress. To determine when management pack deployment is complete, see the procedure ...
  23. The requested ManagementPackElement Type={0}, ID={1} in management pack {2} is not accessible outside of this management ...
  24. The requested ManagementPackElement Type={0}, ID={1} was found in management pack {2} but this management pack is not listed ...
  25. The requested tier does not allow connector initiated connections. Connect to a different tier or update the tier to allow ...
  26. The retrieved allow list value could not be parsed as XML. Use the Reset-SCSMAllowList command to restore a default value. ...
  27. The richtext value specified for property {0} is too long ({1} characters). Specify a value between {2} and {3} characters ...
  28. The root connector received an exception from the System Center Management Configuration service on ManagementPackRequest: ...
  29. The root connector received an exception from the System Center Management Configuration service on StateSyncRequest: %1 ...
  30. The root connector received an exception from the System Center Management Configuration service on StateSyncRequest: %1 ...
  31. The root management service is running but reported limited functionality soon after {0}. The specific reason code is {1} ...
  32. The root management service's heartbeat stopped soon after {0}. This adversely affects all availability calculation for the ...
  33. The rule composition is not valid. {0} DataSource modules specified for this rule, but the ConditionDetection module {1}, ...
  34. The rule name is not valid. Enter a rule name that has between one and 256 characters. A rule name cannot include spaces, ...
  35. The rule starts the workflow when one or more database items (such as incidents or change requests) meet a specific set of ...
  36. The Run As account cannot be deleted because it is associated with a Run As profile. Remove the association before proceeding. ...
  37. The Run As account cannot be validated. This may be because the domain controller is unavailable or the account provided ...
  38. The Runbook "%1" cannot be found in SCSM or its contract has changed. As a result automated activity "%2" cannot complete. ...
  39. The Runbook "%1" could not be invoked successfully for automated activity "%2". Possible reasons can be that permissions ...
  40. The runbook associated with this runbook activity template, {0}, is in an invalid state. Select another runbook or ensure ...
  41. The runbook associated with this runbook activity template, {0}, was not found. Select another runbook or ensure that the ...
  42. The script parameter name is not valid. The name should be alphanumeric and can contain "_" character only. Script parameter ...
  43. The secure data to management service reference cannot be inserted. The most common reason for this is the management service ...
  44. The seed class {0} is not valid for projection component with Alias {1} specified by TypeMapping. It must be equal to or ...
  45. The seed class {0} is not valid for projection {1} specified by TypeMapping. It must be equal to or derived from class {2}. ...
  46. The selected class is in an unsealed Management pack. To target the form to this class, either seal the class's management ...
  47. The selected item is of a class that is defined in another unsealed management pack. To add this item, try creating the group ...
  48. The SelectedDates collection can be changed only in a multiple selection mode. Use the SelectedDate in a single selection ...
  49. The selection of management packs on this page is used only as a filter for the subsequent wizard pages and is not saved ...
  50. The Self-Service Portal can access the Service Manager database under the Local System account, if installed on the same ...
  51. The Self-Service Portal is a Web-based solution that allows end users to open and track service requests. This component ...
  52. The Service Manager Administrators user role is created at setup time and cannot be deleted. This role must contain one or ...
  53. The Service Manager console is installed. You will be prompted for a Service Manager server to connect to when the console ...
  54. The Service Manager data warehouse management server is installed and the data warehouse databases have been created. You ...
  55. The Service Manager data warehouse SQL Reporting Services server is currently unavailable. You will be unable to execute ...
  56. The Service Manager installation was registered successfully with the Data Warehouse installation. Data Warehouse Server: ...
  57. The Service Manager installation was unregistered successfully from the Data Warehouse installation. Data Warehouse Server: ...
  58. The Service Manager management server, the data warehouse and the self-service portal can only be installed on a Windows ...
  59. The Service Manager Service Request Analysts user role is created at setup time, is globally scoped and cannot be deleted. ...
  60. The Service Manager services can run under the Local System account or under a domain user or service account that has been ...
  61. The Service Manager workflows run under this account. Setup will make the domain account a member of the local Users security ...
  62. The Service Offering created here is visible in the portal to the users if they have access to the catalog item groups configured ...
  63. The setting for maximum number of e-mail messages to be processed per cycle cannot be 0. Correct your inbound e-mail settings. ...
  64. The SortDescriptions added are not valid. The probable solutions are to set the CanUserSort on the Column to false, or to ...
  65. The specified element reference ({0}) was found in the management pack, but object Type={1} cannot be cast to requested type ...
  66. The specified RunAsAccount, {0}, refers to user account {1}\{2} and does not match the supplied username of {3}\{4}. The ...
  67. The SQL Server {0} is not running version SQL Server 2008 R2 or SQL Server 2012. Please update it to the newest version and ...
  68. The SQL Server {0} is not running version SQL Server 2008 SP2 or SQL Server 2008 R2. Please update it to the newest version ...
  69. The start time for maintenance mode cannot be in the future. Scheduling of maintenance mode is supported for immediate scheduling, ...
  70. The string supplied for argument {0} is invalid. The string must contain at least 1 character that is not a space, tab, or ...
  71. The string value specified for property {0} could not be validated. The value {1} does not conform to the regular expression ...
  72. The string value specified for property {0} is too short ({1} characters). Specify a value between {2} and {3} characters ...
  73. The string value specified for property {0} is too short ({1} characters). Specify a value of at least {2} characters in ...
  74. The string value {0} specified for property {1} could not be parsed as a GUID. Enter a string in the format "#-#-#-#-#", ...
  75. The SubjectList property of the Microsoft.SystemCenter.DataWarehouse.SCCMDataSource instance must contain a comma-separated ...