%11SMS NW Logon Server Manager failed to read the site control file.%12 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.%0
SMS NW Logon Server Manager failed to complete all of the configuration tasks on NetWare bindery server "%1". These tasks ...
SMS NW Logon Server Manager failed to find a suitable volume on NetWare bindery server "%1" to hold the "SMSLOGON" directory. ...
SMS NW Logon Server Manager failed to initialize, but it will retry in one hour. Possible cause: SMS Inbox Manager is not ...
SMS NW Logon Server Manager failed to modify the system login script on the NetWare bindery server "%1".%12 Possible cause: ...
SMS NW Logon Server Manager failed to read the site control file.%12 Possible cause: The file exists, but it is corrupt. ...
SMS NW Logon Server Manager failed to update the site control file.%12 Possible cause: Low disk space on the drive containing ...
SMS NW Logon Server Manager is beginning a processing cycle for all of the NetWare bindery servers configured for the NetWare ...
SMS NW Logon Server Manager is beginning a processing cycle for NetWare bindery server "%1", which includes: 1. Making this ...
SMS NW Logon Server Manager is unable to create the directory "%1" on the NetWare bindery server "%2".%12 Possible cause: ...