User Guide

592 System Messages
System Messages
103-000150-001
August 29, 2001
Novell Confidential
Manual 99a38 July 17, 2001
SMDR-X-13: The SMDR received an encrypted password it could not decode.
Source: SMDR.NLM
Possible Cause: When SMS resource users (such as SBACKUP) try to connect to remote SMS
resources (TSAs or SDIs, for example), the password is encrypted and packed
into an SMSP datagram. If the data is corrupted before it is sent, during
transmission, or after it is received, the decryption routine will not recognize
the data, and the connect attempt will fail.
Action: Try to reconnect. If the problem persists, contact a Novell support provider.
SMDR-X-14: The SMDR was unable to encrypt the password.
Source: SMDR.NLM
Possible Cause: When SMS resource users (such as SBACKUP) try to connect to remote SMS
resources (TSAs or SDIs, for example), the password is encrypted and packed
into an SMSP datagram. If the data is corrupted before it is sent, during
transmission, or after it is received, the decryption routine will not recognize
the data, and the connect attempt will fail.
Action: Try to reconnect. If the problem persists, contact a Novell support provider.
SMDR-X-15: The named TSA is not loaded on the SMDR. Load the TSA; then try again.
Source: SMDR.NLM
Possible Cause: 1. The wrong SMDR name was specified, or the TSA is not loaded. 2. The
TSA you want to connect to is not loaded on the target computer. 3. The name
of the SMDR is the same as the name of the server it is running on.
Action: Load the TSA on the correct SMDR and try the operation again.
SMDR-X-16: The named SMDR is unknown, does not exist, or is not loaded.
Source: SMDR.NLM
Possible Cause: An invalid SMDR name was typed, or one was typed that is outside the SAP
advertising scope and is therefore invisible.
Action: Make sure that the SMDR is loaded and the name is specified correctly.