System Center Configuration Manager 2007

  1. SMS Discovery Data Manager failed to complete the rule refresh process.%12 Possible cause: Refer to the previous SMS Discovery ...
  2. SMS Discovery Data Manager failed to connect to the discovery database.%12 Possible cause: SQL Server problem. Solution: ...
  3. SMS Discovery Data Manager failed to copy the .ncf (assignment rule) file "%1" to Asstdata.box, the point of replication ...
  4. SMS Discovery Data Manager failed to create a full refresh file to send to the secondary site.%12 Possible cause: Low disk ...
  5. SMS Discovery Data Manager failed to create the discovery data record (DDR) to send to the new parent site.%12 Possible cause: ...
  6. SMS Discovery Data Manager failed to enumerate discovery architectures.%12 Possible cause: SQL Server problem. Solution: ...
  7. SMS Discovery Data Manager failed to enumerate properties for architecture "%1".%12 Possible cause: SQL Server problem. Solution: ...
  8. SMS Discovery Data Manager failed to format discovery data into file "%1".%12 Possible cause: Low memory. Solution: Stop ...
  9. SMS Discovery Data Manager failed to insert discovery data because SMS is out of client access licenses.%12 Solution: Increase ...
  10. SMS Discovery Data Manager failed to insert the new item from file "%1" into the data source.%12 Possible cause: SQL Server ...
  11. SMS Discovery Data Manager failed to move the new parent site notification file to the Data Loader inbox.%12 Possible cause: ...
  12. SMS Discovery Data Manager failed to notify all consumers that a full refresh has occurred and that users need to refresh ...
  13. SMS Discovery Data Manager failed to open the .ncf (assignment rule) file for site "%1".%12 Possible cause: The file is corrupt. ...
  14. SMS Discovery Data Manager failed to parse the new discovery item data from the parsed discovery data record (DDR) %1.%12 ...
  15. SMS Discovery Data Manager failed to process a client registration request for computer with the identity "%1" and with the ...
  16. SMS Discovery Data Manager failed to process file "%1" because it cannot detect any Name properties. SMS Discovery Data Manager ...
  17. SMS Discovery Data Manager failed to process the discovery data record (DDR) "%1", because it cannot update the data source.%12 ...
  18. SMS Discovery Data Manager failed to read the .ncf (assignment rule) file for site "%1".%12 Possible cause: The file is corrupt. ...
  19. SMS Discovery Data Manager failed to read the current site's .ncf (assignment rule) file.%12 Possible cause: The file is ...
  20. SMS Discovery Data Manager failed to read the new discovery item from the parsed discovery data record (DDR) "%1".%12 Possible ...
  21. SMS Discovery Data Manager failed to read the serial number from the parsed discovery data record (DDR) "%1".%12 Possible ...
  22. SMS Discovery Data Manager failed to read the site control file for site "%1". Because the SMS site database maintains the ...
  23. SMS Discovery Data Manager failed to send discovery data to the new parent site. SMS Discovery Data Manager will retry, resuming ...
  24. SMS Discovery Data Manager failed to send file "%1" to site "%2".%12 Possible cause: Low disk space on site "%2". Solution: ...
  25. SMS Discovery Data Manager failed to send file "%1" to site "%2".%12 Possible cause: Low disk space on the disk drive of ...
  26. SMS Discovery Data Manager failed to synchronize this site's deletions with all secondary site databases. When discovery ...
  27. SMS Discovery Data Manager failed to write item buffer to file "%1". SMS Discovery Data Manager is attempting to send a discovery ...
  28. SMS Discovery Data Manager failed to write the .ncf (assignment rule) file "%1". SMS Discovery Data Manager will retry writing ...
  29. SMS Discovery Data Manager failed to write the item key record to file "%1".%12 Possible cause: Low disk space on the disk ...
  30. SMS Discovery Data Manager failed to write the serial number record to file "%1".%12 Possible cause: Low disk space on the ...
  31. SMS Discovery Data Manager has detected a change in assignment rules. SMS Discovery Data Manager will not process discovery ...
  32. SMS Discovery Data Manager has interpreted discovery data record (DDR) "%1" as a delete request. Therefore, SMS Discovery ...
  33. SMS Discovery Data Manager has processed a discovery data record (DDR) for computer "%1" with the SMS identifier of "%2" ...
  34. SMS Discovery Data Manager has processed a discovery data record (DDR) for computer "%1" with the SMS identifier of "%3" ...
  35. SMS Discovery Data Manager has tried ten times to send the discovery database to the new parent site, and SMS Discovery Data ...
  36. SMS Discovery Data Manager is beginning the process of sending discovery data to the new parent site. (This happens whenever ...
  37. SMS Discovery Data Manager is updating statistics in all tables in the SMS site database, which helps ensure optimal performance ...
  38. SMS Discovery Data Manager will resume processing because it has successfully completed assignment-rule processing.%12%0 ...
  39. SMS Distribution Manager created a 1.x style instruction to send package definition for package "%1" to 1.x child site "%2".%12%0 ...
  40. SMS Distribution Manager failed to access the source directory "%1" for package "%2".%12 Possible cause: SMS Distribution ...
  41. SMS Distribution Manager failed to compress package "%1" from "%2" to "%4". The file that failed the compression is "%3".%12 ...
  42. SMS Distribution Manager failed to copy package "%1" from "%2" to "%3".%12 Possible cause: SMS Distribution Manager does ...
  43. SMS Distribution Manager failed to create a 1.x style instruction to send package "%1" to 1.x child site "%2".%12 Solution: ...
  44. SMS Distribution Manager failed to create a 1.x style instruction to send the package definition for package "%1" to 1.x ...
  45. SMS Distribution Manager failed to create subdirectories on distribution point "%1" for distributing package "%2".%12 Possible ...
  46. SMS Distribution Manager failed to decompress package "%1" from "%2" to "%3". The file that failed to decompress is "%4".%12 ...
  47. SMS Distribution Manager failed to decompress package "%1" from "%2".%12 Possible cause: The compressed image "%2" is either ...
  48. SMS Distribution Manager failed to decompress package "%1" from "%2".%12 Possible cause: The compressed image "%2" is either ...
  49. SMS Distribution Manager failed to delete the compressed image of package "%1" at "%2".%12 Possible cause: The SMS Service ...
  50. SMS Distribution Manager failed to distribute package "%1".%12 Possible cause: The specified share is a hidden SMS share. ...
  51. SMS Distribution Manager failed to distribute package "%1".%12 Possible cause: The specified share is a hidden Windows NT ...
  52. SMS Distribution Manager failed to find or create the defined share or volume on distribution point "%1" for distributing ...
  53. SMS Distribution Manager failed to initialize the network abstraction layer (NAL).%12 Possible cause: SMS Distribution Manager ...
  54. SMS Distribution Manager failed to instruct SMS Scheduler to send package "%1" to child site "%2".%12 Solution: Verify that ...
  55. SMS Distribution Manager failed to process package "%1" (package ID = %2).%12 Possible cause: Distribution manager does not ...
  56. SMS Distribution Manager failed to process package "%1" without a source directory.%12 Possible cause: The Source directory ...
  57. SMS Distribution Manager failed to remove package "%1" from "%2".%12 Possible cause: The share type or the share name have ...
  58. SMS Distribution Manager failed to remove package "%1" from distribution path "%2".%12 Possible cause: The distribution point ...
  59. SMS Distribution Manager failed to remove the previously compressed copy for package "%1" located at "%2".%12 Possible cause: ...
  60. SMS Distribution Manager failed to save package status for package "%1" to the SMS site database.%12 Possible cause: SQL ...
  61. SMS Distribution Manager failed to send the package information for package "%1" to child site "%2".%12 Solution: Verify ...
  62. SMS Distribution Manager failed to update the distribution source for package "%1".%12 Possible cause: SMS Distribution Manager ...
  63. SMS Distribution Manager failed to update the package properties on distribution points for package "%1".%12 Solution: Verify ...
  64. SMS Distribution Manager instructed SMS Scheduler and Sender to send a forwarding request to site "%2", requesting that site ...
  65. SMS Distribution Manager instructed SMS Scheduler and Sender to send the package information for package "%1" to child site ...
  66. SMS Distribution Manager is retrying to distribute package "%1".%12 Wait to see if the package is successfully distributed ...
  67. SMS Distribution Manager is unable to forward package "%1" to site(s) "%2" because the local version of the package ("%3") ...
  68. SMS Distribution Manager is unable to forward package "%1" to site(s) "%2" because the local version of the package ("%3") ...
  69. SMS Executive could not start this component because it could not determine the address of the ThreadMain() function exported ...
  70. SMS Executive could not start this component because it could not load \"%1\" using the MFC AfxLoadLibrary() function.%12 ...
  71. SMS Executive detected that this component stopped unexpectedly.%12 Possible cause: The component is experiencing a severe ...
  72. SMS Executive is scheduled to start this component now, but cannot because it is already running. Possible cause: The component ...
  73. SMS Executive will never start this component because it is never scheduled to run. If you want SMS Executive to start the ...
  74. SMS Hardware Inventory Agent cannot connect to the Common Information Model Object Manager (CIM Object Manager).%12 Possible ...
  75. SMS Hardware Inventory Agent cannot open the "%1" namespace.%12 Possible cause: Windows Management Instrumentation (Winmgmt) ...