System Center Configuration Manager 2007

  1. SMS Executive could not start this component because it could not determine the address of the ThreadMain() function exported ...
  2. SMS Executive could not start this component because it could not load \"%1\" using the MFC AfxLoadLibrary() function.%12 ...
  3. SMS Executive detected that this component stopped unexpectedly.%12 Possible cause: The component is experiencing a severe ...
  4. SMS Executive is scheduled to start this component now, but cannot because it is already running. Possible cause: The component ...
  5. SMS Executive will never start this component because it is never scheduled to run. If you want SMS Executive to start the ...
  6. SMS Hardware Inventory Agent cannot connect to the Common Information Model Object Manager (CIM Object Manager).%12 Possible ...
  7. SMS Hardware Inventory Agent cannot open the "%1" namespace.%12 Possible cause: Windows Management Instrumentation (Winmgmt) ...
  8. SMS Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12 Possible ...
  9. SMS Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12 Possible ...
  10. SMS Hardware Inventory Agent cannot process Management Information Format (MIF) file "%1" and has moved it to "%2".%12 Possible ...
  11. SMS Hardware Inventory Agent cannot update the SMS Hardware Inventory Schema. The new Managed Object Format (MOF) file from ...
  12. SMS Hardware Inventory Agent cannot update the SMS Hardware Inventory Schema.%12 Possible cause: The Hardware Inventory Agent ...
  13. SMS Hardware Inventory Agent has insufficient virtual memory or disk space to proceed. The inventory cycle will be delayed ...
  14. SMS Hardware Inventory Agent is unable to locate the Windows Management Instrumentation (WinMgmt) service.%12 Solution: Verify ...
  15. SMS Hardware Inventory Agent successfully collected hardware inventory from this computer, created a Management Information ...
  16. SMS has detected that there are %1 computers in this site that are running Windows 2000 and above and have the SMS Legacy ...
  17. SMS has detected that there are %1 computers in this site that are running Windows 2000 and above and have the SMS Legacy ...
  18. SMS Hierarchy Manager cannot add address account %1 for secondary site %2 to the address group %3, this must be done manually. ...
  19. SMS Hierarchy Manager cannot add machine account %1 for secondary site %2 to the address group %3, this must be done manually. ...
  20. SMS Hierarchy Manager cannot connect to the SMS site database.%12 Possible cause: SQL Server problem. Solution: 1. Review ...
  21. SMS Hierarchy Manager cannot convert the local site from standard security to advanced security because the site database ...
  22. SMS Hierarchy Manager cannot convert the local site from standard security to advanced security because the site server does ...
  23. SMS Hierarchy Manager cannot convert the local site from standard security to advanced security because the site server is ...
  24. SMS Hierarchy Manager cannot reinstall the SMS Site Component Manager under the new service account and password.%12 Possible ...
  25. SMS Hierarchy Manager cannot remove the computer account of site system %1 from database role %2. This needs to be done manually. ...
  26. SMS Hierarchy Manager cannot save site information to the SMS site database for site "%1". %12 Possible cause: SQL Server ...
  27. SMS Hierarchy Manager detected that a change was requested by this site to the configuration of site "%1". SMS Hierarchy ...
  28. SMS Hierarchy Manager detected that site code "%1" is already in use by existing site "%2".%12 Possible cause: Site "%3" ...
  29. SMS Hierarchy Manager detected that the public key of this site in the site control file is no longer valid and has updated ...
  30. SMS Hierarchy Manager failed to execute site maintenance task "%1".%12 Possible cause: Service containing the maintenance ...
  31. SMS Hierarchy Manager has detected secondary site "%1" has enabled the logon discovery and installation features. SMS 2003 ...
  32. SMS Hierarchy Manager has initiated remote deinstallation of secondary site "%1". To track the progress of this operation, ...
  33. SMS Hierarchy Manager has initiated remote installation of secondary site "%1". To track the progress of this operation, ...
  34. SMS Hierarchy Manager has initiated remote upgrade of secondary site "%1". To track the progress of this operation, you should ...
  35. SMS Hierarchy Manager reinstalled SMS Site Component Manager using the new service account and password. SMS Site Component ...
  36. SMS Hierarchy Manager successfully processed "%1", which represented serial number %4 of the site control file for site "%2" ...
  37. SMS Inbox Manager Assistant running on the client access point "%1" cannot connect to site server "%2".%12 Possible cause: ...
  38. SMS Inbox Manager cannot copy files from "%1" to "%2".%12 Possible cause: The destination drive is full. Solution: Make more ...
  39. SMS Inbox Manager cannot create directory "%1" with the desired security rights on client access point "%2".%12 Possible ...
  40. SMS Inbox Manager cannot create directory "%1" with the desired security rights on server "%2".%12 Possible cause: The destination ...
  41. SMS Inbox Manager cannot create directory "%1" with the desired security rights on site system "%2". (The site system is ...
  42. SMS Inbox Manager cannot create the client access point on site system "%1".%12 Possible cause: Site system "%1" does not ...
  43. SMS Inbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ...
  44. SMS installation cannot complete until the required component, Microsoft .NET Framework Version 2.0, is installed. The component ...
  45. SMS Inventory Data Loader detected more than %1 class redefinitions in %2 minutes. Switching to single-threaded operation ...
  46. SMS Inventory Data Loader detected more than %1 class redefinitions in %2 minutes. Will switch to single-threaded operation ...
  47. SMS Inventory Data Loader detected that the parent site has changed to a new site, and now SMS Inventory Data Loader is trying ...
  48. SMS Inventory Data Loader encountered a SQL Server problem and is stopping the MIF processing thread.%12 Possible cause: ...
  49. SMS Inventory Data Loader failed to compile %1. The failing MOF file has been moved to %2, and the last successfully compiled ...
  50. SMS Inventory Data Loader failed to process the delta MIF file "%1" and has moved it to "%2."%12 Possible cause: The file ...
  51. SMS Inventory Data Loader failed to process the delta MIF file "%1" because the file does not have a corresponding discovery ...
  52. SMS Inventory Data Loader failed to process the file %1 because it is larger than the defined maximum allowable size of %2.%12 ...
  53. SMS Inventory Data Loader failed to read the delta MIF file "%1" and will move the file to the BADMIFs directory.%12 Possible ...
  54. SMS Inventory Data Loader failed to send inventory to the new parent site, but it will retry %1 more times before quitting.%12 ...
  55. SMS Inventory Data Loader has added group %1 to architecture %2. Inventory Data Loader found a group that it had not found ...
  56. SMS Inventory Data Loader has added the architecture %1. SMS Inventory Data Loader found an architecture that it had not ...
  57. SMS Inventory Data Loader has detected a resynchronization request for agent %1. When an agent is specified, the resynchronization ...
  58. SMS Inventory Data Loader has detected that a resource with GUID %1 needs to be resynchronized, but the resource will not ...
  59. SMS Inventory Data Loader has finished processing %1 MIF files and is terminating the MIF file processing thread.%12 Each ...
  60. SMS Inventory Data Loader has quit trying to update inventory after failing 10 times. SMS Inventory Data Loader detected ...
  61. SMS Inventory Data Loader has requested a resynchronization for machine %1. Inventory Data Loader requests resynchronization ...
  62. SMS Inventory Data Loader has requested a resynchronization for site %1. Inventory Data Loader requests resynchronization ...
  63. SMS Inventory Data Loader is going to widen attribute %2 of group %1 from %3 to %4. SMS Inventory Data Loader has received ...
  64. SMS Inventory Data Loader is updating database statistics for all inventory-related tables. By default, statistics are updated ...
  65. SMS Inventory Data Loader requested a resynchronization for machine "%1" because a hardware inventory file was sent without ...
  66. SMS Inventory Processor failed to process inventory RAW file %1.%12 Possible cause: The file might be corrupt. Solution: ...
  67. SMS Inventory Processor failed to process MIF file %1.%12 Possible cause: The MIF file is not formatted correctly. Solution: ...
  68. SMS management point encountered an error when connecting to the database %3 on SQL Server %2. The OLEDB error code was %4. ...
  69. SMS NDS Logon Discovery Manager detected that there is no NetWare NDS redirector installed on the site server. SMS NDS Logon ...
  70. SMS NDS Logon Discovery Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is ...
  71. SMS NDS Logon Discovery Manager failed to read file "%1", which contains the configuration of SMS NDS Logon Server Manager.%12 ...
  72. SMS NDS Logon Discovery Manager failed to update the configuration of SMS NDS Logon Server Manager.%12 Solution: Review the ...
  73. SMS NDS Logon Discovery Manager failed to write file "%1", which contains the configuration of SMS NDS Logon Server Manager.%12 ...
  74. SMS NDS Logon Discovery Manager is beginning to update the configuration of SMS NDS Logon Server Manager. Any changes to ...
  75. SMS NDS Logon Discovery Manager successfully updated file "%1", which contains the configuration of SMS NDS Logon Server ...