System Center Configuration Manager 2007

  1. The SMS Hardware Inventory schema has been updated successfully with a new Managed Object Format (MOF) file from site "%1". ...
  2. The SMS Inventory Data Loader has detected that the inventory update process has already been completed. Therefore, SMS Inventory ...
  3. The SMS Inventory Data Loader inventory update process failed to write the MIF file for machine %1 of architecture %2.%12 ...
  4. The SMS Inventory Data Loader inventory update process has finished successfully. All inventory has been sent to the parent ...
  5. The SMS Inventory Data Loader inventory update process has initialized the inventory update status file, which controls the ...
  6. The SMS Inventory Data Loader inventory update process will use the directory %1. SMS Inventory Data Loader will create delta ...
  7. The SMS PXE Service Point does not have a boot image matching the processor architetcure of the PXE booting device. Device ...
  8. The SMS PXE Service Point failed to find boot image for package %3 while handling device. Device MAC Address:%1 SMBIOS GUID:%2. ...
  9. The SMS PXE Service Point failed to find boot image for package %3 while handling device. Stalling device until package becomes ...
  10. The SMS PXE Service Point failed to get boot action from database for device. Device MAC Address:%1 SMBIOS GUID:%2. %0%12 ...
  11. The SMS PXE Service Point failed to initialize the WDS PXE Provider. Check Previous Messages for more error information.%0%12 ...
  12. The SMS PXE Service Point failed to read and configure the registry keys necessary for this component. Possible cause: The ...
  13. The SMS PXE Service Point instructed the device to boot to the bootimage %3 based on advertisement %4. Device MAC Address:%1 ...
  14. The SMS PXE Service Point intructed device to boot normally since it already had executed advertisement %3. Device MAC Address:%1 ...
  15. The SMS PXE Service Point intructed device to boot normally since it has no PXE advertisement assigned. Device MAC Address:%1 ...
  16. The SMS PXE Service Point is not actively processing PXE messages. Ignoring request from device. Device MAC Address:%1 SMBIOS ...
  17. The SMS registry indicates no outbox for the sender to scan. Be sure that you are running this application on an SMS Site ...
  18. The SMS service account contains invalid characters. Usernames can contain any characters except the following: " / \ : ; ...
  19. The SMS Service Host (CCMEXEC) encountered a failure (%1) when performing Certificate operations.%12 Possible cause: The ...
  20. The SMS Service Host (CCMEXEC) has entered Low Memory Mode. The machine has %2 meg(s) available RAM + pagefile, which falls ...
  21. The SMS Service Host (CCMEXEC) has recovered from Low Memory Mode. The machine has %2 meg(s) available RAM + pagefile, which ...
  22. The SMS State Migration Point can not authenticate the client %1. Possible cause: Client machine is not part of the domain ...
  23. The SMS State Migration Point failed to read and configure the registry keys necessary for this component. Possible cause: ...
  24. The SMS State Migration Point has reached the minimum disk space threshold of %1 %2 on drive %3 of computer %4. Current free ...
  25. The SMS State Migration Point reached the minimum disk space threshold on all drives of computer %1. Possible cause: Restoring ...
  26. The SMS State System failed to read and configure the registry keys necessary for this component.%12 Possible cause: The ...
  27. The SMS State System message file processing could not process file '%1' and moved it to the corrupt directory. Review the ...
  28. The SMS State System message file processing experienced a severe error and suspended file processing. Review the statesys.log ...
  29. The SMS State System message file processing processed one or more files that contained errors or invalid data. Review the ...
  30. The SMS Wake On LAN component component failed to send wakeup packets for some clients targeted by object id=%1 of type=%2. ...
  31. The SMS Wake On LAN component component failed to start sending wakeup packets for object id=%1 of type=%2. Possible cause:Client ...
  32. The SMS Wake On LAN component component successfully sent wakeup packets to all clients targeted for the object id=%1 of ...
  33. The SMS Wake On LAN component failed access the database. Possible cause:Client data was unavailable. Possible cause: Solution:%12%0 ...
  34. The SMS Wake On LAN component has entered an unavailable state due to a high number of failures. The component's services ...
  35. The SMS Wake On LAN component has failed to read the site control file settings. Possible cause: The information is not yet ...
  36. The SMS Wake On LAN failed to process wakeup information for the object id=%1 of type=%2. Possible cause:An error occured ...
  37. The SMSITMU scanner upgrade was unsuccessful. While the ITMU scan data has been unchanged, the ITMU scanner might not be ...
  38. The software is not available at this time. If you are offline or connected to the Internet, the files will be available ...
  39. The software metering client on the computer "%1" (user "%2") encountered an error and is performing an abnormal shut down ...
  40. The software metering configuration component could not open the database for "%1".%12 Possible cause: SQL Server problem. ...
  41. The software metering configuration component failed to setup the database. SOFTWARE METERING IS NOT CORRECTLY CONFIGURED ...
  42. The Software Metering Data Monthly Usage Summarization task has completed, %1 rows have been added or updated in the summary ...
  43. The software metering server manager could not assign the 'Logon as service' right to the software metering server service ...
  44. The software metering server manager could not assign the software metering server service account "%1" administrative privileges ...
  45. The software metering server manager could not attach to "%1".%12 Possible cause: "%1" is not shared. Solution: Make sure ...
  46. The software metering server manager could not configure the database on the software metering server "%1".%12 Solution: ...
  47. The software metering server manager could not create the "sender" between the software metering server "%1" (on the "%2" ...
  48. The software metering server manager could not create the directory "%1" on the server "%2".%12 Possible cause: The software ...
  49. The software metering server manager could not create the share "%1" for the directory "%2" on the server "%3".%12 Possible ...
  50. The software metering server manager could not create the software metering server service account "%1" locally at the server ...
  51. The software metering server manager could not determine the operating system of the software metering server "%1".%12%0 ...
  52. The software metering server manager could not find the software metering server files for "%1" on the UNC Path "%2".%12 ...
  53. The software metering server manager could not initialize the software metering server "%1".%12 Solution: If you have removed ...
  54. The software metering server manager could not insert the software metering server "%1" into the ABCSRVCG table on the site ...
  55. The software metering server manager could not locate "%1" on the network.%12 Solution: Make sure that the account "%2" on ...
  56. The software metering server manager could not remove the files on the share "%1". You might want to remove these files yourself.%12%0 ...
  57. The software metering server manager could not remove the software metering server "%1" from the software metering client's ...
  58. The software metering server manager could not remove the software metering server "%1" from the software metering database ...
  59. The software metering server manager could not synchronize the data from the site server "%2" to the software metering server ...
  60. The software metering server manager could not update the service password on "%1".%12 Possible cause: Insufficient permissions. ...
  61. The software metering server manager could not update the service settings on the software metering server "%1".%12 Solution: ...
  62. The software metering server manager does not have sufficient privileges to "%1". Make sure the software metering server ...
  63. The software metering server manager does not return licenses, and checked out licenses, to the site server during the deinstallation ...
  64. The software metering server manager encountered an error while copying files to "%2" on the server "%1". The installation ...
  65. The software metering server manager encountered an error while copying ODBC files to the System32 directory on the server ...
  66. The software metering server manager encountered an error while creating an ODBC Data Source Name (DSN) on the server "%1". ...
  67. The software metering server manager encountered an error while installing required ODBC drivers on the server "%1". The ...
  68. The software metering server manager encountered an error while installing the ODBC Manager on the server "%1". The installation ...
  69. The software metering server manager encountered an error while obtaining the software metering client's list of available ...
  70. The software metering server manager encountered an error while trying to configure the software metering server installation ...
  71. The software metering server manager encountered an error while trying to install or start the software metering server service ...
  72. The software metering server manager encountered an error while trying to install the ODBC installation service on the server ...
  73. The software metering server manager encountered an unknown error while installing ODBC on the server "%1". The installation ...
  74. The software metering server manager has been denied access to "%1".%12 Solution: Make sure that the account "%2" on "%3" ...
  75. The software metering server manager has been denied access to install the service "%1". Make sure that the software metering ...