System Center Configuration Manager 2007

  1. SMS NW Logon Installation Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager ...
  2. SMS NW Logon Installation Manager failed to read file "%1", which contains the configuration of SMS NW Logon Server Manager.%12 ...
  3. SMS NW Logon Installation Manager failed to update the configuration of SMS NW Logon Server Manager.%12 Solution: Review ...
  4. SMS NW Logon Installation Manager failed to write file "%1", which contains the configuration of SMS NW Logon Server Manager.%12 ...
  5. SMS NW Logon Installation Manager is beginning to update the configuration of SMS NW Logon Server Manager. Any changes to ...
  6. SMS NW Logon Installation Manager successfully updated file "%1", which contains the configuration of SMS NW Logon Server ...
  7. SMS NW Logon Installation Manager will instruct SMS NW Logon Server Manager to configure the following NetWare bindery servers ...
  8. SMS NW Logon Server Manager completed a processing cycle for all of the NetWare bindery servers configured for the NetWare ...
  9. SMS NW Logon Server Manager detected that NetWare bindery server "%1" is already being used as an SMS Logon Point by another ...
  10. SMS NW Logon Server Manager detected that site "%1" is using NetWare bindery server "%2" for NetWare Bindery Logon Discovery ...
  11. SMS NW Logon Server Manager detected that site "%1" is using NetWare bindery server "%2" for NetWare Bindery Logon Discovery ...
  12. SMS NW Logon Server Manager detected that the "SMSLOGON" directory is missing from volume "%2" on NetWare bindery server ...
  13. SMS NW Logon Server Manager detected that there is no NetWare bindery redirector installed on the site server. SMS NW Logon ...
  14. SMS NW Logon Server Manager determined that no sites are configured to use NetWare bindery server "%1" for the NetWare Bindery ...
  15. SMS NW Logon Server Manager failed to access NetWare bindery server "%1".%12 Possible cause: Server "%1" does not exist. ...
  16. SMS NW Logon Server Manager failed to complete a processing cycle for NetWare bindery "%1". Solution: Review the status messages ...
  17. SMS NW Logon Server Manager failed to complete all of the configuration tasks on NetWare bindery server "%1". These tasks ...
  18. SMS NW Logon Server Manager failed to find a suitable volume on NetWare bindery server "%1" to hold the "SMSLOGON" directory. ...
  19. SMS NW Logon Server Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not ...
  20. SMS NW Logon Server Manager failed to modify the system login script on the NetWare bindery server "%1".%12 Possible cause: ...
  21. SMS NW Logon Server Manager failed to read the site control file.%12 Possible cause: The file exists, but it is corrupt. ...
  22. SMS NW Logon Server Manager failed to update the site control file.%12 Possible cause: Low disk space on the drive containing ...
  23. SMS NW Logon Server Manager is beginning a processing cycle for all of the NetWare bindery servers configured for the NetWare ...
  24. SMS NW Logon Server Manager is beginning a processing cycle for NetWare bindery server "%1", which includes: 1. Making this ...
  25. SMS NW Logon Server Manager is unable to create the directory "%1" on the NetWare bindery server "%2".%12 Possible cause: ...
  26. SMS NW Logon Server Manager successfully created the directory "%1" on NetWare bindery server "%2". SMS clients will access ...
  27. SMS NW Logon Server Manager will configure the following NetWare bindery servers to no longer use the NetWare Bindery Logon ...
  28. SMS NW Logon Server Manager will configure the following NetWare bindery servers to use the NetWare Bindery Logon Discovery ...
  29. SMS Object Replication Manager failed to process SMS Object %1 of Type %2. This Object has been retried %3 times and has ...
  30. SMS Object Replication Manager failed to process SMS Object %1 of Type %2. This Object will be retried %3 times on the next ...
  31. SMS Object Replication Manager failed to process SMS Object changes. These changes will be retried on next processing cycle.%12 ...
  32. SMS Object Replication Manager failed to process SMS Object Replication File %1 as SMS Object %2 of Type %3 referenced object ...
  33. SMS Object Replication Manager failed to process SMS Object Replication File %1. This SMS Object Replication file has been ...
  34. SMS Offer Status Summarizer cannot process a status message because it contains the invalid Advertisement ID "%6". As a result, ...
  35. SMS Offer Status Summarizer cannot process a status message because it does not contain an Advertisement ID. As a result, ...
  36. SMS Offer Status Summarizer cannot process a status message because it has an invalid message ID %1. The message ID must ...
  37. SMS Outbox Monitor took %1 seconds to complete a cycle. This exceeds its configured interval of %2 seconds by %3 seconds.%12 ...
  38. SMS Policy Provider failed to process Machine Settings changes. These changes will be retried on next processing cycle.%12 ...
  39. SMS Policy Provider failed to process Machine Settings for Machine %1. This Machine Settings will be retried on the next ...
  40. SMS Policy Provider successfully created a policy and a policy assignment based on package %1 (%2), program %3 and advertisement ...
  41. SMS Policy Provider successfully updated the policy and the policy assignment that were created from Distribution Point %1 ...
  42. SMS Policy Provider successfully updated the policy and the policy assignment that were created from package %1 (%2), program ...
  43. SMS Replication Manager received files from the "%1" component at a child site, but that component is not enabled at the ...
  44. SMS Scheduler at site %1 has received package %2 version %3 and has instructed the SMS Sender to send the package to the ...
  45. SMS Scheduler does not have an address defined at site "%2" for site "%1". Files cannot be sent from site "%2" to site "%1" ...
  46. SMS Scheduler has data to send to site "%1", and addresses defined at site "%2" for site "%1", but none of them are available ...
  47. SMS Sender encountered errors while sending software distribution package %1 version %2 to site %3, %4 percent of the sending ...
  48. SMS Sender is currently sending software distribution package %1 version %2 to site %3, %4 percent of the sending has already ...
  49. SMS Server Locator Point encountered an error when connecting to its Database. Possible cause: The SQL server site system ...
  50. SMS Site Backup could not connect to the registy on the SQL machine. Aborting the backup operation. Please verify if the ...
  51. SMS Site Backup could not find the registy entries on the SQL machine. SMS SQL Backup service might not be running on the ...
  52. SMS Site Backup could not find the SMS Writer in the list of writers provided by the VSS. Aborting the backup operation. ...
  53. SMS Site Backup could not start the "%1" executable on the local computer.%12 Possible cause: "%1" does not exist in the ...
  54. SMS Site Backup could not start the "%1" executable on the local computer.%12 Possible cause: "%1" is not found in the specified ...
  55. SMS Site Backup could not start the %1 service on site system %2.%12 Possible cause: SMS Site Backup does not have sufficient ...
  56. SMS Site Backup could not start the %1 SMS client application on the local computer.%12 Possible causes: %1 is not in the ...
  57. SMS Site Backup could not stop the "%1" executable on the local computer.%12 Possible cause: "%1" is an interactive Windows ...
  58. SMS Site Backup could not stop the %1 service on site system %2.%12 Possible cause: SMS Site Backup does not have sufficient ...
  59. SMS Site Backup could not stop the %1 SMS client application on the local computer.%12 Possible cause: %1 does not exist ...
  60. SMS Site Backup failed to initialize the VSS services. Aborting the backup operation. Please verify that the VSS services ...
  61. SMS Site Backup failed while trying to copy the files to the destination. Backup operation is not completed. Possible Cause: ...
  62. SMS Site Backup found syntax errors on the following lines:%1 in backup control file. Site backup did not occur.%12 Possible ...
  63. SMS Site Backup found that the SMS SQL Backup service on the SQL machine is currently backing up the SMS database. It cannot ...
  64. SMS Site Backup is ignoring the invalid definition on line %1 of the backup control file. This problem may cause part of ...
  65. SMS Site Backup is ignoring the invalid section starting on line %1 of the backup control file. This problem might cause ...
  66. SMS Site Backup reported that the backup control data ended unexpectedly at line %1. This problem might cause part of the ...
  67. SMS Site Backup task is starting. This task will interact with the windows VSS services and the appropriate writers to create ...
  68. SMS Site Backup was run, but the %1 token had no value. Site backup did not occur.%12 Possible cause: The current SMS site's ...
  69. SMS Site Backup was run, but the backup destination directory ( %1 ) is invalid. Site backup did not occur.%12 Possible cause: ...
  70. SMS Site Backup was unable to back up %1 database %2 to %3.%12 Possible cause: %3 or its directory are not writable. Solution: ...
  71. SMS Site Backup was unable to back up file system object %1 to %2.%12 Possible cause: %1 is not readable, or %2 is not writable. ...
  72. SMS Site Backup was unable to back up file system object %1 to %2.%12 Possible cause: %1 is not readable, or %2 is not writable. ...
  73. SMS Site Backup was unable to back up registry key %1 to %2.%12 Possible cause: SMS Site Backup was unable to connect to ...
  74. SMS Site Backup was unable to initiate command file "%1" .%12 Possible cause: Unable to find command shell to execute this ...
  75. SMS Site Backup was unable to open control file "%1". Site backup did not occur.%12 Possible cause: Wrong name specified ...