System Center Service Management Automation 2012

  1. A channel into the sanbox manage has failed to verify the connecting client identity. Unknown client name: {0} and remote ...
  2. Activity Metadata Insertion Error in SetActivityMetadataValue; Tenant ID: {1}, ModuleName: {2}, ModuleVersion: {3}. : {4} ...
  3. After uninstalling, you must remove the worker from the runbook worker deployment using the New-SmaRunbookWorkerDeployment ...
  4. An error has occurred while determining whether the database exists. Please verify that your database information is correct. ...
  5. An unexpected exception prevented the cache maintenance from completing, another maintenance should occur shortly. {0}
  6. Any missing prerequisites are marked with a red X icon. System Center 2012 R2 Service Management Automation Runbook Worker ...
  7. Any missing prerequisites are marked with a red X icon. System Center 2012 R2 Service Management Automation Web Service Setup ...
  8. Cannot get runbook snapshots with criteria (jobStatus: {0}, jobStartBeginTime: {1}, jobStartEndTime: {2}, sortProperty: {3}, ...
  9. Cannot validate the 'ComputerName' for the Runbook Worker deployment. The argument is null or empty. Supply an argument that ...
  10. Cannot validate the argument on parameter 'RunbookWorker'. The argument is missing required information for the 'ComputerName' ...
  11. Cannot validate the argument on parameter 'RunbookWorker'. The argument type '{0}' is not supported. Supply an argument that ...
  12. Conversion of value to JSON failed, passing the original string for Job ID {1}, parameter: {2}. No specific error message ...
  13. Creating a new Runbook Worker deployment. Note: There can be unpredictable results if the deployment is changed when there ...
  14. Creating empty Runbook Worker deployment. Any new jobs will not be queued, but the maintainer will resume them once there ...
  15. Error calling AddStreamRecord; Tenant ID: {1}, Job ID: {2}, Runbook Version ID: {3}, Stream Type: {4}, Record: {5}, Text ...
  16. Handle job action was aborted because the job data is missing. Check if the job, Runbook or tenant was deleted.
  17. If you don't provide a Product key during setup, System Center 2012 R2 Service Management Automation will install as an evaluation ...
  18. Installation of the runbook worker has completed successfully, but if this is not the first worker installed in your SMA ...
  19. Job ID {1} :: Activate command not executed - the job is loaded but the current status does not allow Activate.
  20. Job ID {1} :: Activate command not executed - the job is loaded but the current status does not allow Reactivate.
  21. Job ID {1} :: Resume {2} command not executed - the job is loaded but the current status does not allow Resume.
  22. Job ID {1} :: Terminate command not executed - the job is loaded but the current status does not allow Terminate.
  23. Maintainer cannot restore the job ID {1}. The job data is null. Check if the job, runbook or tenant were deleted.
  24. Microsoft Update offers security updates and other important updates for Windows and other Microsoft software, including ...
  25. Module {0} could not be created as connection type with the same name {1} and different connention type field properties/values ...
  26. No authentication method has been selected. An authentication method needs to be specified in the authentication.config file. ...
  27. RunbookService unexpected call to SetUnavailable. Only the storage availability participants should set the storage to unavailable. ...
  28. SandboxCollection: Ignoring all new job actions, the system is draining, any affected jobs will be recovered when the service ...
  29. SandboxCollection: The job {0} for Tenant {1} action {2} cannot be run because the process stopped unexpectedly. The job ...
  30. SandboxCollection: The sandbox {0} faulted, but the system is draining, any affected jobs will be recovered when the service ...
  31. SandboxCollection: The system is draining jobs, preparing to stop. All future pending actions and sandbox faults will be ...
  32. SandboxManager stops processing new job actions. This is triggered by the unavailable storage, stop or shutdown service request. ...
  33. The channel into the sandbox manager could not verify the caller of the {1} method, so the channel has been faulted.
  34. The Customer Experience Improvement Program collects data about your use of Microsoft applications to identify possible improvements ...
  35. The Runbook Worker deployment specifies the computers in your network that are designated to run SMA runbooks. The deployment ...
  36. The Setup wizard is already running. Please close any other instance of the Setup wizard before you start the wizard again. ...
  37. The value contains a secure string for the key "{0}" that must be converted and stored as plain text. Do you wish to continue? ...
  38. You currently have another version of Service Management Automation PowerShell Module installed. You must uninstall using ...
  39. You currently have another version of Service Management Automation Runbook Worker installed. You must uninstall using Add/Remove ...
  40. You currently have another version of Service Management Automation Web Service installed. You must uninstall using Add/Remove ...
  41. You have insufficient privileges to create the SMA database. Your account for the specified SQL Server must have the 'sysadmin' ...
  42. You have insufficient privileges to update the SMA database. Your account for the specified SQL Server must have the CONNECT ...
  43. You have insufficient privileges to update the SMA database. Your account for the specified SQL Server must have the CONNECT ...
  44. You must accept the license terms before you can install or use the software. If you do not accept the license terms, installation ...