15.0 DSI Messages
This module contains some messages that are not numbered. These message are listed alphabetically after the numbered messages.
DSI-X-1: An internal error has occurred. DSI cannot load the message file.
Source:
DSI.NLM
Explanation:
The DSI.NLM program was unable to load the DSI.MSG message file.
Action:
Make sure that the server language is set to 4 (English) for the built-in messages, or to a different number to correspond to both of the following:
If the problem persists, contact a Novell® support provider.
DSI-X-2: Insufficient memory is available to get a memory resource tag.
Source:
DSI.NLM
Possible Cause:
Insufficient memory at the server would not allow the installation to run.
DSI-X-3: An internal error has occurred. DSI cannot insert a predefined entry. Error description: description.
Source:
DSI.NLM
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-4: An internal error has occurred. Predefined entry IDs are out of alignment.
Source:
DSI.NLM
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-5: An initialization internal table failure has occurred.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-6: An internal error has occurred. DSI cannot insert a Schema entry. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-7: An internal error has occurred. DSI cannot insert a property value. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-8: An internal error has occurred. Predefined property IDs are out of alignment.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-9: An internal error has occurred. The class definition is too large.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-10: An internal error has occurred. DSI cannot insert a class entry. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-11: An internal error has occurred. DSI cannot insert a class value. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-12: An internal error has occurred. Predefined class IDs are out of alignment.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-14: An internal error has occurred. DSI cannot insert predefined partitions. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-15: An internal error has occurred. DSI cannot get time stamps. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-16: The Directory Services context could not create DDSCONTEXT. Error description: description.
Source:
DSI.NLM
Possible Cause:
Insufficient memory at the server would not allow INSTALL to run.
DSI-X-17: Insufficient memory is available to allocate a buffer. Error description: description.
Source:
DSI.NLM
Possible Cause:
Insufficient memory at the server would not allow INSTALL to run.
DSI-X-18: An internal error has occurred. This version of DSI does not match the version of Directory Services you are using. DSI version: number. Directory Services version: number.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-19: DSI cannot create the Directory database. Error description: description.
Source:
DSI.NLM
Possible Cause:
The volume SYS: might not be mounted.
Possible Cause:
The volume SYS: might be corrupted.
Possible Cause:
The volume SYS: might be out of disk space.
DSI-X-20: The Directory database cannot be opened. Error description: description.
Source:
DSI.NLM
Possible Cause:
The volume SYS: might not be mounted,
Possible Cause:
The volume SYS: might be corrupted.
DSI-X-21: An internal error has occurred. DSI cannot translate a Unicode string to local. You may have a problem with the Unicode translation files. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-23: DSI cannot resolve to the master replica of the partition containing context name. (Error description: description. Make certain that the server containing the master replica of that context is up and on the network before retrying the installation.
Source:
DSI.NLM
Possible Cause:
The server containing the master replica of the context might not be visible to this server, or it might be down. The server containing the master replica is typically the one on which the context was initially created.
Action:
Make sure that the server containing the master replica is running, connected to the network, and visible from workstations. Also, make sure the server you are installing has the proper LAN drivers loaded and is bound to the right network addresses, with the proper frame types.
DSI-X-24: An internal error has occurred. DSI cannot generate key pair for name. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-25: An internal error occurred while DSI was loading system Directory objects.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-26: DSI cannot open the Directory database. Error description: description.
Source:
DSI.NLM
Possible Cause:
The volume SYS: might not be mounted.
Possible Cause:
The volume SYS: might be corrupted.
DSI-X-27: DSI cannot create external reference to server. Error description: description.
Source:
DSI.NLM
Possible Cause:
The DSI NLM program probably lost its connection with the server that contains the master replica of the container context.
Action:
Make sure that the server containing the master replica is on the network. Try reinstalling a couple of more times. If the problem persists, contact a Novell support provider.
DSI-X-28: An internal error has occurred. DSI was unable to add pseudo server values. Error description: description.
Source:
DSI.NLM
Possible Cause:
Memory at the server might be insufficient.
Possible Cause:
Disk space at the server might be insufficient.
Possible Cause:
An internal system error has occurred.
Action:
If the problem persists, contact a Novell support provider.
DSI-X-29: The local Directory Services agent cannot be opened. Error description: description.
Source:
DSI.NLM
Explanation:
The Novell Directory Services database could not be opened and initialized properly.
Possible Cause:
A database corruption has occurred.
Possible Cause:
Traffic on the network might be excessive.
Action:
Check the external network traffic between this server and other servers in the same Directory tree, minimize traffic as much as possible, then retry the installation.
Possible Cause:
An internal system error has occurred.
Action:
If the problem persists, contact a Novell support provider.
DSI-X-30: DSI cannot resolve to the master replica of the partition containing context context. Error description: description.
Source:
DSI.NLM
Possible Cause:
The server containing the master replica of the partition that contains the specified context might not be running.
Action:
Find out which server contains the master replica of the container’s partition. Typically, this will be the first server on which this container was specified during installation. Make sure that the server is running and that it is visible from workstations on the network; then retry the installation
Possible Cause:
A network connection could not be established to that server.
Action:
Establish a connection with the desired server, then retry the installation.
DSI-X-31: An attempt to place a replica of the partition on this server failed. The partition that failed is the one that holds this server’s container object. Error description: description.
Source:
DSI.NLM
Possible Cause:
Traffic on the network might excessive.
Action:
Minimize external network traffic between this server and other servers in the same Directory tree as much as possible; then retry the installation.
Possible Cause:
An internal system error has occurred.
Action:
If the problem persists, contact a Novell support provider.
DSI-X-32: An internal error has occurred. DSI cannot add a partition replica. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-33: An internal error has occurred. DSI cannot create an internal Directory context structure. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-34: An attempt to place the master replica of the new partition on this server failed (Error description: description). The master replica of the new partition is located on server name, and a read/write replica exists on this server. You can change the type of the replica on this server to a master replica later by using the Partition Manager (PARTMGR) utility. The installation should continue normally.
Source:
DSI.NLM
Explanation:
A new partition was created on the server containing the most recent parent of the new context. The new context was created in the new partition; then an attempt was made to migrate that partition so that it would become a local partition (on the new server being installed). The attempt to change the local partition to the master replica and delete the (remote) secondary replica failed.
Possible Cause:
Traffic on the network might be excessive.
Action:
Continue with the installation. After it is completed, change the read/write replica to a master replica. You can then delete the replica on the server identified in the error message. However, this is not absolutely necessary.
DSI-X-35: An NLM version mismatch has occurred. DSI version: number. Directory Services version: number.
Source:
DSI.NLM
Possible Cause:
The DSI.NLM and DS.NLM have different database versions that don’t work together properly.
Action:
Make sure that the INSTALL.NLM, DS.NLM, DSI.NLM, and SERVER.EXE are all from the same software release.
DSI-X-37: DSI cannot find a NetWare 4.x server.
Source:
DSI.NLM
Explanation:
The installation program was unable to find the root server.
Possible Cause:
Traffic on the network traffic might be excessive.
Action:
Minimize external network traffic between this server and other servers in the same Directory tree as much as possible; then retry the installation. If the problem persists, contact a Novell support provider.
Possible Cause:
The server containing the context into which this server is being installed suddenly went down.
Action:
Make sure the server containing the context is running and retry the installation.
DSI-X-39: A call to DSAgentOpenLocal failed. Error description: description.
Source:
DSI.NLM
Explanation:
Novell Directory Services was unable to open the local Directory agent (database handler).
Possible Cause:
Disk space on the server might be insufficient.
Possible Cause:
Traffic on the network might be excessive.
Action:
Minimize external network traffic between this server and other servers in the same Directory tree as much as possible; then retry the installation.
Possible Cause:
An internal error might have occurred.
Action:
If the problem persists, contact a Novell support provider.
DSI-X-40: An internal error has occurred. DSI cannot set the bindery context. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal error might have occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-41: DSI cannot modify the existing NCP server object. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal error might have occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-42: DSI cannot delete the existing NCP server object. Error description: description.
Source:
DSI.NLM
Explanation:
An NCP™ server object that had the same name as the server being installed was found in this context. To complete the installation, that object must be deleted and re-created. An initial attempt at deleting the object was unsuccessful.
Possible Cause:
The object corresponding to the administrator that you logged in as does not have Delete rights in the current context.
Action:
Make sure you have the Supervisor right in the current context (or to the nearest parent to the context) where you are installing. If this is not the case, give yourself Supervisor rights in the context and retry the installation. If the problem persists, contact a Novell support provider.
DSI-X-43: DSI cannot create the NCP server object. Error description: description.
Source:
DSI.NLM
Explanation:
An attempt to create the NCP server object in the context specified for this server was unsuccessful.
Possible Cause:
The object corresponding to the administrator that you logged in as does not have Create rights in the context.
Action:
Make sure you have the Supervisor right in the context (or to the nearest parent to the context) where you are installing. If this is not the case, give yourself the Supervisor right in the context and retry the installation. If the problem persists, contact a Novell support provider.
DSI-X-44: DSI’s attempt to add a new partition timed out.
Source:
DSI.NLM
Explanation:
An attempt to create a new partition for the new context failed. The new partition should have been created on the server containing the master partition for the nearest existing parent context.
Possible Cause:
The server containing the master might have suddenly gone down.
Action:
Make sure that all servers above this one in the tree that contain master partitions are operating.
Possible Cause:
Traffic on the network might be excessive.
Action:
Minimize external network traffic between this server and other servers in the same Directory tree as much as possible; then, retry the installation. If the problem persists, contact a Novell support provider.
DSI-X-45: An internal error has occurred. DSI cannot get the volume ID; you are not logged in to the Directory.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-46: DSI cannot find the local server context. Error description: description.
Source:
DSI.NLM
Explanation:
An attempt to get information from the Directory database failed.
Possible Cause:
File I/O errors might have occurred.
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-47: An internal error has occurred. DSI cannot translate a local string to Unicode. You may have a problem with the Unicode translation files. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-48: An internal error has occurred. The object for volume name cannot be created. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-49: An internal error has occurred. DSI cannot determine the base class from RDN. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-50: DSI cannot create object name. Error description: description. Verify that the context is entered correctly and follows proper containment rules.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-51: An internal error has occurred. DSI cannot create the root partition. Error description: description.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-52: DSI cannot create the Directory database. Error description: description.
Source:
DSI.NLM
Explanation:
An attempt to create the Directory database failed.
Explanation:
The server might have insufficient disk space.
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-53: DSI cannot open the record manager. Error description: description.
Source:
DSI.NLM
Explanation:
An attempt to access the Directory database failed.
Possible Cause:
The Directory database might be locked by another process.
Action:
Unload all other NLM™ programs (such as DSREPAIR) that might be accessing the database; then, retry the installation.
Possible Cause:
An internal system error has occurred.
Action:
If the problem persists, contact a Novell support provider.
DSI-X-54: DSI cannot open the Directory database. Error description: description.
Source:
DSI.NLM
Explanation:
An attempt to access the Directory database failed.
Possible Cause:
The Directory database might be locked by another process.
Action:
Unload all other NLM programs (such as DSREPAIR) that might be accessing the database; then, retry the installation.
Possible Cause:
An internal system error has occurred.
Action:
If the problem persists, contact a Novell support provider.
DSI-X-55: An internal error has occurred. The Directory Services bindery is not open, and must be for the bindery to be upgraded.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider.
DSI-X-56: Bindery upgrade information cannot be saved to file SWITCH.UPG.
Source:
DSI.NLM
Possible Cause:
A file I/O error occurred while the program was writing bindery upgrade information to the SWITCH.UPG Directory file.
DSI-X-57: DSI cannot read a previous bindery object. Error code: code.
Source:
DSI.NLM
Explanation:
An error occurred while the program was attempting to read the old bindery files (SYS:\SYSTEM\NET$OBJ.SYS, SYS:\SYSTEM\NET$PROP.SYS, SYS:\SYSTEM\ NET$VAL.SYS).
Possible Cause:
The bindery files might be corrupted.
Possible Cause:
The volume might be unreadable.
DSI-X-58: DSI cannot add a previous bindery object. Error code: code. Object: name.
Source:
DSI.NLM
Explanation:
An error occurred while the program was adding an old bindery object to the Directory. This object will not be upgraded correctly even though the installation might be completed and even though other objects might be installed correctly. You might have to re-create the object manually later.
Action:
Write down the name of the object that failed, along with the error code. Complete the installation and re-create the object later. Also, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
DSI-X-59: DSI cannot map a previous bindery name to a Directory ID. Error code: code. Bindery object: name.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
DSI-X-62: DSI cannot add a previous bindery property. Error code: code. Object: name. Property: name.
Source:
DSI.NLM
Explanation:
An error occurred while the program was adding an old bindery object to the Directory. This object will not be upgraded correctly even though the installation might be completed and even though other objects might be installed correctly. You might have to re-create the object manually later.
Action:
Write down the name of the object and property that failed, along with the error code. Complete the installation, and re-create the object later. Also, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
DSI-X-63: DSI cannot add a previous bindery group member. Error code: code. Object: name. Property: name. Member: name.
Source:
DSI.NLM
Explanation:
An error occurred while the program was adding an old bindery object to the Directory. This object will not be upgraded correctly even though the installation might be completed and even though other objects might be installed correctly. You might have to re-create the object manually later.
Action:
Write down the name of the object, property, and member that failed along with the error code. Complete the installation, and re-create the object later. If necessary, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
DSI-X-64: DSI cannot write a previous bindery property. Error code: code. Object: name. Property: name.
Source:
DSI.NLM
Explanation:
An error occurred while the program was adding an old bindery object to the Directory. This object will not be upgraded correctly even though the installation might be completed and even though other objects might be installed correctly. You might have to re-create the object manually later.
Action:
Write down the name of the object that failed along with the error code. Complete the installation, and re-create the object later. Also, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
DSI-X-66: DSI cannot get the Directory NCP server object ID. Error code: code. Object: name.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
DSI-X-68: DSI cannot allocate sufficient memory.
Source:
DSI.NLM
Possible Cause:
Insufficient memory at the server would not allow INSTALL to run.
DSI-X-69: DSI cannot get Directory information for previous bindery object name. Error code: code.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
DSI-X-74: DSI cannot read a previous bindery property. Error description: description.
Source:
DSI.NLM
Explanation:
An error occurred while the program tried to read the old bindery files (SYS:\SYSTEM\NET$OBJ.SYS, SYS:\SYSTEM\NET$PROP.SYS, SYS:\SYSTEM\ NET$VAL.SYS).
Possible Cause:
The bindery files might be corrupted.
Possible Cause:
The volume SYS: might be unreadable.
DSI-X-75: DSI cannot read a previous bindery property. Error code: code. Object: name.
Source:
DSI.NLM
Explanation:
An error occurred while the program attempted to read the old bindery files (SYS:\SYSTEM\NET$OBJ.SYS, SYS:\SYSTEM\NET$PROP.SYS, SYS:\SYSTEM\ NET$VAL.SYS).
Possible Cause:
The bindery files might be corrupted.
Possible Cause:
The volume SYS: might be unreadable.
DSI-X-76: DSI cannot read a previous bindery value. Error code: code. Object: name. Property: name.
Source:
DSI.NLM
Explanation:
An error occurred while the program tried to read the old bindery files (SYS:\SYSTEM\NET$OBJ.SYS, SYS:\SYSTEM\NET$PROP.SYS, SYS:\SYSTEM\ NET$VAL.SYS).
Possible Cause:
The bindery files might be corrupted.
Possible Cause:
The volume might be unreadable.
DSI-X-77: DSI cannot read a previous bindery object. Error code: code.
Source:
DSI.NLM
Explanation:
An error occurred while the program attempted to read the old bindery files (SYS:\SYSTEM\NET$OBJ.SYS, SYS:\SYSTEM\NET$PROP.SYS, SYS:\SYSTEM\ NET$VAL.SYS).
Possible Cause:
The bindery files might be corrupted.
Possible Cause:
The volume SYS: might be unreadable.
DSI-X-78: Bindery file SYS:SYSTEM\NET$OBJ.SYS is already open and was not expected to be.
Source:
DSI.NLM
Explanation:
The file NET$OBJ.SYS is in an opened state when it should be closed.
Possible Cause:
Previous errors might have occurred.
Action:
Dismount volume SYS: and remount it. If the problem persists, contact a Novell support provider.
DSI-X-79: Bindery file SYS:SYSTEM\NET$OBJ.SYS cannot be opened.
Source:
DSI.NLM
Explanation:
An error occurred while the program attempted to open the old bindery file (SYS:SYSTEM\NET$OBJ.SYS).
Possible Cause:
The bindery file might not exist or is corrupted.
Possible Cause:
The volume might be unreadable.
DSI-X-80: Directory file SWITCH.UPG cannot be opened.
Source:
DSI.NLM
Possible Cause:
The eDirectory file SWITCH.UPG might be corrupted or unreadable.
DSI-X-81: Some old ID’s in SWITCH.UPG do not match the bindery. You have probably upgraded more than once. You must restore the original (first) SWITCH.UPG before you can downgrade a volume. Even then, some of your trustees, etc. may be irreversibly corrupted.
Source:
DSI.NLM
Possible Cause:
The eDirectory file SWITCH.UPG is out of date with the bindery.
Action:
Delete the file SWITCH.UPG. You will need to re-create trustees on the volumes.
DSI-X-82: DSI cannot switch bindery IDs to Directory Services IDs for volume name. Error code: code.
Source:
DSI.NLM
Possible Cause:
An internal system error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
DSI-X-83: An attempt to upgrade volume name failed because users were logged in. Remove all user connections and try the upgrade again.
Source:
DSI.NLM
Explanation:
A volume cannot be upgraded until all users have logged out of it.
Action:
Remove all connections. Retry the installation.
DSI-X-84: DSI cannot allocate sufficient memory for ID tables.
Source:
DSI.NLM
Possible Cause:
Sufficient memory was not available for INSTALL to run.
DSI-X-86: DSI cannot read the Directory default Supervisor object.
Source:
DSI.NLM
Possible Cause:
The Directory database might be corrupted or unreadable.
DSI-X-87: DSI cannot write the Directory default Supervisor object.
Source:
DSI.NLM
Explanation:
The Directory database could not be written.
DSI-X-88: DSI cannot add attribute NNS domain name to the server context. Error code: code.
Source:
DSI.NLM
Possible Cause:
An internal eDirectory error has occurred.
Action:
Try the operation again. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
DSI-X-89: An attempt to remove an extraneous replica of the new Directory partition replica failed. Error: description. This is not a fatal problem, however, the installation should continue normally. A read/write replica of the partition will exist on server name. You may delete this replica after the installation is complete using the Partition Manager (PARTMGR) utility.
Source:
DSI.NLM
Action:
As stated in the message, you might want to delete the read/write replica after the installation is complete using the Partition Manager or PARTMGR. For information about a specific error code, search the Error Codes online documentation.
DSI-X-90: DSI cannot resolve to the root of the Directory tree. Error description: description. Make certain that a server containing the replica of the root partition is up and connected to the network.
Source:
DSI.NLM
Explanation:
A replica of the root partition for the Directory tree you are trying to install is not visible to this server, or internal errors have occurred.
Action:
Make sure a server containing a replica of the root partition is up. Resolve any network problems that might be present. If this fails, contact a Novell support provider.
DSI-X-91: DSI cannot resolve to the master partition containing the NCP Server object. Error description: description. Make certain that this server is up and connected to the network.
Source:
DSI.NLM
Explanation:
DSI cannot find the NCP Server object for this server in any master Directory partition replica.
Possible Cause:
The server that contains the master partition (which contains the server object) is not operating or is not visible on the network from this server.
Action:
Make sure a server containing the master replica of the partition containing the server object is operating. Resolve any network problems that might be present. If the problem persists, contact a Novell support provider.
DSI-X-92: Directory Services API interface versions do not match
DSI internal interface version is: interface_version
DSI API interface version is: DS_access_version_expected
Directory Services API interface version is: DS_access_version
Source:
DSI.NLM
Explanation:
An incorrect version of one of the listed APIs exists.
Action:
Note the version for each API display, and contact a Novell support provider to find out which version is required.
DSI-X-93: Could not gain access to Directory Services. Either DS.NLM is not loaded or another NLM has already registered with DS. This could be one of DSI.NLM, DSMERGE.NLM, or DSREPAIR.NLM.
Source:
DSI.NLM
Action:
Load the DS.NLM, and retry the operation.
DSI-X-94: An internal error has occurred. DSI unable to timestamp schema. Error description: description.
Source:
DSI.NLM
Explanation:
An internal system error has occurred at the operation noted in the message.
Action:
Note the error code displayed, search the Error Codes online documentation,, and follow the recommended suggestions. If the problem persists, contact a Novell support provider.
DSI-X-95: An internal error has occurred. DSI unable to add server to internal list. Error description: description.
Source:
DSI.NLM
Explanation:
An internal system error has occurred at the operation noted in the message.
Action:
For information about a specific error code, search the Error Codes online documentation.Retry the operation. If the problem persists, contact a Novell support provider.
DSI-X-96: An internal error has occurred. DSI unable to synchronize schema. Error description: description.
Source:
DSI.NLM
Explanation:
An internal system error has occurred at the operation noted in the message.
Action:
For information about a specific error code, search the Error Codes online documentation.Retry the operation. If the problem persists, contact a Novell support provider.
DSI-X-97: An internal error has occurred. DSI unable to get partition root information. Error description: description.
Source:
DSI.NLM
Explanation:
An internal system error has occurred at the operation noted in the message.
Action:
Retry the operation. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
DSI-X-1001: An internal error has occurred. DSI cannot set the bindery services context. Error description: description. Make certain that TTS is enabled before retrying the installation.
Source:
DSI.NLM
Explanation:
An internal system error has occurred at the operation noted in the message. TTS might be disabled because of insufficient disk space.
DSI-X-1001: This server is not backlinked on server: name.
Source:
DSI.NLM
Explanation:
This server participates in replica operations with the server displayed in the message.
Possible Cause:
Novell Directory Services is being removed from the server.
Possible Cause:
Insufficient information exists on the server displayed in the message to properly delete the server object.
Action:
Please try removing this server from the tree at a later time.
DSI-X-1002: The partition name is in a transitional state. The local server is participating in a replica operation that involves this partition. Please try removing this server from the tree at a later time.
Source:
DSI.NLM
Possible Cause:
Novell Directory Services® is being removed from the server.
Action:
Follow the action specified in the message. If the condition persists, contact a Novell support provider.
DSI-X-1003: This server cannot communicate with server name. Please try removing this server from the tree at a later time.
Source:
DSI.NLM
Possible Cause:
Novell Directory Services is being removed from the server.
Action:
Try removing the server from the tree at a later time. If the condition persists, contact a Novell support provider.
DSI-X-1004: Could not change the replica type of the partition name on the server name. Error description description.
Source:
DSI.NLM
Possible Cause:
Novell Directory Services is being removed from the server.
Action:
Make sure the server is operating. Wait a few minutes; then retry the operation. If the error persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
DSI-X-1005: Could not delete one of the namebase files. Error description description.
Source:
DSI.NLM
Possible Cause:
Novell Directory Services is being removed from the server.
DSI-X-1007: Error code beginning Directory operation.
Source:
DSI.NLM
DSI-X-1008: Could not change the replica type of the partition. Error description description.
Source:
DSI.NLM
Explanation:
This condition might exist when Novell Directory Services is being removed from the server.
Action:
For information about a specific error code, search the Error Codes online documentation. Make sure the server is operating. Wait a few minutes; then retry the operation. If the problem persists, contact a Novell support provider.
Error description getting replica information for partition_name. Unable to make necessary replica changes during the removal of Directory Services from this server.
Source:
DSI.NLM
Possible Cause:
Novell Directory Services is being removed from the server.
Action:
Note the error code displayed, search the Error Codes online documentation, and follow the recommended suggestions. If the problem persists, contact a Novell support provider.
Error allocating memory for server certificate.
Source:
DSI.NLM
Explanation:
The server is out of memory.
Error create schema. Error description description
Source:
DSI.NLM
Explanation:
The message indicates the point in the installation process at which the error occurred.
Action:
Note the error code displayed, For information about a specific error code, search the Error Codes online documentation, and follow the recommended suggestions. If the problem persists, contact a Novell support provider.
Error getting server’s public key. Error description description.
Source:
DSI.NLM
Explanation:
The message indicates the point in the installation process at which the error occurred.
Action:
Note the error code displayed, search the Error Codes online documentation, and follow the recommended suggestions. If the problem persists, contact a Novell support provider.
Error getting server’s state. Error description description.
Source:
DSI.NLM
Explanation:
This message indicates the point in the installation process at which the error occurred.
Action:
Note the error code displayed, search the Error Codes online documentation, and follow the recommended suggestions. If the problem persists, contact a Novell support provider.
Error upgrading the schema. Error description description.
Source:
DSI.NLM
Explanation:
The message indicates the point in the installation process at which the error occurred.
Action:
Note the error code displayed, search the Error Codes online documentation, and follow the recommended suggestions. If the problem persists, contact a Novell support provider.
Unable to change the replica type of partition name on server name to master. Error Description description.
Source:
DSI.NLM
Explanation:
The message indicates the point in the installation process at which the error occurred.
Action:
Note the error code displayed, search the Error Codes online documentation, and follow the recommended suggestions. If the problem persists, contact a Novell support provider.
Unable to create the NCP server object. Error description description.
Source:
DSI.NLM
Explanation:
The message indicates the point in the installation process at which the error occurred.
Action:
Note the error code displayed, search the Error Codes online documentation, and follow the recommended suggestions. If the problem persists, contact a Novell support provider.
Unable to get the replica type. Error description description
Source:
DSI.NLM
Explanation:
The message indicates the point in the installation process at which the error occurred.
Action:
Note the error code displayed, search the Error Codes online documentation, and follow the recommended suggestions. If the problem persists, contact a Novell support provider.
Unable to update the schema in this tree. The installation process will continue. Error description description
Source:
DSI.NLM
Explanation:
The installation process was unable to upgrade the tree schema to NetWare® 4.10 or a later version.
Action:
Note the error code displayed, search the Error Codes online documentation, and follow the recommended suggestions. If the problem persists, contact a Novell support provider.