System Center Service Manager 2012 R2

  1. Specify the alphanumeric prefix that will be used in the ID of any new incidents. Existing incidents will not be changed. ...
  2. Specify the calendar and metric you want to use for this service level objective. In addition, specify the target and warning ...
  3. Specify the name and port number for the SharePoint Web site. Specify the server and database that will be used to store ...
  4. Specify the name of the server that hosts the instance of SQL Server 2008 R2 or SQL Server 2012 that contains the Service ...
  5. Specify the prefix that will be used in the ID of any new change requests. Existing change requests will not be changed. ...
  6. Specify the prefix that will be used in the ID of any new knowledge articles. Existing knowledge articles will not be changed. ...
  7. Specify the prefix that will be used in the ID of any new release records. Existing release records will not be changed. ...
  8. Specify the prefix that will be used in the ID of any new service requests. Existing service requests will not be changed. ...
  9. Specify the starting and ending values for events that will trigger a workflow. You can choose to specify only a starting ...
  10. Specify the time in which an incident must be resolved, based on its priority. For example, use this table to record your ...
  11. Subscription module encountered errors while validating subscription as user associated with subscription could not be found. ...
  12. Successfully completed the job. JobName = %1; JobCategory = %2; BatchId = %3; BatchCompletionTime = %4; TotalProcessingTime ...
  13. Successfully created System Center Configuration Manager Connector "%1" to server "%2". The connector was created by user ...
  14. Successfully created System Center Orchestrator Connector "%1". The webservice URL is "%2" and synced folder is "%3". The ...
  15. Successfully created Virtual Machine Manager Connector "%1". The server is "%2". The connector was created by user account ...
  16. Successfully deleted System Center Orchestrator Connector "%1". The connector was deleted by user account %2. Any runbooks ...
  17. System Center Data Access Service and/or System Center Management is unresponsive because Authorization Manager is unable ...
  18. Target class {0} for Recovery {1} does not derive from Target class {2} of the diagnostic ({3}) that this recovery is assigned ...
  19. Target class {0} for Recovery {1} does not derive from Target class {2} of the monitor ({3}) that this recovery is assigned ...
  20. Target entity already bound to another membership through hosting. Relationship target ID: {0} Rule ID: {1} Instance:{2} ...
  21. Target entity missing in the discovery data item. The target entity and the membership relationship entity must be inserted ...
  22. Target property is currently not supported on Datasource, Probe, or Condition Detection module references. Error in ID={0}, ...
  23. Target/.$ expressions are not allowed in module references that have the Target property specified. Remove the Target property ...
  24. Task in user role scope is not allowed for this user role. The profile associated with this user role does not allow task ...
  25. Template in user role scope is not allowed for this user role. The profile associated with this user role does not allow ...
  26. The '{0}' cloud already has the '{1}' price sheet assigned to it.{2}{2}Remove the cloud from the list or unassign the cloud ...
  27. The account used to connect to the tier was unauthorized. Make sure a valid username and password were specified on ConnectTier. ...
  28. The agent ({0}) is managing other devices and cannot be uninstalled. Resolve this issue via Agentless Managed view in Administration ...
  29. The batch size controls how much data is retrieved per batch from this reader. The value must be between 100 and 10,000. ...
  30. The call produced inconsistent results. The data on the client does not match the data returned from the server. The most ...
  31. The call resulted in multiple return values, where one was expected. Use an appropriate method for further specializing the ...
  32. The change request template below will be applied when any of the below listed software packages is selected in the self-service ...
  33. The class does not implement the Commit() method. Please use the SaveObjects() method on DatawarehouseStaging service on ...
  34. The class property value specified in the discovery data item is not valid. The value needs to adhere to the class. Class ...
  35. The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection. ...
  36. The collection ids or names below do not exist in the SCCM database {0} on server {1}: {2} The list of valid collection names ...
  37. The collection of objects on which the loop operates. The loop will end after it has acted on each object in the collection. ...
  38. The component Alias {0} does not match the alias of any component declared on the projection {1} specified by TypeMapping. ...
  39. The ComponentType ({0}) has lifetime set to ReferenceCount but there are no ComponentReference for this ComponentType is ...
  40. The Configuration Manager 2007 site server database has a build version that is not supported (found: {0}, expected: 6204+). ...
  41. The Configuration Manager 2007 site server database has a build version that is not supported (found: {0}, expected: 6487+). ...
  42. The connector could not be deleted because there are outstanding connector subscriptions that use it. Please delete these ...
  43. The connector with the given connector ID is in an incorrect initialized state for the given operation or does not exist. ...
  44. The criteria associated with this user prompt was authored outside of this control and cannot be edited. To change the criteria, ...
  45. The criteria used for the query has a character or keyword that is not valid. The following parse error was returned: {0} ...
  46. The CSVImporter could not run. The Open(string dataFileName, string formatFileName) method must complete successfully before ...
  47. The Cube and CubeExtension cannot be in the same management pack. All elements in the cube extension can be added to the ...
  48. The cube dimension specified by the many-to-many relationship was not found in the cube. Cube Dimension: {0}. The deployment ...
  49. The cube dimension targeted by the action was not found. Cube Dimension : {0}. The deployment of the cube may still succeed ...
  50. The current context of the path does not allow for any portion to end in an abstract class reference. The following path ...
  51. The Customer Experience Improvement Program collect data about your use of Microsoft applications to identify possible improvements ...
  52. The Customer Experience Improvement Program collects data about your use of Microsoft applications to identify possible improvements ...
  53. The Customer Experience Improvement Program collects data anonymously about the use of Microsoft applications to identify ...
  54. The customizations done on selected form '{0}' will permanently be removed from this management pack. Do you want to continue? ...
  55. The DailyFrequency and DailyStart parameters can only be specified for a daily schedule. Use -ScheduleType Daily or omit ...
  56. The data access service was unable to read license information. This is probably due to an incorrectly restored Root Management ...
  57. The Data Access service was unable to synchronize its snapshot of monitoring object instances with its cached monitoring ...
  58. The data warehouse management group to which this management group is registered must be upgraded or unregistered before ...
  59. The Data Warehouse server specified does not have the Microsoft.SystemCenter.Warehouse.Configuration management pack. Please ...
  60. The database subscription configuration is not valid. The following errors were encountered: Exception message: %5 One or ...
  61. The database subscription has recovered from its wait to be acknowledged. The following errors were encountered: Exception ...
  62. The database subscription has recovered from its wait to execute database queries. The following errors were encountered: ...
  63. The database subscription is unable to find instances that match its criteria because of database errors. The following errors ...
  64. The database subscription is unable to notify the runtime of errors it encountered. The following errors were encountered: ...
  65. The database subscription is unable to retrieve the watermark because of database errors. The watermark is being set from ...
  66. The database subscription is unable to save the error state to the database. Check previous event log messages for the error. ...
  67. The database subscription is unable to save the state of triggered Windows workflow because of database errors. You will ...
  68. The database subscription is unable to save the watermark because of database errors. If the module is restarted you may ...
  69. The database subscription is unable to trigger the Windows workflow because of Data Access service errors. The following ...
  70. The database subscription notification acknowledgement is taking longer than expected. The following errors were encountered: ...
  71. The database subscription notification could not be authorized. Notifications will be sent without authorizing the subscription's ...
  72. The database subscription query is longer than expected. Check the database or simplify the database subscription criteria. ...
  73. The database subscription ran into errors while removing the subscription. The following errors were encountered: Exception ...
  74. The database subscription was unable to notify about instances that matched its criteria because of runtime errors. The following ...
  75. The database subscription Windows workflow configuration is not valid. The following errors were encountered: Exception message: ...