| Message ID | Severity | Message |
|---|---|---|
|
2000 |
Informational |
SMS NDS Logon Server Manager successfully modified the container login script for NetWare NDS container %2 in tree %1. |
|
2001 |
Error |
SMS NDS Logon Server Manager failed to modify the container login script for NetWare NDS container %2 in tree %1. Possible cause: SMS NDS Logon Server Manager does not have sufficient access rights to remotely administer the container. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the container. Possible cause: Network problems are preventing SMS NDS Logon Server Manager from properly accessing the container. Solution: Investigate and correct any problems with your network. |
|
2002 |
Informational |
SMS NDS Logon Server Manager is beginning a processing cycle for all of the NetWare NDS containers and volumes configured for the NetWare NDS Logon Discovery or Client Installation methods. |
|
2003 |
Informational |
SMS NDS Logon Server Manager completed a processing cycle for all of the NetWare NDS containers and volumes configured for the NetWare NDS Logon Discovery or Client Installation methods. |
|
2004 |
Informational |
SMS NDS Logon Server Manager is beginning a processing cycle for NetWare NDS container %2 and volume %3 in tree %1, which includes: 1. Making this volume a site system serving the SMS logon point role. 2. Modifying the container login scripts on this container, if instructed to do so by the configuration of the NetWare NDS Logon Discovery and Client Installation methods. 3. Creating and updating the contents of the “SMSLOGON” directory on this volume. |
|
2005 |
Informational |
SMS NDS Logon Server Manager successfully completed a processing cycle for NetWare NDS container %2 and volume %3 in tree %1. |
|
2006 |
Error |
SMS NDS Logon Server Manager failed to complete a processing cycle for NetWare NDS container %2 and volume %3 in tree %1. The processing tasks includes: 1. Making this volume a site system serving the SMS logon point role. 2. Modifying the container login scripts on this container, if instructed to do so by the configuration of the NetWare NDS Logon Discovery and Client Installation methods. 3. Creating and updating the contents of the “SMSLOGON” directory on this volume. Possible cause: SMS NDS Logon Server Manager does not have sufficient access rights to remotely administer the container or volume. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the container or volume. Possible cause: Network problems are preventing SMS NDS Logon Server Manager from properly accessing the container or volume. Solution: Investigate and correct any problems with your network. |
|
2007 |
Error |
SMS NDS Logon Server Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not running or is experiencing a problem. Solution: Use SMS Service Manager, which is invoked from the SMS Administrator console, to verify that SMS Inbox Manager is running; if it is not, restart it. Review the status messages reported by SMS Inbox Manager and correct and problems it is experiencing. |
|
2008 |
Error |
SMS NetWare NDS Logon Server Manager failed to access NetWare NDS volume %3 in tree %1 due to a memory allocation failure. Possible cause: The site server is low on virtual memory or not functioning properly. Solution: Verify that the site server is functioning properly. Stop any processes that are using up all of the virtual memory. If necessary, reboot the site server to free up virtual memory. |
|
2009 |
Informational |
SMS NDS Logon Server Manager will configure NetWare NDS container %2 and volume %3 in tree %1 to use the NetWare NDS Logon Discovery and/or Client Installation methods. |
|
2010 |
Informational |
SMS NDS Logon Server Manager will configure NetWare NDS container %2 and volume %3 in tree %1 to no longer use the NetWare NDS Logon Discovery and/or Client Installation methods. |
|
2016 |
Informational |
SMS NDS Logon Server Manager detected that site %1 is using NetWare NDS container %3 and volume %4 in tree %2 for NetWare NDS Logon Discovery and/or Client Installation, but that site %1 has not recently completed a processing cycle for this container and volume. Possible cause: Site %1 is temporarily out of service. Solution: Ignore this message, but bring site %1 back into service soon. Possible cause: Site %1 was deinstalled. Solution: Ignore this message. Eventually the SMS NDS Logon Server Manager will remove site %1 from the list of sites that use this container and volume for NetWare NDS Logon Discovery and Client Installation. |
|
2017 |
Warning |
SMS NDS Logon Server Manager detected that site %1 is using NetWare NDS container %3 and volume %4 in tree %2 for NetWare NDS Logon Discovery and/or Client Installation, but that site %1 has not completed a processing cycle for this container and volume in over seven days. SMS NDS Logon Server Manager will remove site %1 from the list of sites that use this container and volume for NetWare NDS Logon Discovery and Client Installation. Possible cause: Site %1 is temporarily out of service. Solution: Bring site %1 back into service. Possible cause: Site %1 was deinstalled. Solution: Ignore this message. |
|
2018 |
Informational |
SMS NDS Logon Server Manager determined that no sites are configured to use NetWare NDS container %2 and volume %3 in tree %1 for the NetWare NDS Logon Discovery or Client Installation methods. SMS NDS Logon Server Manager will now configure the container and volume to no longer serve as an SMS logon point for this site. This task includes: 1. Removing the SMS logon point role from this volume. 2. Undoing any modifications made by SMS to the container login scripts for this container. 3. Deleting the “SMSLOGON” directory and any directories and files associated with it from this volume. |
|
2020 |
Warning |
SMS NDS Logon Server Manager failed to update the site control file. Error %1. Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the site control file or the directory containing it. Solution: Restore the file’s permissions or attributes so that this SMS service can access the file. Possible cause: The site control file exists, but it is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\Inboxes\Sitectrl.box\History directory on the site server), or run SMS Setup and reset the current installation. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
|
2021 |
Error |
SMS NDS Logon Server Manager failed to read the site control file. Error %1. Possible cause: Low disk space on the drive containing the site control file. Solution: Make more space available on that drive. Possible cause: The file is being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: Something other than SMS has changed the permissions or attributes of the file or the directory containing it. Solution: Restore the file’s permissions or attributes so that this SMS service can access the file. Possible cause: The site control file is corrupt. Solution: Restore the site control file from a backup copy (kept in the \Sms\Inboxes\Sitectrl.box\History directory on the site server), or run SMS Setup and reset the current installation. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
|
2023 |
Warning |
SMS NDS Logon Server Manager detected that there is no NetWare NDS redirector installed on the site server. SMS NDS Logon Server Manager cannot configure NetWare NDS containers and volumes for the NetWare NDS Logon Discovery and Client Installation methods until an appropriate redirector is installed on the site server. Solution: Install an appropriate NetWare NDS redirector on the site server. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information. |
|
2024 |
Error |
SMS NDS Logon Server Manager detected that NetWare NDS context %1 is already being used as an SMS logon point by another SMS site. Solution: Only one SMS site should be configured to use context %1 as an SMS logon point. Using the SMS Administrator console, remove this context from the list of logon points used for the NetWare NDS Logon Discovery and Installation methods, either for this site or the site that is currently using this context as an SMS logon point. |