System Center Configuration Manager 2007

  1. SMS Software Inventory Processor is terminating its processing cycle due to a SQL Server problem.%12 Solution: 1. Review ...
  2. SMS Software Inventory Processor is updating database statistics.%12 By default, statistics are updated to optimize SQL Server ...
  3. SMS Software Inventory Processor requested a resynchronization for machine "%1" because a software inventory file was sent ...
  4. SMS Software Inventory Processor requested a resynchronization for machine "%1" because an attempt was made to update inventory ...
  5. SMS Software Inventory Processor was unable to store collected file "%1" for resource "%2".%12 Possible cause: Low disk space ...
  6. SMS Software Metering Agent encountered an error while collecting %1 data from WMI, error code %2. The Agent will not be ...
  7. SMS Software Metering Agent failed to download %1 rule file, error code %2. The agent will retry later to download this file.%12%0 ...
  8. SMS Software Metering Agent failed to upload %1 usage data file, error code %2. The agent will retry later to upload this ...
  9. SMS Software Metering Processor could not process a summary file sent from a child site because a referenced computer was ...
  10. SMS Software Metering Processor could not process a summary file sent from a child site because a referenced computer was ...
  11. SMS Software Metering Processor could not process replicated summary data from a child site.%12 Possible cause: SQL Server ...
  12. SMS Software Metering Processor experienced an error while processing and forwarding usage data to the parent site.%12 Possible ...
  13. SMS Software Metering Processor failed to completely process local rule changes, the rule change log has not been cleared ...
  14. SMS Software Metering Processor failed to process a rule replicated from the parent site. %12 Possible cause: SQL Server ...
  15. SMS Software Metering Processor failed to process the usage file "%1" for client "%2" because a record contained a bad usage ...
  16. SMS Software Metering Processor failed to process the usage file "%1" for client "%2".%12 Possible cause: The file is corrupt. ...
  17. SMS Software Metering Processor failed to process usage data file %1 and moved it to the retry directory. The file will be ...
  18. SMS Software Metering Processor failed to read and configure the registry keys necessary for this component.%12 Possible ...
  19. SMS Software Metering Processor failed to replicate summary data to the parent site.%12 Possible cause: The site server drive ...
  20. SMS Software Metering Processor failed to replicate the definition for rule %1 to child sites. %12 Solution: Review the previous ...
  21. SMS Software Metering Processor has retried the usage data file "%1" the maxumum number of times and has moved it to the ...
  22. SMS Software Metering Processor moved file "%1" to the corrupt directory. The file will be deleted when the minimum clean ...
  23. SMS Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is ...
  24. SMS Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is ...
  25. SMS Software Metering Processor was unable to copy the definition for rule %1 to the master rule file for this site. %12 ...
  26. SMS SQL Backup service on the SQL server %1 did not start the SMS database backup. SMS SQL Backup service might not be running ...
  27. SMS SQL Backup service on the SQL server %1 failed to backup the SMS database %2. The error reported by the service is %3. ...
  28. SMS SQL Monitor could not start the SMS Backup service on server %1.%12 Possible cause: You changed the service setting for ...
  29. SMS SQL Monitor failed to copy file smsxp.dll from the \SMS\bin\i386 directory (or \SMS\bin\alpha if this is an Alpha computer) ...
  30. SMS SQL Monitor failed to execute database maintenance SQL command "%1".%12 Possible cause: The SQL command contains syntax ...
  31. SMS SQL Monitor failed to execute database maintenance task "%1".%12 Possible cause: A SQL Server problem prevented this ...
  32. SMS SQL Monitor failed to install trigger "%1" in the SMS site database.%12 Possible cause: Either table "%2" or column "%3" ...
  33. SMS SQL Monitor is executing database maintenance SQL command/task "%1". You can configure the execution schedule for this ...
  34. SMS SQL Monitor is installing trigger "%1" for table "%2" and actions "%3" in the SMS site database. Server components such ...
  35. SMS SQL Monitor is removing trigger "%1" from the SMS site database. Server components such as SMS Hierarchy Manager, SMS ...
  36. SMS State Migration Point failed to read the SignedSerializedSMPKey from the registry on computer %1. Possible reasons are ...
  37. SMS Status Manager has created %1 instances of the "SMS Status Messages" performance object, which is the maximum allowed ...
  38. SMS Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the ...
  39. SMS Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the ...
  40. SMS Status Manager received a status message with an invalid time stamp. The status message was reported by component "%1" ...
  41. SMS Status Manager successfully initialized an in-memory queue to forward status messages to the summarizer component %1. ...
  42. SMS Status Manager successfully initialized the "SMS Status Messages" performance object. Every time SMS Status Manager receives ...
  43. SMS Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt ...
  44. SMS Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt ...
  45. SMS Status Manager was instructed by a Status Filter Rule to execute program and command-line arguments "%1" upon receipt ...
  46. SMS Status Manager will no longer forward status messages to the summarizer component %1 because the summarizer was disabled. ...
  47. SMS Systems Management Server could not locate the "System Management" container in Active Directory. Nor could it create ...
  48. SMS Systems Management Server created a default "System Management" container in Active Directory. This will be used to publish ...
  49. SMS Windows NT Remote Client Installation Manager created the client configuration request "%1" for the resource "%2" in ...
  50. SMS Windows NT Remote Client Installation Manager failed to create the client configuration request "%1" for the resource ...
  51. SMS Windows NT Remote Client Installation Manager failed to initialize, but it will retry in one hour.%12 Possible cause: ...
  52. SMS Windows NT Remote Client Installation Manager failed to set up change notifications, but it will retry in one hour.%12 ...
  53. SMS Windows NT Server Discovery Agent failed to read the location of the outbox.%12 Possible cause: The information necessary ...
  54. SMS Windows NT Server Discovery Agent failed to read the necessary registry information.%12 Possible cause: The registry ...
  55. SMS Windows NT Server Discovery Agent read the system roles and found %1 server role entries in the site control file. Windows ...
  56. SMS Writer could not start the "%1" executable on the local computer.%12 Possible cause: "%1" does not exist in the specified ...
  57. SMS Writer could not start the %1 service on site system %2.%12 Possible cause: SMS Writer does not have sufficient access ...
  58. SMS Writer could not start the %1 SMS client application on the local computer.%12 Possible causes: %1 is not in the system ...
  59. SMS Writer could not stop the "%1" executable on the local computer.%12 Possible cause: "%1" is an interactive Windows application ...
  60. SMS Writer could not stop the %1 service on site system %2.%12 Possible cause: SMS Writer does not have sufficient access ...
  61. SMS Writer could not stop the %1 SMS client application on the local computer.%12 Possible cause: %1 does not exist on the ...
  62. SMS Writer found syntax errors on the following lines:%1 in backup control file. Site backup will fail.%12 Possible cause: ...
  63. SMS Writer was unable to export the registry key %1 to %2.%12 Possible cause: SMS Writer was unable to connect to or set ...
  64. SMS Writer was unable to locate the file system object %1.%12 Possible cause: %1 is not readable. Solution: Adjust file attributes ...
  65. SMS Writer was unable to open control file "%1". Site backup will fail.%12 Possible cause: Wrong name specified or permissions ...
  66. SMS Writer was unable to write the machine info to the temporary backup destination %1.%12 Possible cause: %1 might be locked ...
  67. SMS WSUS Configuration Manager failed to configure proxy settings on WSUS Server "%1".%12 Possible cause: WSUS Server version ...
  68. SMS WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "%1".%12 Possible cause: WSUS ...
  69. SMS WSUS Configuration Manager failed to get update categories, classifications and locales from WSUS Server "%1".%12 Possible ...
  70. SMS WSUS Configuration Manager failed to monitor WSUS Server "%1".%12 Possible cause: WSUS Server version 3.0 and above is ...
  71. SMS WSUS Configuration Manager failed to publish client boot-strapper package "%1" with version "%2" to the Software Updates ...
  72. SMS WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server "%1".%12 Possible ...
  73. SMS WSUS Configuration Manager failed to unpublish client boot-strapper package "%1" from the Software Updates Point.%12%0 ...
  74. SMS WSUS Configuration Manager failed to unpublish client boot-strapper package "%1" with version "%2" from the Software ...
  75. SMS WSUS Configuration Manager has configured WSUS Server "%1" to sync from the parent WSUS Server instead of sync from Microsoft ...