System Center Configuration Manager 2012

  1. Site Component Manager successfully removed all accounts, files, and registry keys associated with the Configuration Manager ...
  2. Site Component Manager successfully used the %1 service to run the following program on site system "%2": %3 %4 %5 The program ...
  3. Site Component Manager was instructed by Configuration Manager Setup to deinstall the site. Site Component Manager will now ...
  4. Site Component Manager was instructed by Configuration Manager Setup to shut down the site in preparation for a site upgrade, ...
  5. Site Component Manager will not deinstall any Configuration Manager Server Components from site system "%1" because no Configuration ...
  6. Site Component Manager will not stop any Configuration Manager Server Components on site system "%1" because no Configuration ...
  7. Site Component Manager will now cease trying to deinstall all of the Configuration Manager Server Components from site system ...
  8. Site Component Manager will now cease trying to stop all of the Configuration Manager Server Components on site system "%1", ...
  9. Site Component Manager will now try again to deinstall all of the Configuration Manager Server Components from site system ...
  10. Site Component Manager will now try again to stop all of the Configuration Manager Server Components on site system "%1", ...
  11. Site Control Manager aborted the processing of delta site control file %1.%12 Possible cause: The delta site control file ...
  12. Site Control Manager added a "%1" item named "%2" to the actual site control file %5.%12 This addition occurred as a result ...
  13. Site Control Manager could not completely process delta site control file %1.%12 Possible cause: Some site configuration ...
  14. Site Control Manager could not write a copy of the actual site control file %1 to %2. Consequently, Hierarchy Manager will ...
  15. Site Control Manager created serial number %2 of the actual site control file %1 as a result of processing delta site control ...
  16. Site Control Manager created serial number %2 of the actual site control file %1.%12 This creation occurred in response to ...
  17. Site Control Manager created the temporary file "%1".%12 In a moment, Site Control Manager will rename this file to %2, and ...
  18. Site Control Manager deleted the "%1" item named "%2" from the actual site control file %5.%12 This deletion occurred as ...
  19. Site Control Manager is beginning to process delta site control file "%1".%12 Configuration Manager Server Components and ...
  20. Site Control Manager is configured so that no more heartbeat site control files will be submitted to Hierarchy Manager.%12 ...
  21. Site Control Manager modified the properties of the "%1" item named "%2" in the actual site control file %7.%12 This modification ...
  22. Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager as a heartbeat ...
  23. Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager as a heartbeat ...
  24. Site Control Manager submitted a copy of serial number %2 of the actual site control file %1 to Hierarchy Manager.%12 This ...
  25. Site Control Manager will ignore this site configuration change request ("%1" from site "%2").%12 This change request was ...
  26. Site Control Manager will maintain copies of the %1 most recent actual site control files in the directory "%2".%12 The actual ...
  27. Site Control Manager wrote a copy of the actual site control file %1 to %2.%12 In a moment, Site Control Manager will move ...
  28. Site databases cannot be upgraded when they are configured for replication. Before you begin the upgrade process, disable ...
  29. Site has finished processing resync request for replicationgroup %1]. Please refer to dmpuploader.log for further details.%0 ...
  30. Site maintenance allows you to change your SQL Server and SMS Provider configuration or perform a site reset. Select the ...
  31. Site maintenance allows you to modify site configuration, and perform a site reset to reapply default file and registry permissions ...
  32. Site System Status Summarizer could not access storage object "%1" on site system "%2".%12 Possible cause: The site system ...
  33. Site System Status Summarizer could not access the "%1" database on site database Server "%2". Possible cause: The site database ...
  34. Site System Status Summarizer could not access the transaction log for the "%1" database on SQL Server "%2".%12 Possible ...
  35. Site System Status Summarizer detected that the "%1" database on site database server "%2" has %3 KB of free space, which ...
  36. Site System Status Summarizer detected that the "%1" database on site database server "%2" has %3 KB of free space, which ...
  37. Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Degraded.%12 ...
  38. Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Failed.%12 Possible ...
  39. Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Offline.%12 Possible ...
  40. Site System Status Summarizer detected that the availability of the "%1" role on server "%2" has changed to Unknown.%12 Possible ...
  41. Site System Status Summarizer detected that the database "%1" on site database server "%2" has %3 KB of free space, which ...
  42. Site System Status Summarizer detected that the storage object "%1" on Branch Distribution Point site system "%2" has %3 ...
  43. Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, ...
  44. Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, ...
  45. Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, ...
  46. Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 ...
  47. Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 ...
  48. Site System Status Summarizer detected that the transaction log for the "%1" database on site database server "%2" has %3 ...
  49. Site System Status Summarizer has not been able to access the storage object "%1" on Site Object "%2" for %3 hours. Site ...
  50. Site System Status Summarizer still cannot access storage object "%1" on site system "%2".%12 Possible cause: The site system ...
  51. Site System Status Summarizer still cannot access the "%1" database on site database Server "%2".%12 Possible cause: The ...
  52. Site System Status Summarizer still cannot access the transaction log for the "%1" database on SQL Server "%2".%12 Possible ...
  53. Site System Status Summarizer successfully accessed storage object "%1" on site system "%2".%12 Possible cause: The storage ...
  54. Site System Status Summarizer successfully accessed the "%1" database on SQL Server "%2".%12 Possible cause: The database ...
  55. Site System Status Summarizer successfully accessed the transaction log for the "%1" database on SQL Server "%2". The transaction ...
  56. SMP Control Manager detected SMP is not responding to HTTP requests. The http error is %1.%12 Possible cause: IIS service ...
  57. SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is %1, %2.%12 Possible ...
  58. SMS CI Assignment has been directly deleted from the site Database. Deletion of collection may cause the deletion of all ...
  59. SMS Executive could not start this component because it could not determine the address of the ThreadMain() function exported ...
  60. SMS Executive could not start this component because it could not load \"%1\" using the MFC AfxLoadLibrary() function.%12 ...
  61. SMS Executive detected that this component stopped unexpectedly.%12 Possible cause: The component is experiencing a severe ...
  62. SMS Executive is scheduled to start this component now, but cannot because it is already running. Possible cause: The component ...
  63. SMS Executive will never start this component because it is never scheduled to run. If you want SMS Executive to start the ...
  64. SMS Hardware Inventory Agent cannot update the SMS Hardware Inventory Schema. The new Managed Object Format (MOF) file from ...
  65. SMS Inbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ...
  66. SMS installation cannot complete until the required component, Microsoft .NET Framework Version 4.0, is installed. The component ...
  67. SMS Outbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ...
  68. SMS provider cannot be installed on SQL server as it is clustered and it cannot be installed on the site server as SMS provider ...
  69. SMS Site Component Manager cannot remove HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS subkeys from the registry on server %s. ...
  70. SMS Site Component Manager cannot stop component %s on component server %s. The component is probably performing clean up ...
  71. SMS Site Component Manager cannot stop component %s on multisite component server %s. The component is probably performing ...
  72. SMS SQL Backup service on the SQL Server %1 did not start the database backup. SMS SQL Backup service might not be running ...
  73. SMS SQL Backup service on the SQL Server %1 failed to backup the site database %2. The error reported by the service is %3. ...
  74. SMS Writer could not start the "%1" executable on the local computer.%12 Possible cause: "%1" does not exist in the specified ...
  75. SMS Writer could not start the %1 ConfigMgr client application on the local computer.%12 Possible causes: %1 is not in the ...