User Guide

590 System Messages
System Messages
103-000150-001
August 29, 2001
Novell Confidential
Manual 99a38 July 17, 2001
SMDR-X-4: An internal error has occurred. The SMDR was unable to allocate a
listening socket. The SMDR will unload.
Source: SMDR.NLM
Possible Cause: The server does not have enough available memory. The SMDR listens for
remote SMDRs requesting local access, and uses a listening socket with the
underlying transport. If no sockets are available, the SMDR cannot recognize
connection requests.
Action: Increase the memory available to the server. See Freeing Server Memory
Temporarily in the Server Operating System Administration Guide.
SMDR-X-5: An internal error has occurred. Insufficient memory is available for SMDR
tables. The SMDR will unload.
Source: SMDR.NLM
Possible Cause: The server does not have enough available memory. When SMS resources
(such as TSAs or SDIs) are loaded on the server, they register with an SMDR.
If the SMDR cannot allocate a table to record these registrations, other SMS
modules (local or remote) will not be able to access SMS resources.
Action: Increase the memory available to the server. See Freeing Server Memory
Temporarily in the Server Operating System Administration Guide.
SMDR-X-6: An internal error has occurred. The connection number to a module is
invalid.
Source: SMDR.NLM
Possible Cause: An internal error has occurred in the program. An SMS resource user
(SBACKUP, for example) is using an obsolete or damaged connection
number. No resources (TSAs or SDIs, for example) can be accessed through
the connection number given.
Action: Report the error to the vendor of the SMS compliant software.
SMDR-X-7: An internal error has occurred. An invalid parameter was passed.
Source: SMDR.NLM
Possible Cause: An internal error has occurred in the program. An SMS resource user
(SBACKUP, for example) passed corrupted data to an SMS routine. There
might be a bug in the program.
Action: Report the error to the vendor of the SMS compliant software.