System Center Service Management Automation 2012 R2

  1. A channel into the sanbox manage has failed to verify the connecting client identity. Unknown client name: {0} and remote ...
  2. A file that is required cannot be installed because the cabinet file 2 has an invalid digital signature. This may indicate ...
  3. A file that is required cannot be installed because the cabinet file 2 is not digitally signed. This may indicate that the ...
  4. A previous installation for this product is in progress. You must undo the changes made by that installation to continue. ...
  5. A workflow defined in System Center 2012 R2 Orchestrator - Service Management Automation was unable to start or complete ...
  6. A workflow defined in System Center 2012 R2 Orchestrator - Service Management Automation was was stopped because of an exception. ...
  7. Activity Metadata Insertion Error in SetActivityMetadataValue; Tenant ID: {1}, ModuleName: {2}, ModuleVersion: {3}. : {4} ...
  8. After uninstalling, you must remove the worker from the runbook worker deployment using the New-SmaRunbookWorkerDeployment ...
  9. An error has occurred while determining whether the database exists. Please verify that your database information is correct. ...
  10. An error occurred during the installation of assembly '[6]'. One or more modules of the assembly could not be found. HRESULT: ...
  11. An error occurred during the installation of assembly '[6]'. Please refer to Help and Support for more information. HRESULT: ...
  12. An error occurred during the installation of assembly '[6]'. The assembly is not strongly named or is not signed with the ...
  13. An error occurred during the installation of assembly '[6]'. The signature or catalog could not be verified or is not valid. ...
  14. An error occurred while applying security settings. 2 is not a valid user or group. This could be a problem with the package, ...
  15. An error occurred while writing installation information to disk. Check to make sure enough disk space is available, and ...
  16. An installation for 2 is currently suspended. You must undo the changes made by that installation to continue. Do you want ...
  17. An installation package for the product 2 cannot be found. Try the installation again using a valid copy of the installation ...
  18. An unexpected exception prevented the cache maintenance from completing, another maintenance should occur shortly. {0}
  19. Any missing prerequisites are marked with a red X icon. System Center 2012 R2 Service Management Automation Runbook Worker ...
  20. Any missing prerequisites are marked with a red X icon. System Center 2012 R2 Service Management Automation Web Service Setup ...
  21. Both web role as well as the worker role make requests to the database. A high database request rate indicates heavy traffic ...
  22. Cannot create the directory '[2]'. A file with this name already exists. Please rename or remove the file and click Retry, ...
  23. Cannot create the file '[2]'. A directory with this name already exists. Cancel the install and try installing to a different ...
  24. Cannot get runbook snapshots with criteria (jobStatus: {0}, jobStartBeginTime: {1}, jobStartEndTime: {2}, sortProperty: {3}, ...
  25. Cannot validate the 'ComputerName' for the Runbook Worker deployment. The argument is null or empty. Supply an argument that ...
  26. Cannot validate the argument on parameter 'RunbookWorker'. The argument is missing required information for the 'ComputerName' ...
  27. Cannot validate the argument on parameter 'RunbookWorker'. The argument type '{0}' is not supported. Supply an argument that ...
  28. Click Change to begin the installation. Click Back to review or change any of your installation settings. Click Cancel to ...
  29. Click Install to begin the installation. Click Back to review or change any of your installation settings. Click Cancel to ...
  30. Click Remove to remove ProductName from your computer. Click Back to review or change any of your installation settings. ...
  31. Click Repair to repair the installation of ProductName]. Click Back to review or change any of your installation settings. ...
  32. Click Update to update ProductName from your computer. Click Back to review or change any of your installation settings. ...
  33. Collects the Job Queue length which indicates the number of jobs waiting to be processed by the Service Management Automation ...
  34. Collects the Web Service Calls Per Second performance counter. This indicates the number of calls that clients are making ...
  35. Collects the Work Database Response Time performance counter. This indicates the response time for calls made from the Worker ...
  36. Component Services (COM+ 1.0) are not installed on this computer. This installation requires Component Services in order ...
  37. Conversion of value to JSON failed, passing the original string for Job ID {1}, parameter: {2}. No specific error message ...
  38. Could not create key: 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
  39. Could not delete key 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
  40. Could not delete value 2 from key 3]. { System error 4].} Verify that you have sufficient access to that key, or contact ...
  41. Could not get sub key names for key 2]. { System error 3].} Verify that you have sufficient access to that key, or contact ...
  42. Could not get value names for key 2]. { System error 3].} Verify that you have sufficient access to that key, or contact ...
  43. Could not increase the available registry space. 2 KB of free registry space is required for the installation of this application. ...
  44. Could not open key: 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support personnel. ...
  45. Could not read security information for key 2]. { System error 3].} Verify that you have sufficient access to that key, or ...
  46. Could not read value 2 from key 3]. { System error 4].} Verify that you have sufficient access to that key, or contact your ...
  47. Could not register font 2]. Verify that you have sufficient permissions to install fonts, and that the system supports this ...
  48. Could not set file security for file '[3]'. Error: 2]. Verify that you have sufficient privileges to modify the security ...
  49. Could not update environment variable '[2]'. Verify that you have sufficient privileges to modify environment variables. ...
  50. Could not write value 2 to key 3]. { System error 4].} Verify that you have sufficient access to that key, or contact your ...
  51. Creating a new Runbook Worker deployment. Note: There can be unpredictable results if the deployment is changed when there ...
  52. Creating empty Runbook Worker deployment. Any new jobs will not be queued, but the maintainer will resume them once there ...
  53. Determines if the Job Queue length has exceeded the specified threshold. This queue is stored in the Service Management Automation ...
  54. Error applying patch to file 2]. It has probably been updated by other means, and can no longer be modified by this patch. ...
  55. Error calling AddStreamRecord; Tenant ID: {1}, Job ID: {2}, Runbook Version ID: {3}, Stream Type: {4}, Record: {5}, Text ...
  56. Error configuring ODBC data source: 4], ODBC error 2]: 3]. Verify that the file 4 exists and that you can access it.
  57. For this monitor to work correctly, it must have permission to read the Service Management Automation database. Create a ...
  58. Handle job action was aborted because the job data is missing. Check if the job, Runbook or tenant was deleted.
  59. Highlighted volumes do not have enough disk space available for selected features. You can either remove some files from ...
  60. If the job queue length has reached critical limit then workers are not able to adequately handle the job load. Rate of job ...
  61. If the monitor is configured correctly and the monitor is in error then the database is offline or the database server is ...
  62. If the monitor is in an error state, the database is currently overloaded. This condition can be caused by a variety of reasons. ...
  63. If this monitor is in an error state, it indicates that the Runbook service is consuming an excessive amount of processor ...
  64. If this monitor is in an error state, it indicates that the web service is experiencing heavy traffic that could degrade ...
  65. If this monitor is in error, then either the database is not available from the server or the security for the monitor is ...
  66. If you don't provide a Product key during setup, System Center 2012 R2 Service Management Automation will install as an evaluation ...
  67. In order to complete the installation of 2], you must restart the computer. Other users are currently logged on to this computer, ...
  68. Installation of the runbook worker has completed successfully, but if this is not the first worker installed in your SMA ...
  69. Job ID {1} :: Activate command not executed - the job is loaded but the current status does not allow Activate.
  70. Job ID {1} :: Activate command not executed - the job is loaded but the current status does not allow Reactivate.
  71. Job ID {1} :: Resume {2} command not executed - the job is loaded but the current status does not allow Resume.
  72. Job ID {1} :: Terminate command not executed - the job is loaded but the current status does not allow Terminate.
  73. Maintainer cannot restore the job ID {1}. The job data is null. Check if the job, runbook or tenant were deleted.
  74. Microsoft Update offers security updates and other important updates for Windows and other Microsoft software, including ...
  75. Module {0} could not be created as connection type with the same name {1} and different connention type field properties/values ...