User Guide

SMDR Messages 593
System Messages
103-000150-001
August 29, 2001
Novell Confidential
Manual 99a38 July 17, 2001
SMDR-X-17: An external SMDR failed to respond to the connection request.
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. Visible SMDRs can remain
visible somewhat longer than they are available. When SMDR is unloaded, it
can still be visible to other servers for a short time. Also, a loaded SMDR can
fail to respond to a connection request if the CPU is too busy with higher
priority tasks and cannot process the SMDR request within an allotted time.
Action: Make sure that the SMDR is properly loaded; then retry the operation. If the
problem persists, contact a Novell support provider.
SMDR-X-18: No matching data remains for the given scan parameters.
Source: SMDR.NLM
Explanation: This message is for information only.
SMDR-X-19: An internal error has occurred. No sockets are available for remote
communication. 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 it 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-20: An internal error has occurred. The protocol selected by the redirector
is not available.
Source: SMDR.NLM
Explanation: SMS uses proxy TSAs, loaded on the server, to represent workstations to the
SMS architecture. When a workstation (including Macintosh, DOS,
Windows, UNIX, etc.) registers with the appropriate proxy TSA on the server,
it gives its name and address, and it identifies the underlying protocol.
When a backup engine connects to the proxy TSA, it assumes it has connected
to the actual workstation. However, the proxy TSA informs the backup engine
that it is only a proxy and broadcasts the real workstation address and protocol.
At an underlying level, the SMDR disconnects the proxy TSA and uses the
information it has received to try to connect to the real workstation.