System Center Configuration Manager 2007
- SMS Software Inventory Processor is terminating its processing cycle due to a SQL Server problem.%12 Solution: 1. Review ...
- SMS Software Inventory Processor is updating database statistics.%12 By default, statistics are updated to optimize SQL Server ...
- SMS Software Inventory Processor requested a resynchronization for machine "%1" because a software inventory file was sent ...
- SMS Software Inventory Processor requested a resynchronization for machine "%1" because an attempt was made to update inventory ...
- SMS Software Inventory Processor was unable to store collected file "%1" for resource "%2".%12 Possible cause: Low disk space ...
- SMS Software Metering Agent encountered an error while collecting %1 data from WMI, error code %2. The Agent will not be ...
- SMS Software Metering Agent failed to download %1 rule file, error code %2. The agent will retry later to download this file.%12%0 ...
- SMS Software Metering Agent failed to upload %1 usage data file, error code %2. The agent will retry later to upload this ...
- SMS Software Metering Processor could not process a summary file sent from a child site because a referenced computer was ...
- SMS Software Metering Processor could not process a summary file sent from a child site because a referenced computer was ...
- SMS Software Metering Processor could not process replicated summary data from a child site.%12 Possible cause: SQL Server ...
- SMS Software Metering Processor experienced an error while processing and forwarding usage data to the parent site.%12 Possible ...
- SMS Software Metering Processor failed to completely process local rule changes, the rule change log has not been cleared ...
- SMS Software Metering Processor failed to process a rule replicated from the parent site. %12 Possible cause: SQL Server ...
- SMS Software Metering Processor failed to process the usage file "%1" for client "%2" because a record contained a bad usage ...
- SMS Software Metering Processor failed to process the usage file "%1" for client "%2".%12 Possible cause: The file is corrupt. ...
- SMS Software Metering Processor failed to process usage data file %1 and moved it to the retry directory. The file will be ...
- SMS Software Metering Processor failed to read and configure the registry keys necessary for this component.%12 Possible ...
- SMS Software Metering Processor failed to replicate summary data to the parent site.%12 Possible cause: The site server drive ...
- SMS Software Metering Processor failed to replicate the definition for rule %1 to child sites. %12 Solution: Review the previous ...
- SMS Software Metering Processor has retried the usage data file "%1" the maxumum number of times and has moved it to the ...
- SMS Software Metering Processor moved file "%1" to the corrupt directory. The file will be deleted when the minimum clean ...
- SMS Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is ...
- SMS Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is ...
- SMS Software Metering Processor was unable to copy the definition for rule %1 to the master rule file for this site. %12 ...
- SMS SQL Backup service on the SQL server %1 did not start the SMS database backup. SMS SQL Backup service might not be running ...
- SMS SQL Backup service on the SQL server %1 failed to backup the SMS database %2. The error reported by the service is %3. ...
- SMS SQL Monitor could not start the SMS Backup service on server %1.%12 Possible cause: You changed the service setting for ...
- 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) ...
- SMS SQL Monitor failed to execute database maintenance SQL command "%1".%12 Possible cause: The SQL command contains syntax ...
- SMS SQL Monitor failed to execute database maintenance task "%1".%12 Possible cause: A SQL Server problem prevented this ...
- SMS SQL Monitor failed to install trigger "%1" in the SMS site database.%12 Possible cause: Either table "%2" or column "%3" ...
- SMS SQL Monitor is executing database maintenance SQL command/task "%1". You can configure the execution schedule for this ...
- SMS SQL Monitor is installing trigger "%1" for table "%2" and actions "%3" in the SMS site database. Server components such ...
- SMS SQL Monitor is removing trigger "%1" from the SMS site database. Server components such as SMS Hierarchy Manager, SMS ...
- SMS State Migration Point failed to read the SignedSerializedSMPKey from the registry on computer %1. Possible reasons are ...
- SMS Status Manager has created %1 instances of the "SMS Status Messages" performance object, which is the maximum allowed ...
- SMS Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the ...
- SMS Status Manager received a status message reported by component "%1" running on computer "%2", and the time stamp on the ...
- SMS Status Manager received a status message with an invalid time stamp. The status message was reported by component "%1" ...
- SMS Status Manager successfully initialized an in-memory queue to forward status messages to the summarizer component %1. ...
- SMS Status Manager successfully initialized the "SMS Status Messages" performance object. Every time SMS Status Manager receives ...
- SMS Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt ...
- SMS Status Manager was instructed by a Status Filter Rule to execute program "%1" with command-line arguments "%2" upon receipt ...
- SMS Status Manager was instructed by a Status Filter Rule to execute program and command-line arguments "%1" upon receipt ...
- SMS Status Manager will no longer forward status messages to the summarizer component %1 because the summarizer was disabled. ...
- SMS Systems Management Server could not locate the "System Management" container in Active Directory. Nor could it create ...
- SMS Systems Management Server created a default "System Management" container in Active Directory. This will be used to publish ...
- SMS Windows NT Remote Client Installation Manager created the client configuration request "%1" for the resource "%2" in ...
- SMS Windows NT Remote Client Installation Manager failed to create the client configuration request "%1" for the resource ...
- SMS Windows NT Remote Client Installation Manager failed to initialize, but it will retry in one hour.%12 Possible cause: ...
- SMS Windows NT Remote Client Installation Manager failed to set up change notifications, but it will retry in one hour.%12 ...
- SMS Windows NT Server Discovery Agent failed to read the location of the outbox.%12 Possible cause: The information necessary ...
- SMS Windows NT Server Discovery Agent failed to read the necessary registry information.%12 Possible cause: The registry ...
- SMS Windows NT Server Discovery Agent read the system roles and found %1 server role entries in the site control file. Windows ...
- SMS Writer could not start the "%1" executable on the local computer.%12 Possible cause: "%1" does not exist in the specified ...
- SMS Writer could not start the %1 service on site system %2.%12 Possible cause: SMS Writer does not have sufficient access ...
- SMS Writer could not start the %1 SMS client application on the local computer.%12 Possible causes: %1 is not in the system ...
- SMS Writer could not stop the "%1" executable on the local computer.%12 Possible cause: "%1" is an interactive Windows application ...
- SMS Writer could not stop the %1 service on site system %2.%12 Possible cause: SMS Writer does not have sufficient access ...
- SMS Writer could not stop the %1 SMS client application on the local computer.%12 Possible cause: %1 does not exist on the ...
- SMS Writer found syntax errors on the following lines:%1 in backup control file. Site backup will fail.%12 Possible cause: ...
- SMS Writer was unable to export the registry key %1 to %2.%12 Possible cause: SMS Writer was unable to connect to or set ...
- SMS Writer was unable to locate the file system object %1.%12 Possible cause: %1 is not readable. Solution: Adjust file attributes ...
- SMS Writer was unable to open control file "%1". Site backup will fail.%12 Possible cause: Wrong name specified or permissions ...
- SMS Writer was unable to write the machine info to the temporary backup destination %1.%12 Possible cause: %1 might be locked ...
- SMS WSUS Configuration Manager failed to configure proxy settings on WSUS Server "%1".%12 Possible cause: WSUS Server version ...
- SMS WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "%1".%12 Possible cause: WSUS ...
- SMS WSUS Configuration Manager failed to get update categories, classifications and locales from WSUS Server "%1".%12 Possible ...
- SMS WSUS Configuration Manager failed to monitor WSUS Server "%1".%12 Possible cause: WSUS Server version 3.0 and above is ...
- SMS WSUS Configuration Manager failed to publish client boot-strapper package "%1" with version "%2" to the Software Updates ...
- SMS WSUS Configuration Manager failed to subscribe to update categories and classifications on WSUS Server "%1".%12 Possible ...
- SMS WSUS Configuration Manager failed to unpublish client boot-strapper package "%1" from the Software Updates Point.%12%0 ...
- SMS WSUS Configuration Manager failed to unpublish client boot-strapper package "%1" with version "%2" from the Software ...
- SMS WSUS Configuration Manager has configured WSUS Server "%1" to sync from the parent WSUS Server instead of sync from Microsoft ...