System Center Configuration Manager 2012
- 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 stop the "%1" executable on the local computer.%12 Possible cause: "%1" is an interactive Windows application ...
- SMS Writer could not stop the %1 ConfigMgr client application on the local computer.%12 Possible cause: %1 does not exist ...
- SMS Writer could not stop the %1 service on site system %2.%12 Possible cause: SMS Writer does not have sufficient access ...
- 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 ...
- Snapshot for replication group "%1" from Site %2 failed to be applied successfully.%12 Error: %3 %12 Refer to rcmctrl.log ...
- Software Center can not be loaded. There is a problem loading the required components for Software Center. You can try launching ...
- Software Center cannot be loaded at this time. If your computer has recently been restarted, try relaunching Software Center ...
- Software Center cannot get the current status for some of the software. Software Center will list any items with available ...
- Software Center encountered an error while starting the application. Information that is shown in the following section might ...
- Software Inventory Agent could not collect one or more files.%12 Possible cause: Software Inventory Agent needs to make a ...
- Software Inventory Agent has insufficient virtual memory or disk space to proceed. The inventory cycle will be delayed by ...
- Software Inventory Agent raised an exception while attempting to extract file version information from file "%1".%12 Possible ...
- Software Inventory Agent successfully collected %1 files, totally %2 KB of data, from this computer. These files will be ...
- Software Inventory Agent was unable to collect one or more files because the maximum size for collected files of %1 MB has ...
- Software Inventory Processor failed to process software inventory file "%1" because the file does not have a corresponding ...
- Software Inventory Processor failed to process software inventory file "%1," and has moved it to "%2."%12 Possible cause: ...
- Software Inventory Processor failed to process the file %1 because it is larger than the defined maximum allowable size of ...
- Software Inventory Processor has removed the oldest revision of collected file "%1" for resource "%2". The maximum revision ...
- Software Inventory Processor is terminating its processing cycle due to a SQL Server problem.%12 Solution: 1. Review the ...
- Software Inventory Processor is updating database statistics.%12 By default, statistics are updated to optimize SQL Server ...
- Software Inventory Processor requested a resynchronization for machine "%1" because a software inventory file was sent without ...
- Software Inventory Processor requested a resynchronization for machine "%1" because an attempt was made to update inventory ...
- Software Inventory Processor was unable to store collected file "%1" for resource "%2".%12 Possible cause: Low disk space ...
- Software Metering Agent encountered an error while collecting %1 data from WMI, error code %2. The Agent will not be able ...
- Software Metering Agent failed to download %1 rule file, error code %2. The agent will retry later to download this file.%12%0 ...
- Software Metering Agent failed to upload %1 usage data file, error code %2. The agent will retry later to upload this file.%12%0 ...
- Software Metering Processor could not process a summary file sent from a child site because a referenced computer was not ...
- Software Metering Processor could not process a summary file sent from a child site because a referenced computer was not ...
- Software Metering Processor could not process replicated summary data from a child site.%12 Possible cause: SQL Server problem. ...
- Software Metering Processor experienced an error while processing and forwarding usage data to the parent site.%12 Possible ...
- Software Metering Processor failed to completely process local rule changes, the rule change log has not been cleared and ...
- Software Metering Processor failed to process a rule replicated from the parent site. %12 Possible cause: SQL Server problem. ...
- Software Metering Processor failed to process the usage file "%1" for client "%2" because a record contained a bad usage ...
- Software Metering Processor failed to process the usage file "%1" for client "%2".%12 Possible cause: The file is corrupt. ...
- Software Metering Processor failed to process usage data file %1 and moved it to the retry directory. The file will be reprocessed ...
- Software Metering Processor failed to read and configure the registry keys necessary for this component.%12 Possible cause: ...
- Software Metering Processor failed to replicate summary data to the parent site.%12 Possible cause: The site server drive ...
- Software Metering Processor failed to replicate the definition for rule %1 to child sites. %12 Solution: Review the previous ...
- Software Metering Processor has retried the usage data file "%1" the maxumum number of times and has moved it to the discard ...
- Software Metering Processor moved file "%1" to the corrupt directory. The file will be deleted when the minimum clean up ...
- Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is disabled.%0 ...
- Software Metering Processor successfully processed a change for the rule %1 which was last modified on %2, the rule is enabled.%0 ...
- Software Metering Processor was unable to copy the definition for rule %1 to the master rule file for this site. %12 Solution: ...
- Software removal is only allowed for users with administrative permissions on this computer, or is not allowed on this computer. ...
- Software update catalog (type = %1) sync operation completed successfully. Newer version of catalog was downloaded and updated ...
- Software update catalog (type = %1) sync operation completed successfully. Newer version of catalog was not available.%12%0 ...
- Software update installation failed: the scheduled installation window expired while software update installation was not ...
- Software update installation was postponed: awaiting system restart. Possible cause: Previous installations might have replaced ...
- Software update packages and software update deployments that you have selected for this migration job might contain references ...
- Software updates cannot be installed because a system restart is in progress. To install this update, please try again after ...
- Software updates evaluation failed: could not determine the deployment assignment schedule. This is needed to calculate the ...
- Software updates evaluation failed: could not load software updates authorization list %1. Possible cause: authorization ...
- Software updates evaluation failed: could not locate the scan component of the specified software update inventory tool. ...
- Software updates evaluation failed: could not run the scan component of the specified software update inventory tool on the ...
- Software updates evaluation failed: error loading Win32_PatchState class from WMI. Possible cause: This is most likely a ...
- Software updates evaluation failed: error storing Win32_PatchState class into WMI. Possible cause: This is most likely a ...
- Software updates evaluation failed: invalid syntax or value for the specified scheduled installation window (/l). Possible ...
- Software updates evaluation failed: unable to load resource file. Possible cause: file not present. Solution: Verify that ...
- Software updates evaluation was ended due to a scheduled installation window violation (installation started too early.) ...
- Software updates evaluation was ended due to a scheduled installation window violation (installation started too late.) Solution: ...
- Software Updates Installation Agent completed successfully and suppressed the required system restart because the program ...
- Software Updates Installation Agent completed successfully and suppressed the required system restart because the program ...
- Software updates installation was automatically postponed: a pre-installation restart was required, but the user did not ...
- Software updates installation was automatically postponed: the user did not choose to install the updates and the grace period ...
- Software updates installation was postponed: The user postponed the required pre-installation restart. Possible cause: Previous ...
- Software updates installation was postponed: the user rescheduled the required system restart. Possible cause: Previous installations ...
- Software Updates Scan Agent completed the scan successfully. However, scan reported error(s) %2 that might result in some ...
- Software Updates will be appended to the following deployment. You can modify the deployment name and description to reflect ...
- Some driver(s) can not be imported because they are not applicable to any supported platforms. See DriverCatalog.log file ...
- Some fatal errors occured in setup package decompression on secondary site server. Please review SMS_BOOTSTRAP.log on Secondary ...