| Message ID | Severity | Message |
|---|---|---|
|
2100 |
Error |
SMS NDS Logon Discovery 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. |
|
2101 |
Informational |
SMS NDS Logon Discovery Manager is beginning to update the configuration of SMS NDS Logon Server Manager. Any changes to the configuration of the NetWare NDS Logon Discovery method in the SMS Administrator console will now be propagated to SMS NDS Logon Server Manager. |
|
2102 |
Informational |
SMS NDS Logon Discovery Manager successfully updated the configuration of SMS NDS Logon Server Manager. |
|
2103 |
Error |
SMS NDS Logon Discovery Manager failed to update the configuration of SMS NDS Logon Server Manager. Solution: Review the previous status messages to determine the exact reason for the failure. |
|
2104 |
Error |
SMS NDS Logon Discovery Manager failed to read file %1, which contains the configuration of SMS NDS Logon Server Manager. Possible cause: The file %1 exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. 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. |
|
2105 |
Error |
SMS NDS Logon Discovery Manager failed to write file %1, which contains the configuration of SMS NDS Logon Server Manager. Possible cause: Low disk space on the drive containing the file %1. Solution: Make more disk space available on that drive. Possible cause: The file %1 exists, but it is corrupt. Solution: Restore the file from a backup copy, or run SMS Setup and reset the site. 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. |
|
2106 |
Informational |
SMS NDS Logon Discovery Manager successfully updated file %1, which contains the configuration of SMS NDS Logon Server Manager. |
|
2107 |
Informational |
SMS NDS Logon Discovery Manager will instruct SMS NDS Logon Server Manager to configure the following NetWare NDS contexts for the NetWare NDS Logon Discovery method: %1. |
|
2108 |
Warning |
SMS NDS Logon Discovery Manager detected that there is no NetWare NDS redirector installed on the site server. SMS NDS Logon Discovery Manager cannot function 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. |