63.0 SMDR Messages
These messages are generated by the Storage Management Data Requester (SMDR) Module.
SMDR-X-1: An internal error has occurred. An external SMDR requested a connection that cannot be opened.
Source:
SMDR.NLM
Possible Cause:
An internal error has occurred in the program. The underlying transport was unable to complete the connection transaction due to a network disruption or failure in the protocol driver (for example, SPXS.NLM, etc.).
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-2: An internal error has occurred. The SMDR was unable to provide a thread to service the connection.
Source:
SMDR.NLM
Explanation:
Normally SMDR creates a thread for a new service process for each connection. In this case, the server did not have enough memory for this process.
SMDR-X-3: An internal error has occurred. The SMDR was unable to broadcast a SAP. The SMDR will unload.
Source:
SMDR.NLM
Explanation:
An internal error has occurred in the program. The Service Advertising Protocol (SAP) failed.
Action:
Try bringing down the server, then rebooting it. Reload the SMDR. If the problem persists, contact a Novell support provider.
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.
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.
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.
SMDR-X-8: An internal error has occurred. One or more of the parameters is null or invalid.
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.
SMDR-X-9: The server is unable to allocate sufficient memory.
Source:
SMDR.NLM
SMDR-X-10: An internal error has occurred. The TLI transport underlying SMS has failed.
Source:
SMDR.NLM
Possible Cause:
An internal error has occurred in the TLI transport for the SMDR. The likelihood of this error occurring increases as the number of hops between servers increases. The reason for the failure is internal to the supported protocol (SPX, TCP/IP, or ADSP). Heavy traffic can also contribute to the difficulty.
Action:
Run the backup or restore on a server closer to the target, during off hours. If the problem persists, contact a Novell support provider.
SMDR-X-11: An internal error has occurred. The requested function is not supported.
Source:
SMDR.NLM
Possible Cause:
An internal error has occurred. This error message indicates a software malfunction.
Action:
Report the error to the vendor of the SMS compliant software.
SMDR-X-12: The named module is already registered to SMDR.
Source:
SMDR.NLM
Explanation:
SMS resources (TSAs or SDIs, for example) can be loaded only once per server. Subsequent attempts to load multiple copies will result in this error message. This message is for information only.
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.
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.
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.
Possible Cause:
This error message indicates that the workstation is available only on a protocol not supported by that SMDR, causing the redirection attempt to fail.
Action:
Replace the SMDR with one that supports the needed protocols and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-21: The maximum number of connections allowed through the SMDR (64) has been exceeded.
Source:
SMDR.NLM
Possible Cause:
The SMDR allows a maximum of 64 simultaneous connections.
Action:
Eliminate unneeded connections; then try the operation again.
SMDR-X-22: An internal error has occurred. A handle is tagged invalid or the pointer to the handle is null.
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 software program.
Action:
Report the error to the vendor of the SMS compliant software.
SMDR-X-23: An internal error has occurred. The offset to the end of the field did not reference the correct field ending.
Source:
SMDR.NLM
Possible Cause:
A data format error occurred in the System Independent Data Format (SIDF) data.
Action:
Retry the operation. If the error recurs, check the hardware read-write head, then retry the operation. If the problem persists, the media might be faulty.
SMDR-X-24: An internal error has occurred. Either the list has no more entries or the specified name space type does not exist.
Source:
SMDR.NLM
Possible Cause:
This error indicates that all of the name spaces in the data set have been represented and processed to completion by SMS.
Action:
Report the error to the vendor of the SMS compliant software.
SMDR-X-25: An internal error has occurred. The SIDF data type is corrupted on overflow.
Source:
SMDR.NLM
Possible Cause:
Corrupted data exists in the file or in the tape format.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-26: An internal error has occurred. The SIDF data type is corrupted on underflow.
Source:
SMDR.NLM
Possible Cause:
Corrupted data exists in the file or in the tape format.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-27: An internal error has occurred. The SMDR encountered an invalid field identifier.
Source:
SMDR.NLM
Possible Cause:
Corrupted data exists in the file or in the tape format.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-40: The unassigned number cannot be decoded.
Source:
SMDR.NLM
Possible Cause:
A number has been used internally that could not be decoded.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-45: The SMDR version is incompatible with the OS. The SMDR is unloaded.
Source:
SMDR.NLM
Possible Cause:
SMDR 5.0 works on NetWare 4.1x servers and later. If it is loaded on a NetWare 3.x server, this error might result.
Action:
If this is not the problem, retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-53: The server is unable to allocate sufficient memory.
Source:
SMDR.NLM
Possible Cause:
There is not enough memory to run the operation.
Action:
Increase the memory in the server. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-54: The server is unable to allocate memory-shared memory space.
Source:
SMDR.NLM
Possible Cause:
SMDR 5.0 uses shared memory for IPC. The server was not able to allocate enough space.
Action:
Increase the memory available to the server.
SMDR-X-55: An internal error has occurred. The parameter passed is NULL or not valid.
Source:
SMDR.NLM
Possible Cause:
The parameters passed to the internal function are not valid.
Action:
Report the error to the vendor of the SMS-compliant software using the SMDR.
SMDR-X-56: An internal error has occurred. The path name used by SMDR is invalid.
Source:
SMDR.NLM
Possible Cause:
SMDR uses registering and loading of registered services. The services registered have a different path than the path specified.
Action:
Report the error to the vendor of the SMS-compliant software using the SMDR.
SMDR-X-57: An internal error has occurred. The network address used to connect to the external SMDR is not valid.
Source:
SMDR.NLM
Possible Cause:
The specified address (or its size) was invalid.
Action:
Check the visibility of the remote server using the ping command. If it is visible, retry the operation. If the problem still persists, contact a Novell support provider. If it is not visible, check the network connection and retry the operation.
SMDR-X-58: An internal error has occurred. The service requested is invalid.
Source:
SMDR.NLM
Possible Cause:
This is an internal error that occurs when the service name or the service responder name is invalid.
Action:
Report the error to the vendor of the SMS-compliant software.
SMDR-X-59: An internal error has occurred. The internal structure used to maintain context is corrupted.
Source:
SMDR.NLM
Possible Cause:
Corrupted data exists in the file.
Action:
Restart the SMDR and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-60: The service name requested is not valid or the registry is corrupted.
Source:
SMDR.NLM
Possible Cause:
This is an internal error that occurs when the service name is invalid.
Action:
Restart the SMDR and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-61: An internal error has occurred. The handle is corrupted.
Source:
SMDR.NLM
Possible Cause:
A file handle or a service handle is corrupted.
Action:
Restart the SMDR and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-62: An internal error has occurred. The protocol selected by the requester is not available.
Source:
SMDR.NLM
Possible Cause:
You selected a protocol that is not available on the server.
Action:
Install the supported protocols. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-63: An internal error has occurred. The service registered is not valid.
Source:
SMDR.NLM
Possible Cause:
Services can be registered with the SMDR using the interface. The services must be present in an SMS-compliant format; otherwise, the error is reported to the screen.
Action:
Report the error to the vendor of the SMS-compliant service provider.
SMDR-X-64: An internal error has occurred. One or more data structures are corrupted.
Source:
SMDR.NLM
Possible Cause:
The internal data structures maintained by the SMDR became corrupted.
Action:
Restart the SMDR and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-65: An internal error has occurred. The requested function is not supported.
Source:
SMDR.NLM
Possible Cause:
The function you asked for is not supported.
Action:
Retry the operation using a different function. If the problem persists, contact a Novell support provider.
SMDR-X-66: An internal error has occurred. The network address for the local host cannot be obtained.
Source:
SMDR.NLM
Possible Cause:
An error occurred while obtaining the information from the local host.
Action:
Check the network configuration of the server. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-67: An internal error has occurred. The requested service type is not available.
Source:
SMDR.NLM
Possible Cause:
The service type you requested is not registered with the SMDR.
Action:
Register the required service using the specified interface. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-68: Unassigned error has occurred.
Source:
SMDR.NLM
Possible Cause:
This error code is not used in the current version of the SMDR.
Action:
Not applicable.
SMDR-X-69: An internal error has occurred. The command issued to the listener is invalid.
Source:
SMDR.NLM
Possible Cause:
An unknown command has been sent to the SMDR listener.
Action:
Check the commands that can be sent to the SMDR listeners. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-70: An internal error has occurred. No protocols or services are registered.
Source:
SMDR.NLM
Possible Cause:
No protocols or services are registered with the SMDR.
Action:
Configure the correct protocols and services. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-71: An internal error has occurred. The maximum limit has been registered. No more protocols or services can be registered.
Source:
SMDR.NLM
Possible Cause:
SMDR has a limit of 16 services and 8 protocols that can be registered. The maximum has been reached.
Action:
Retry registering the services or protocols after removing some of the entries. If the problem persists, contact a Novell support provider.
SMDR-X-72: An internal error has occurred. Access to the locked data structure or other objects failed.
Source:
SMDR.NLM
Possible Cause:
Access to some of the internal members is mutually exclusive. The data structure is locked before it is updated. This error indicates that the operation has failed.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-73: An internal error has occurred. The transport underlying SMS has failed.
Source:
SMDR.NLM
Possible Cause:
Either the connection to a remote host was lost, or there was a problem in the TLI interface of the server.
Action:
Reconnect to the remote server and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-74: An internal error has occurred. No protocols are available for communication.
Source:
SMDR.NLM
Possible Cause:
No protocols are available for the SMDR to communicate with other SMDRs in the network.
Action:
Retry the operation after configuring the required protocols in the server (IPX and/or IP). If the problem persists, contact a Novell support provider.
SMDR-X-75: An internal error has occurred. The configuration file or requested file is not found.
Source:
SMDR.NLM
Possible Cause:
SMDR maintains the configuration in a file at sys:\etc\sms\smdr.cfg. Though the error indicates that the file is not available, this is not an error. SMDR creates this file if it is not found. Also, the service may have requested an unknown file.
Action:
Restart the SMDR, or type load smdr new. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-76: An internal error has occurred. Could not create scratch file for an internal buffer.
Source:
SMDR.NLM
Possible Cause:
SMDR could not create a scratch file. This file is created internally for data buffers, and in this case, the file could not be created.
Action:
Check your rights when you logged in. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-77: An internal error has occurred. Reading an object from NDS or a file failed.
Source:
SMDR.NLM
Possible Cause:
A connection to the remote host was lost abruptly while reading or retrieving data from it.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-78: An internal error has occurred. Could not write an object to NDS or write to a stream.
Source:
SMDR.NLM
Possible Cause:
A connection to the remote host was lost abruptly while reading or retrieving data from it.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-79: An internal error has occurred. Attempted to seek past the file size made.
Source:
SMDR.NLM
Possible Cause:
A problem occurred while buffering data into the file maintained internally.
Action:
Restart the SMDR and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-80: An internal error has occurred. The file used for the internal buffer could not be closed.
Source:
SMDR.NLM
Possible Cause:
The file handle of the internal file could not be closed. This is for information only.
Action:
The system automatically retrieves lost resources.
SMDR-X-81: An internal error has occurred. An attempt to delete the NDS object or delete a file has failed.
Source:
SMDR.NLM
Possible Cause:
You might not have rights.
Action:
Check the rights. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-82: An internal error has occurred. The stream handle is invalid.
Source:
SMDR.NLM
Possible Cause:
The handle to the stream is invalid. The server may be overloaded.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-83: An internal error has occurred. The internal buffer overflowed.
Source:
SMDR.NLM
Possible Cause:
An internal error occurred when the buffer overflowed. The server might be overloaded or was not able to allocate enough memory.
Action:
Restart the SMDR and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-84: An internal error has occurred. The data in the buffer is less than expected data.
Source:
SMDR.NLM
Possible Cause:
A mismatch occurred between the size of the buffer data and what was expected.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-85: An internal error has occurred. The buffer accessed internally is locked.
Source:
SMDR.NLM
Possible Cause:
The locks to the buffer could not be acquired. This is for information only.
Action:
Restart and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-86: The required entry for protocols or services is not found. Register the appropriate protocol or service.
Source:
SMDR.NLM
Possible Cause:
SMDR listens on some protocols that can be configured. The SMDR has been requested to connect by an unregistered protocol (not registered with the SMDR), or it is rquested to provide a service that is not registered with it.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-87: An attempt was made to register an entry that already exists.
Source:
SMDR.NLM
Possible Cause:
A duplication of entries was attempted. This is for information only.
Action:
None required.
SMDR-X-88: An internal error has occurred. The required entry in the registry is not active or is being removed.
Source:
SMDR.NLM
Possible Cause:
SMDR maintains a list of internal tables (shared data structures) of protocols, services, requesters, responders, etc. The appropriate table does not contain the required entry, or the entry has been removed.
Action:
Check the configuration and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-89: An internal error has occurred. The table for registration is full.
Source:
SMDR.NLM
Possible Cause:
The maximum size of the table has been reached. The maximum is 8 service types, 16 services, and 8 protocols and responders.
Action:
Remove any unnecessary entries and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-90: An internal error has occurred. The index used to access the registry is not valid.
Source:
SMDR.NLM
Possible Cause:
An internal error has occurred with the data structures.
Action:
Restart the SMDR and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-91: An internal error has occurred. Could not obtain the hosts network address.
Source:
SMDR.NLM
Possible Cause:
The network connection may not be configured properly.
Action:
Check the network connection and the server configuration.
SMDR-X-92: An internal error has occurred. Could not connect to the specified endpoint.
Source:
SMDR.NLM
Possible Cause:
The specified remote SMDR could not be connected to. The problem could be heavy network traffic, or an incorrect server configuration.
Action:
Check the network connection and server configuration. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-93: The connection to the remote host is lost. The remote host might have disconnected.
Source:
SMDR.NLM
Possible Cause:
This message is for information only.
Action:
Try again.
SMDR-X-94: An error occurred while disconnecting from the remote host.
Source:
SMDR.NLM
Possible Cause:
The remote host might have exited abruptly without clearing the connections. The remote system might have abended causing the communication to be lost.
Action:
Retry after checking the remote server and its configuration. In most cases, restarting the system and the SMDRs solves the problem.
SMDR-X-95: An internal error has occurred. The underlying transport used by SMS has failed.
Source:
SMDR.NLM
Possible Cause:
The TLI being used by the SMDR encountered a problem.
Action:
Check the server configuration. Restart the SMDR and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-96: An internal error has occurred. Could not spawn thread.
Source:
SMDR.NLM
Possible Cause:
The server might be heavily overloaded and could not allow any new threads to be spawned by the SMDR.
Action:
Reduce the server load by unloading unwanted modules. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-97: An internal error has occurred. The requested module could not be loaded.
Source:
SMDR.NLM
Possible Cause:
SMDR dynamically loads the services, protocols, requesters, and responders as specified in its internal tables. These tables are configurable. The specified entry might not be present in the table to load, or it might not be present on the server at the specified location.
Action:
Restart the SMDR and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-98: An internal error has occurred. A module could not be unloaded.
Source:
SMDR.NLM
Possible Cause:
SMDR dynamically unloads the services, protocols, requesters, and responders as specified in its internal tables. These tables are configurable. The specified entry might not be present in the table to load, or it might not be present on the server at the specified location.
Action:
Restart SMDR and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-99: An internal error has occurred. No data was found.
Source:
SMDR.NLM
Possible Cause:
There was no data found in the SMDR IPC buffers. This is for information only.
Action:
None required.
SMDR-X-100: An internal error has occurred. The underlying transport of SMS could not connect to the requested host.
Source:
SMDR.NLM
Possible Cause:
The remote host is not visible or could not be connected due to some protocol differences between the server and the remote host.
Action:
Check the server configurations of both the servers and retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-101: An internal error has occurred. The underlying transport of SMS would not connect to the remote host.
Source:
SMDR.NLM
Possible Cause:
There was an error binding to the remote host.
Action:
Check the network configuration and the server load. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-102: An internal error has occurred. The bindery to search the targets could not be read.
Source:
SMDR.NLM
Possible Cause:
The SAP tables could not be read for the SMDR entries.
Action:
Check the SAP configuration on the server and also check the network connectivity. The SAP table could also be out of date. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-103: An internal error has occurred. The handle to the function or transport layer is invalid.
Source:
SMDR.NLM
Possible Cause:
The TLI conneciton has not been properly opened.
Action:
Check the network configuration for the server. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-104: The name of the entity registered is too long. Try a shorter name.
Source:
SMDR.NLM
Possible Cause:
The maximum limit for the name of the registered entity has been reached. The limit is 120 characters.
Action:
Retry the operation using a smaller name. If the problem persists, contact a Novell support provider.
SMDR-X-105: An internal error has occurred. The encryption used is not known.
Source:
SMDR.NLM
Possible Cause:
There may be no encryter or the encryter is invalid. Also, an external authentication scheme possibly is being used.
Action:
Restart and retry the operation. Check the encryter service or if the service is internal to the SMDR. If the problem persists, contact a Novell support provider.
SMDR-X-106: An internal error has occurred. The Directory Services Application Programming Interfaces (DSAPIs) could not be imported. Load the NLM that exports the directory services APIs.
Source:
SMDR.NLM
Possible Cause:
SMDR uses Novell eDirectory for name resolution with DSAPI. It dynamically imports the required symbols which could not be done. The required programs might not be available with the server.
Action:
Retry the operation after loading the required eDirectory NLM programs. If the problem persists, contact a Novell support provider.
SMDR-X-107: An internal error has occurred. The file or transport stream could not be opened.
Source:
SMDR.NLM
Possible Cause:
There is a problem with the TLI interface.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-108: An internal error has occurred. The listener could not be started.
Source:
SMDR.NLM
Possible Cause:
The listener could not be started. The server may be overloaded, or another internal error occurred.
Action:
Retry the operation. If the problem persists, note the scenario and contact a Novell support provider.
SMDR-X-109: An internal error has occurred. The underlying transport failed to accept the connection.
Source:
SMDR.NLM
Possible Cause:
An internal TLI error occurred.
Action:
Retry the operation. If the problem persists, note the scenario and contact a Novell support provider.
SMDR-X-110: An internal error has occurred. The transport layer’s events could not be polled.
Source:
SMDR.NLM
Possible Cause:
An internal error has occurred. This error is no longer used.
Action:
None required.
SMDR-X-111: An internal error has occurred. A symbol could not be dynamically bound. The symbol may be incorrect.
Source:
SMDR.NLM
Possible Cause:
An error occurred when trying to bind a symbol.
Action:
Check that the required modules are installed. Retry the operation. If the problem persists, contact a Novell support provider.
SMDR-X-112: An internal error has occurred. A symbol could not be unbound.
Source:
SMDR.NLM
Possible Cause:
An error occurred when trying to unbind a symbol.
Action:
Retry the operation. If the problem persists, contact a Novell support provider.