Message ID | Severity | Message |
---|---|---|
1700 |
Informational |
SMS NW Logon Server Manager successfully modified the system login script on NetWare bindery server %1. |
1701 |
Error |
SMS NW Logon Server Manager failed to modify the system login script on the NetWare bindery server %1. Possible cause: The server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the server is turned on, connected to the network, and functioning properly. Possible cause: SMS NW Logon Server Manager does not have sufficient access rights to remotely administer the server. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the server. Possible cause: Network problems are preventing SMS NW Logon Server Manager from properly accessing the server. Solution: Investigate and correct any problems with your network. |
1702 |
Informational |
SMS NW Logon Server Manager is beginning a processing cycle for all of the NetWare bindery servers configured for the NetWare Bindery Logon Discovery or Client Installation methods. |
1703 |
Informational |
SMS NW Logon Server Manager completed a processing cycle for all of the NetWare bindery servers configured for the NetWare Bindery Logon Discovery or Client Installation methods. |
1704 |
Informational |
SMS NW Logon Server Manager is beginning a processing cycle for NetWare bindery server %1, which includes: 1. Making this server a site system serving the SMS logon point role. 2. Modifying the system login scripts on this server, if instructed to do so by the configuration of the NetWare Bindery Logon Discovery and Client Installation methods. 3. Creating and updating the contents of the “SMSLOGON” directory on this server. |
1705 |
Informational |
SMS NW Logon Server Manager successfully completed a processing cycle for NetWare bindery server %1. |
1706 |
Error |
SMS NW Logon Server Manager failed to complete a processing cycle for NetWare bindery %1. Solution: Review the status messages previously reported by SMS NW Logon Server Manager to determine the exact reasons for this failure. |
1707 |
Error |
SMS NW 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 any problems it has. |
1708 |
Error |
SMS NW Logon Server Manager failed to access NetWare bindery server %1. Possible cause: Server %1 does not exist. Solution: Using the SMS Administrator console, remove server %1 from the lists of servers in the Windows Networking Logon Discovery and/or Client Installation methods. Add the correct server to the lists. Possible cause: The server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the server is turned on, connected to the network, and functioning properly. Possible cause: SMS NW Logon Server Manager does not have sufficient access rights to remotely administer the server. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the server. Possible cause: Network problems are preventing SMS NW Logon Server Manager from properly accessing the server. Solution: Investigate and correct any problems with your network. |
1709 |
Informational |
SMS NW Logon Server Manager will configure the following NetWare bindery servers to use the NetWare Bindery Logon Discovery and/or Client Installation methods: %1. |
1710 |
Informational |
SMS NW Logon Server Manager will configure the following NetWare bindery servers to no longer use the NetWare Bindery Logon Discovery or Client Installation methods: %1. |
1713 |
Warning |
SMS NW Logon Server Manager failed to find a suitable volume on NetWare bindery server %1 to hold the “SMSLOGON” directory. Possible cause: Every volume on the server has less than 50 MB of free space. Solution: Either free up enough space on a volume or manually create the “SMSLOGON” directory on the root directory of a volume. If you manually create the directory, it might have less than 50 MB of free space. |
1714 |
Warning |
SMS NW Logon Server Manager is unable to create the directory %1 on the NetWare bindery server %2. Possible cause: The server is turned off, not connected to the network, or not functioning properly. Solution: Verify that the server is turned on, connected to the network, and functioning properly. Possible cause: SMS NW Logon Server Manager does not have sufficient access rights to remotely administer the server. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to remotely administer the server. Possible cause: Network problems are preventing SMS NW Logon Server Manager from properly accessing the server. Solution: Investigate and correct any problems with your network. |
1715 |
Informational |
SMS NW Logon Server Manager successfully created the directory %1 on NetWare bindery server %2. SMS clients will access this directory during the client discovery and installation process. |
1716 |
Informational |
SMS NW Logon Server Manager detected that site %1 is using NetWare bindery server %2 for NetWare Bindery Logon Discovery and/or Client Installation, but that site %1 has not recently completed a processing cycle for this server. 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 NW Logon Server Manager will remove site %1 from the list of sites that use this server for NetWare Bindery Logon Discovery and Client Installation. |
1717 |
Warning |
SMS NW Logon Server Manager detected that site %1 is using NetWare bindery server %2 for NetWare Bindery Logon Discovery and/or Client Installation, but that site %1 has not completed a processing cycle for this server in over seven days. SMS NW Logon Server Manager will remove site %1 from the list of sites that use this server for NetWare Bindery 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. |
1718 |
Informational |
SMS NW Logon Server Manager determined that no sites are configured to use NetWare bindery server %1 for the NetWare Bindery Logon Discovery or Client Installation methods. SMS NW Logon Server Manager will now configure the server to no longer serve as an SMS logon point for this site. This task includes: 1. Removing the SMS logon point role from the site system %1. 2. Undoing any modifications made by SMS to the system login scripts on the server. 3. Deleting the “SMSLOGON” directory and any directories and files associated with it. |
1719 |
Warning |
SMS NW Logon Server Manager failed to complete all of the configuration tasks on NetWare bindery server %1. These tasks include: 1. Assigning the SMS logon point role to the site system %1. 2. Modifying the system login scripts, if instructed to do so by the configuration of the NetWare Bindery Logon Discovery and Client Installation methods. 3. Creating and updating the “SMSLOGON” directory and the directories and files associated with it. |
1720 |
Warning |
SMS NW Logon Server Manager failed to update the site control file. |
1721 |
Error |
SMS NW Logon Server Manager failed to read the site control file. Possible cause: The 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. Possible cause: The file is being read from 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. 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. |
1723 |
Warning |
SMS NW Logon Server Manager detected that there is no NetWare bindery redirector installed on the site server. SMS NW Logon Server Manager cannot configure NetWare bindery servers for the NetWare Bindery Logon Discovery and Client Installation methods until an appropriate redirector is installed on the site server. Solution: Install an appropriate NetWare bindery redirector on the site server. Please refer to your SMS documentation or the Microsoft Knowledge Base for further information. |
1724 |
Informational |
SMS NW Logon Server Manager detected that the “SMSLOGON” directory is missing from volume %2 on NetWare bindery server %1. Solution: SMS NW Logon Server Manager will automatically recreate the directory now. |
1725 |
Error |
SMS NW Logon Server Manager detected that NetWare bindery server %1 is already being used as an SMS logon point by another SMS site. Solution: Only one SMS site should be configured to use server %1 as an SMS logon point. Using the SMS Administrator console, remove this server from the list of logon points used for the SMS NetWare Bindery Logon Discovery and Installation methods, either for this site or the site that is currently using this server as an SMS logon point. |