-601 | 0xFFFFFDA7 | ERR_NO_SUCH_ENTRY | The specified object is not found on the server replying to the request. The context could be a factor, or the client doesn't have sufficient rights to the object. |
-602 | 0xFFFFFDA6 | ERR_NO_SUCH_VALUE | The requested attribute value is not found on the server replying to the request. The client may not have sufficient rights to the attribute. |
-603 | 0xFFFFFDA5 | ERR_NO_SUCH_ATTRIBUTE | The requested attribute is not found on the server replying to the request. The client may not have sufficient rights to the attribute. |
-604 | 0xFFFFFDA4 | ERR_NO_SUCH_CLASS | The specified schema class is not found on the server replying to the request. |
-605 | 0xFFFFFDA3 | ERR_NO_SUCH_PARTITION | The specified partition doesn't exist on the server replying to the request. There may be communication problems between servers in the DS tree. |
-606 | 0xFFFFFDA2 | ERR_ENTRY_ALREADY_EXISTS | Trying to create, rename, or restore an object when an object with the same name already exists at the same context level of the tree. |
-607 | 0xFFFFFDA1 | ERR_NOT_EFFECTIVE_CLASS | Attempting to create an object using a schema class definition that is not an effective class. |
-608 | 0xFFFFFDA0 | ERR_ILLEGAL_ATTRIBUTE | Attempting to add an attribute that's not listed as an optional or mandatory attribute in the object's class. |
-609 | 0xFFFFFD9F | ERR_MISSING_MANDATORY | Trying to create an object that's missing one or more mandatory attributes. For example, a User object must have its Surname attribute defined when being created. (You can use Schema Manager to determine which attributes are mandatory for a given schema class; see Chapter 7). |
-610 | 0xFFFFFD9E | ERR_ILLEGAL_DS_NAME | The specified object name is incorrectly formatted or is longer than 256 characters. (Because DS stores all characters using Unicode representation, the maximum internal object name length is 512 characters.) |
-611 | 0xFFFFFD9D | ERR_ILLEGAL_CONTAINMENT | Attempting to add an object that violates the schema's containment rules. |
-612 | 0xFFFFFD9C | ERR_CANT_HAVE_MULTIPLE_VALUES | Attempting to add more than one attribute value to a single-value attribute. If you want to replace the value, you need to either delete the old value first or overwrite it with the new. |
-613 | 0xFFFFFD9B | ERR_SYNTAX_VIOLATION | Trying to modify an attribute by using data that doesn't conform to the syntax specified for the attribute. For example, your API call specified SYN_INTEGER instead of SYN_STRING . |
-614 | 0xFFFFFD9A | ERR_DUPLICATE_VALUE | Attempting to add the same value-attribute combination to an object. For example, a User object already has a telephone number of 555-1212, and you're trying to add another telephone number whose value is also 555-1212. |
-615 | 0xFFFFFD99 | ERR_ATTRIBUTE_ALREADY_EXISTS | Attempting to create a schema attribute that already exists. |
-616 | 0xFFFFFD98 | ERR_MAXIMUM_ENTRIES_EXIST | Unable to add a new object to the DS database because the maximum number of entries (16,777,215,) in the object database has been reached. (Applies to DS 6 and DS 7 only.) |
-617 | 0xFFFFFD97 | ERR_DATABASE_FORMAT | The record structure of the DS database doesn't match the structure expected by the version of the DS module being used. The database cannot be used. If you ever encounter this error, it will be while the DS module is trying to open the database or when you're attempting to abort a DS operation, such as partitioning. |
-618 | 0xFFFFFD96 | ERR_INCONSISTENT_DATABASE | The DS module is unable to open the DS database. This can be due to unexpected data returned from the local database to the DS module or due to a problem with the database. This error may be rectified using DSRepair, by running a local database repair. |
-619 | 0xFFFFFD95 | ERR_INVALID_COMPARISON | Attempting to compare two attributes whose syntax is not comparable (for example, one is numeric and the other is text string) or using an invalid compare syntax. |
-620 | 0xFFFFFD94 | ERR_COMPARISON_FAILED | The two attribute values specified for comparison are not the same. |
-621 | 0xFFFFFD93 | ERR_TRANSACTIONS_DISABLED | No DS request can be processed because the server's TTS has been disabled. |
-622 | 0xFFFFFD92 | ERR_INVALID_TRANSPORT | The server does not support the specified type of transport. |
-623 | 0xFFFFFD91 | ERR_SYNTAX_INVALID_IN_NAME | The naming attribute specified for the new schema class definition is not of the character string type. |
-624 | 0xFFFFFD90 | ERR_REPLICA_ALREADY_EXISTS | Trying to place a replica on a server that is already holding a (non-subref) replica of the same partition. |
-625 | 0xFFFFFD8F | ERR_TRANSPORT_FAILURE | Unable to communicate with the target server. This error is generally a result of the target server being down, a LAN/WAN outage , or some sort of routing problems. |
-626 | 0xFFFFFD8E | ERR_ALL_REFERRALS_FAILED | The local server has no objects that match the request, and all attempts to tree-walk to other servers to find the objects have failed. This error is not the same as ERR_NO_REFERRALS (-634). This error could be an indirect result of SAP/RIP filtering on the network. |
-627 | 0xFFFFFD8D | ERR_CANT_REMOVE_NAMING_VALUE | Cannot remove the attribute value that's flagged as a naming attribute of an object. You can use Schema Manager to determine the naming attributes of a particular object class. |
-628 | 0xFFFFFD8C | ERR_OBJECT_CLASS_VIOLATION | Trying to create an object without specifying its base class. |
-629 | 0xFFFFFD8B | ERR_ENTRY_IS_NOT_LEAF | Attempting to delete an object containing subordinates , such as an organizational unit (OU) that still has objects in it. |
-630 | 0xFFFFFD8A | ERR_DIFFERENT_TREE | The request was sent to a server that is not located in the current DS tree. |
-631 | 0xFFFFFD89 | ERR_ILLEGAL_REPLICA_TYPE | The server responding to the request doesn't have a replica with the required replica type to service the request. For example, the server has a Read/Only replica and not a Read/Write replica. This error is generally due to an application bug. |
-632 | 0xFFFFFD88 | ERR_SYSTEM_FAILURE | An unknown and unexpected error. This error can be a result of memory corruption in the server or an inconsistent DS database. Restarting the server or using DSRepair may resolve the problem. |
-633 | 0xFFFFFD87 | ERR_INVALID_ENTRY_FOR_ROOT | Trying to restore an object as [Root] but the object's base class is not "Top" . Or attempting to assign an object as a partition root object but the object's base class is not of "container class" . |
-634 | 0xFFFFFD86 | ERR_NO_REFERRALS | The local server has no objects that match the request and has no referrals on which to search for the object. This error is not the same as ERR_ALL_REFERRALS_FAILED (-626). This error could be an indirect result of SAP/RIP filtering on the network. |
-635 | 0xFFFFFD85 | ERR_REMOTE_FAILURE | Unable to connect to another server. Unlike error ERR_TRANSPORT_FAILURE (-625), this is not an error due to the network. Rather, it is due to the requester using an invalid server handle or unsupported NCP call, or it is due to the remote server returning an invalid reply. Therefore, this is mostly an application-related error. |
-636 | 0xFFFFFD84 | ERR_UNREACHABLE_SERVER | A partition operation can't be performed because one or more of the servers in the replica ring is unreachable due to a ERR_TRANSPORT_FAILURE (-625) error. |
-637 | 0xFFFFFD83 | ERR_PREVIOUS_MOVE_IN_PROGRESS | Cannot process the current request because a previous object move operation is still in progress. |
-638 | 0xFFFFFD82 | ERR_NO_CHARACTER_MAPPING | Making a request with an object or property name that contains illegal characters, such as a control character, a comma, a colon, a semicolon, a slash, a backslash, a question mark, an asterisk, or a tilde. This error may also be due to the DS module being unable to map the supplied name to its Unicode representation. (This is the same as error DSERR_ILLEGAL_NAME [-239].) |
-639 | 0xFFFFFD81 | ERR_INCOMPLETE_AUTHENTICATION | An error happened during the final phase of the DS authentication process. This is generally due to LAN/WAN hardware or software as it is suggestive of packet corruption. |
-640 | 0xFFFFFD80 | ERR_INVALID_CERTIFICATE | An invalid security certificate was specified. (Applies to NetWare 5 and higher.) |
-641 | 0xFFFFFD7F | ERR_INVALID_REQUEST | The request was invalid or unsupported by the running version of the DS module. |
-642 | 0xFFFFFD7E | ERR_INVALID_ITERATION | The iteration handle in a message fragment of a DS request is invalid. This could be a result of packet corruption. |
-643 | 0xFFFFFD7D | ERR_SCHEMA_IS_NONREMOVABLE | Attempting to delete a base schema class flagged as nonremovable. |
-644 | 0xFFFFFD7C | ERR_SCHEMA_IS_IN_USE | Attempting to delete a schema class definition that still contains an object using that definition. |
-645 | 0xFFFFFD7B | ERR_CLASS_ALREADY_EXISTS | Trying to add a schema class definition that already exists in the schema. |
-646 | 0xFFFFFD7A | ERR_BAD_NAMING_ATTRIBUTES | Trying to add a schema class definition whose naming attribute is not a valid attribute for the class. |
-647 | 0xFFFFFD79 | ERR_NOT_ROOT_PARTITION | Attempting to perform a partitioning operation on a nonpartition root object. |
-648 | 0xFFFFFD78 | ERR_INSUFFICIENT_STACK | Internal error. The server ran out of stack. |
-649 | 0xFFFFFD77 | ERR_INSUFFICIENT_BUFFER | The server ran out of memory or the calling application didn't provide sufficient buffer space for the request. |
-650 | 0xFFFFFD76 | ERR_AMBIGUOUS_CONTAINMENT | Attempting to create a schema class definition that contained an ambiguous containment rule. |
-651 | 0xFFFFFD75 | ERR_AMBIGUOUS_NAMING | Attempting to create a schema class definition that contained an ambiguous containment name. |
-652 | 0xFFFFFD74 | ERR_DUPLICATE_MANDATORY | Attempting to create a schema class definition that contained a duplicate mandatory attribute name. |
-653 | 0xFFFFFD73 | ERR_DUPLICATE_OPTIONAL | Attempting to create a schema class definition that contained a duplicate optional attribute name. |
-654 | 0xFFFFFD72 | ERR_PARTITION_BUSY | Cannot process the request because the specified partition is currently involved in a partition operation or the replica's state is not On . |
-655 | 0xFFFFFD71 | ERR_MULTIPLE_REPLICAS | Attempting to add a new replica attribute value to the partition root object that already has a replica attribute with the same value. |
-656 | 0xFFFFFD70 | ERR_CRUCIAL_REPLICA | An illegal partition operation was requested (such as trying to add a Read/Write replica to a server holding the Master replica of the same partition). |
-657 | 0xFFFFFD6F | ERR_SCHEMA_SYNC_IN_PROGRESS | The request can't be processed because the schema sync process is in progress. |
-658 | 0xFFFFFD6E | ERR_SKULK_IN_PROGRESS | The request can't be processed because the skulk process is in progress. |
-659 | 0xFFFFFD6D | ERR_TIME_NOT_SYNCHRONIZED | The time between the source and target server is not synchronized. Consequently, partition operation can't be performed. |
-660 | 0xFFFFFD6C | ERR_RECORD_IN_USE | NDS tried to purge a DS database record that's still in use. Running DSRepair may resolve this error. |
-661 | 0xFFFFFD6B | ERR_DS_VOLUME_NOT_MOUNTED | Internal error. Logically, you should never encounter this error because it is used by the operating system to indicate that the DS module can't be loaded at this time because the SYS volume is not yet mounted. |
-662 | 0xFFFFFD6A | ERR_DS_VOLUME_IO_FAILURE | Internal error. An I/O operation attempted on the SYS volume failed, possibly because the volume is not yet mounted. |
-663 | 0xFFFFFD69 | ERR_DS_LOCKED | Can't process request because the DS database is locked (or closed); this is analogous to the bindery being locked. The database may be locked by DSRepair while it is doing a repair or it may be closed because the server's TTS is shut down. In some cases, this error is due to a UNI_HANDLE_MISMATCH (-497) error from the Unicode module. |
-664 | 0xFFFFFD68 | ERR_OLD_EPOCH | Trying to modify objects on a server that is using an older epoch of the data. This can happen during either a replica sync process or a schema sync process. This is a transitory error and will disappear when the sync process updates the epoch on the servers. (An epoch is an arbitrary time and date that marks the beginning of an event. In the context of DS schema, a schema epoch defines the time at which the schema was last updated or changed.) |
-665 | 0xFFFFFD67 | ERR_NEW_EPOCH | Trying to modify objects on a server that is using a newer epoch of the data. This can happen during either a replica sync process or a schema sync process. This is a transitory error and will disappear when the sync process updates the epoch on the servers. |
-666 | 0xFFFFFD66 | ERR_INCOMPATIBLE_DS_VERSION | Unable to synchronize with the target server due to either incompatible DS module versions between the source and target servers or the version of the DS module on the source server being on the target server's restricted version list. On NetWare, you can check a server's restricted DS version list by using the "NDS do not synchronize with" console SET command. |
-667 | 0xFFFFFD65 | ERR_PARTITION_ROOT | Attempting to perform a DS operation on a partition root object when it is not allowed. For example, you tried to delete a container root object without first merging it with its parent partition. |
-668 | 0xFFFFFD64 | ERR_ENTRY_NOT_CONTAINER | Attempting to perform a partition operation on a leaf object. |
-669 | 0xFFFFFD63 | ERR_FAILED_AUTHENTICATION | Using an invalid password to authenticate into DS. |
-670 | 0xFFFFFD62 | ERR_INVALID_CONTEXT | Internal error. A request was made using an invalid context handle. The server's task and connection management table may be corrupted. Reloading the DS module may help resolve the problem. |
-671 | 0xFFFFFD61 | ERR_NO_SUCH_PARENT | Attempting to modify an object whose parent object cannot be found. |
-672 | 0xFFFFFD60 | ERR_NO_ACCESS | The requester doesn't have sufficient rights to the requested information. For example, you're trying to perform a partitioning operation but you don't have the necessary rights to the specified partition root objects. |
-673 | 0xFFFFFD5F | ERR_REPLICA_NOT_ON | Cannot process the request because the specified partition's replica state is not On . You can check the current state of the replica by using DSRepair. |
-674 | 0xFFFFFD5E | ERR_INVALID_NAME_SERVICE | The specified name service is not available or is not supported. |
-675 | 0xFFFFFD5D | ERR_INVALID_TASK | Internal server error. A request of an NCP connection was made, using a task ID of 0. The server's task and connection management table may be corrupted. Reloading the DS module may help resolve the problem. |
-676 | 0xFFFFFD5C | ERR_INVALID_CONN_HANDLE | Internal server error. A request was made of an NCP connection, using an invalid NCP connection handle or an invalid task ID. The server's task and connection management table may be corruption. Reloading the DS module may help resolve the problem. |
-677 | 0xFFFFFD5B | ERR_INVALID_IDENTITY | Internal DS error. A request was made using an invalid NDS identity. The server's identity tables may be corrupted. Reloading the DS module may help resolve the problem. |
-678 | 0xFFFFFD5A | ERR_DUPLICATE_ACL | Attempt to add an access control list (ACL) attribute value to an object that already has the same ACL attribute value and trustee. |
-679 | 0xFFFFFD59 | ERR_PARTITION_ALREADY_EXISTS | Trying to create a partition on a server that already has the specified object as a partition root object. |
-680 | 0xFFFFFD58 | ERR_TRANSPORT_MODIFIED | A communication inconsistency occurred when attempting to connect to a remote server. The initial attempt resulted in a -625 error. However, a subsequent retry succeeded by re-negotiating the IPX checksum, IPX packet signatures, or maximum packet size. This error is generally caused by faults in the LAN/WAN hardware or software components . |
-681 | 0xFFFFFD57 | ERR_ALIAS_OF_AN_ALIAS | Trying to create an alias of an Alias object. |
-682 | 0xFFFFFD56 | ERR_AUDITING_FAILED | Internal error due to DS auditing operations. This error may be a result of an attempt to audit an object that has not been flagged for auditing or a failure to reset the auditing files. |
-683 | 0xFFFFFD55 | ERR_INVALID_API_VERSION | An API call specified a version number that is not supported by the currently running DS module. The application may have been created using an outdated library. |
-684 | 0xFFFFFD54 | ERR_SECURE_NCP_VIOLATION | The source server or client attempted to authenticate with a remote server, using IPX packet signatures, but the remote server doesn't support packet signing. |
-685 | 0xFFFFFD53 | ERR_MOVE_IN_PROGRESS | The specified object is currently involved in a DS object move operation; the object has either Move Obituary or Inhibit Move Obituary . (For more information about obits, see Chapter 6.) |
-686 | 0xFFFFFD52 | ERR_NOT_LEAF_PARTITION | Attempting to perform a move subtree partition operation, but the specified object is not a leaf partition. You must first merge any subordinate partition root object with its parent partition. |
-687 | 0xFFFFFD51 | ERR_CANNOT_ABORT | The current partition operation can't be aborted because it has progressed past a specific turnaround state. Typically when a change replica type, split partition, or merge partition operation has gone beyond its initial phase (for example, state RS_CRT_0 or replica state 4 during a change replica type operation), the operation cannot be aborted. The same is true during a move subtree operation when any of the move tree-related obits are changed to Notified , OK To Purge , or Purgeable ; the operation can't be aborted. |
-688 | 0xFFFFFD50 | ERR_CACHE_OVERFLOW | An internal error from the cache used by the NDS replica synchronization process. |
-689 | 0xFFFFFD4F | ERR_INVALID_SUBORDINATE_COUNT | The subordinate object count in the object's database record doesn't match the number of presently found child objects. A repair local database operation using DSRepair may resolve the error. |
-690 | 0xFFFFFD4E | ERR_INVALID_RDN | The RDN specified in the object's database record doesn't match the name found in the object's naming attribute. Or the specified object's parent object, as identified by the database record, is invalid. A repair local database operation using DSRepair may resolve the error. |
-691 | 0xFFFFFD4D | ERR_MOD_TIME_NOT_CURRENT | The modification timestamp of an object attribute is newer than the modification timestamp found in the object's database record. A repair local database operation using DSRepair may resolve the error. |
-692 | 0xFFFFFD4C | ERR_INCORRECT_BASE_CLASS | The base class of an object doesn't match the base class specification found in the object's database record. A repair local database operation using DSRepair may resolve the error. |
-693 | 0xFFFFFD4B | ERR_MISSING_REFERENCE | The specified object has an attribute value that references another object in the local database, but the referenced object doesn't have a reference attribute indicating that the specified object references it. A repair local database operation using DSRepair may resolve the error. |
-694 | 0xFFFFFD4A | ERR_LOST_ENTRY | The NDS replica synchronization process tried to update an object on the target server, but the target server has not yet received the object. This is a transitory error because the NDS replica synchronization process will re-send the lost object before trying to update it. |
-695 | 0xFFFFFD49 | ERR_AGENT_ALREADY_REGISTERED | Trying to load the DS when another module has already registered with the operating system as an NDS agent. |
-696 | 0xFFFFFD48 | ERR_DS_LOADER_BUSY | The DS loader was busy when a request was made to unload and reload the DS module. You should try the operation again at a later time. |
-697 | 0xFFFFFD47 | ERR_DS_CANNOT_RELOAD | Trying to unload and reload the DS module when one or more DS-dependent modules (such as DSRepair) are still loaded. |
-698 | 0xFFFFFD46 | ERR_REPLICA_IN_SKULK | Attempting to start the NDS replica synchronization process with a target server when the target server is busy synchronizing with another server. This is a transitory error and the NDS replica synchronization process will reschedule. |
-699 | 0xFFFFFD45 | ERR_FATAL | An internal error. If this happens during normal DS operations, it is generally transitory. However, if the error persists, you can try reloading the DS module or restarting the server. If the standard repair methods (such as performing a local database repair by using DSRepair) do not resolve the error, you need to open a call with Novell. |
-700 | 0xFFFFFD44 | ERR_OBSOLETE_API | An API request that's no longer supported by the running version of the DS module. This is the opposite of error ERR_NOT_IMPLEMENTED (-714). |
-701 | 0xFFFFFD43 | ERR_SYNCHRONIZATION_DISABLED | The NDS replica synchronization process is unable to sync with the target server as its inbound replica synchronization is disabled using the SET DSTRACE=!D or SET DSTRACE=!DI command. If this is the case, the message "*SKULKER: SYNCHRONIZATION DISABLED" is displayed on the target server's DSTrace screen. You can re-enable the inbound sync by using the SET DSTRACE=!E or SET DSTRACE=!EI command. The error can also be due to the local server's outbound replica synchronization process being disabled. If this is the case, the message "*SYNC: SYNCHRONIZATION DISABLED" is displayed on the local server's DSTrace screen. You can re-enable the outbound sync by using the SET DSTRACE=!E or SET DSTRACE=!EO command. This error may also be a result of the schema synchronization process being disabled. If this is the case, you need to re-enable the schema synchronization by using the SET DSTRACE=!SI1 or SET DSTRACE=!SO1 command. |
-702 | 0xFFFFFD42 | ERR_INVALID_PARAMETER | Attempt to register for an unsupported DS event or to unregister an unregistered event. This error is due to logic faults in NLM applications. |
-703 | 0xFFFFFD41 | ERR_DUPLICATE_TEMPLATE | This is an internal error that is expected during schema initialization. |
-704 | 0xFFFFFD40 | ERR_NO_MASTER_REPLICA | Unable to locate the Master replica of the partition. The server holding the Master may be unavailable. |
-705 | 0xFFFFFD3F | ERR_DUPLICATE_CONTAINMENT | This is an internal error that is expected during schema initialization. |
-706 | 0xFFFFFD3E | ERR_NOT_SIBLING | The objects specified in a merge entries operation are not siblings to one another. A repair local database operation using DSRepair may resolve the error. |
-707 | 0xFFFFFD3D | ERR_INVALID_SIGNATURE | The packet signature is invalid. This may be due to packet corruption. |
-708 | 0xFFFFFD3C | ERR_INVALID_RESPONSE | The data received by the DS module is invalid or contains unexpected information. This may be due to packet corruption. |
-709 | 0xFFFFFD3B | ERR_INSUFFICIENT_SOCKETS | All available NCP sockets are currently in use. This is a transitory error. However, if the error persists, you can increase the number of sockets by using SPXCONFG.NLM . |
-710 | 0xFFFFFD3A | ERR_DATABASE_READ_FAIL | Unable to read the DS database. |
-711 | 0xFFFFFD39 | ERR_INVALID_CODE_PAGE | The currently running DS module does not support the code page used by the operating system. |
-712 | 0xFFFFFD38 | ERR_INVALID_ESCAPE_CHAR | The currently running DS module does not support the specified escape character. An escape character tells DS to treat the following character as a regular text character, as opposed to whatever meaning that character might normally have for DS. |
-713 | 0xFFFFFD37 | ERR_INVALID_DELIMITERS | The currently running DS module does not support the specified delimiters. (DS uses dots, . , as delimiters in object names .) |
-714 | 0xFFFFFD36 | ERR_NOT_IMPLEMENTED | The currently running DS module does not support the requested operation or function. You need to upgrade to a newer version of DS module. This is the opposite of error ERR_OBSOLETE_API (-700). |
-715 | 0xFFFFFD35 | ERR_CHECKSUM_FAILURE | The NDS checksum in the request packet is invalid. This error is generally caused by faults in the LAN/WAN hardware or software components. NDS checksumming is generally not recommended because the current version of the DS module uses a transport-independent CRC checking for all traffic between servers. You can enable NDS checksumming by using the SET DSTRACE=CHECKSUM command or disable it with the SET DSTRACE=NOCHECKSUM command. Note that NDS checksumming is not supported on all frame types, such as Novell's Ethernet 802.3. |
-716 | 0xFFFFFD34 | ERR_CHECKSUMMING_NOT_SUPPORTED | Attempting to negotiate an NCP connection with a server that doesn't support NDS checksumming, while the source server has NDS checksumming enabled. |
-717 | 0xFFFFFD33 | ERR_CRC_FAILURE | The NDS CRC (different from the NDS checksum) in the request packet is invalid. This error is generally caused by faults in the LAN/WAN hardware or software components. |
-718 | 0xFFFFFD32 | ERR_INVALID_ENTRY_HANDLE | The file handle for the object entry database file is invalid. |
-719 | 0xFFFFFD31 | ERR_INVALID_VALUE_HANDLE | The file handle for the attribute value database file is invalid. |
-720 | 0xFFFFFD30 | ERR_CONNECTION_DENIED | NDS outbound traffic or NCP connection to a remote server is not permitted because of WAN Traffic Manager (WANMan) restriction policies. |
-721 | 0xFFFFFD2F | ERR_NO_SUCH_FEDERATION_LINK | Reserved error code for federated partition implementation. |
-722 | 0xFFFFFD2E | ERR_OP_SCHEMA_MISMATCH | A mismatch in the operational schema was detected. |
-723 | 0xFFFFFD2D | ERR_STREAM_NOT_FOUND | The specified stream file doesn't exist. This could be a result of no database files being found in the DIB directory. |
-724 | 0xFFFFFD2C | ERR_DCLIENT_UNAVAILABLE | The DSA is not running. |
-725 | 0xFFFFFD2B | ERR_MASV_NO_ACCESS | Cannot access Mandatory Access Control Service. (Applies to NetWare 5 and higher.) |
-726 | 0xFFFFFD2A | ERR_MASV_INVALID_REQUEST | The Mandatory Access Control Service received an invalid request. (Applies to NetWare 5 and higher.) |
-727 | 0xFFFFFD29 | ERR_MASV_FAILURE | A failure condition was detected in the Mandatory Access Control Service. (Applies to NetWare 5 and higher.) |
-728 | 0xFFFFFD28 | ERR_MASV_ALREADY_EXISTS | The Mandatory Access Control Service is already running. (Applies to NetWare 5 and higher.) |
-729 | 0xFFFFFD27 | ERR_MASV_NOT_FOUND | The Mandatory Access Control Service is not running. (Applies to NetWare 5 and higher.) |
-730 | 0xFFFFFD26 | ERR_MASV_BAD_RANGE | The Mandatory Access Control Service data is out of range. (Applies to NetWare 5 and higher.) |
-731 | 0xFFFFFD25 | ERR_VALUE_DATA | The value received is invalid. |
-732 | 0xFFFFFD24 | ERR_DATABASE_LOCKED | The database files are locked. |
-733 | 0xFFFFFD23 | ERR_DATABASE_ALREADY_EXIST | Internal error. (Currently unused.) |
-734 | 0xFFFFFD22 | ERR_DATABASE_NOT_FOUND | Internal error. (Currently unused.) |
-735 | 0xFFFFFD21 | ERR_NOTHING_TO_ABORT | Cannot abort the specified NDS operation because it has already completed or has been aborted. |
-736 | 0xFFFFFD20 | ERR_END_OF_STREAM | End-of-file encountered while accessing the stream file. |
-737 | 0xFFFFFD1F | ERR_NO_SUCH_TEMPLATE | The specified user template doesn't exist. |
-738 | 0xFFFFFD1E | ERR_SAS_LOCKED | The SAS database is locked. (Applies to NetWare 5 and higher.) |
-739 | 0xFFFFFD1D | ERR_INVALID_SAS_VERSION | The currently running SAS module does not support the version information in the SAS request. (Applies to NetWare 5 and higher.) |
-740 | 0xFFFFFD1C | ERR_SAS_ALREADY_REGISTERED | The SAS module is already running. (Applies to NetWare 5 and higher.) |
-741 | 0xFFFFFD1B | ERR_NAME_TYPE_NOT_SUPPORTED | The specified object type is not supported. |
-742 | 0xFFFFFD1A | ERR_WRONG_DS_VERSION | The specified DS version is not supported. |
-743 | 0xFFFFFD19 | ERR_INVALID_CONTROL_FUNCTION | The specified control function is not supported. |
-744 | 0xFFFFFD18 | ERR_INVALID_CONTROL_STATE | The specified control function state is not supported. |
-745 | 0xFFFFFD17 | ERR_CACHE_IN_USE | Trying to use the data cache while it is in use by another process. |
-746 | 0xFFFFFD16 | ERR_ZERO_CREATION_TIME | The specified object has a zero creation timestamp. A repair local database operation using DSRepair may resolve the error. |
-747 | 0xFFFFFD15 | ERR_WOULD_BLOCK | The specified API call is blocked (that is, control is not returned to the calling client until the execution of the API function is completed). |
-748 | 0xFFFFFD14 | ERR_CONN_TIMEOUT | The connection has timed out. |
-749 | 0xFFFFFD13 | ERR_TOO_MANY_REFERRALS | The tree-walking process has reached the maximum number of servers that the local server can contact to retrieve an object's information. |
-750 | 0xFFFFFD12 | ERR_OPERATION_CANCELLED | The specified DS operation has been (successfully) cancelled. |
-751 | 0xFFFFFD11 | ERR_UNKNOWN_TARGET | The specified server is unknown. |
-752 | 0xFFFFFD10 | ERR_GUID_FAILURE | The SGUID (set global unique identifier) module can't process the request, or can't find the required GUID. (Applies to NetWare 5 and higher.) |
-753 | 0xFFFFFD0F | ERR_INCOMPATIBLE_OS | The software module can't be loaded on this version of the operating system. |
-754 | 0xFFFFFD0E | ERR_CALLBACK_CANCEL | The execution of the callback routine has been cancelled. |
-755 | 0xFFFFFD0D | ERR_INVALID_SYNCHRONIZATION_DATA | Invalid data was found in the data sent by the NDS replica synchronization process. |
-756 | 0xFFFFFD0C | ERR_STREAM_EXISTS | The specified stream file already exists. |
-757 | 0xFFFFFD0B | ERR_AUXILIARY_HAS_CONTAINMENT | Internal error. (Currently unused.) |
-758 | 0xFFFFFD0A | ERR_AUXILIARY_NOT_CONTAINER | Internal error. (Currently unused.) |
-759 | 0xFFFFFD09 | ERR_AUXILIARY_NOT_EFFECTIVE | Internal error. (Currently unused.) |
-760 | 0xFFFFFD08 | ERR_AUXILIARY_ON_ALIAS | Internal error. (Currently unused.) |
-761 | 0xFFFFFD07 | ERR_HAVE_SEEN_STATE | The server received notification of the state of a partition operation that it is involved in, but it had previously received the same state information. This may occur during normal operation and may be a transitory error. |
-762 | 0xFFFFFD06 | ERR_VERB_LOCKED | Internal error. (Currently unused.) |
-763 | 0xFFFFFD05 | ERR_VERB_EXCEEDS_TABLE_LENGTH | Internal error. (Currently unused.) |
-764 | 0xFFFFFD04 | ERR_BOF_HIT | Internal error. (Currently unused.) |
-765 | 0xFFFFFD03 | ERR_EOF_HIT | Indicates no more data on recursive search. This is not a real error condition. |
-766 | 0xFFFFFD02 | ERR_INCOMPATIBLE_REPLICA_VER | Internal error. (Currently unused.) |
-767 | 0xFFFFFD01 | ERR_QUERY_TIMEOUT | Internal error. (Currently unused.) |
-768 | 0xFFFFFD00 | ERR_QUERY_MAX_COUNT | Internal error. (Currently unused.) |
-769 | 0xFFFFFCFF | ERR_DUPLICATE_NAMING | Internal error. (Currently unused.) |
-770 | 0xFFFFFCFE | ERR_NO_TRANS_ACTIVE | Internal error. The database expected a transaction to be active prior to executing an operation, but the calling code did not start one. You need to report this to Novell. |
-771 | 0xFFFFFCFD | ERR_TRANS_ACTIVE | Internal error. The database did not expect a transaction to be active prior to executing an operation. You need to report this to Novell. |
-772 | 0xFFFFFCFC | ERR_ILLEGAL_TRANS_OP | Internal error. This error is returned when an update operation is attempted against the database within the context of a read-only transaction. You need to report this to Novell. |
-773 | 0xFFFFFCFB | ERR_ITERATOR_SYNTAX | A malformed request was sent to the NDS iterator. |
-774 | 0xFFFFFCFA | ERR_REPAIRING_DIB | A request is rejected because the DIB directory is currently being repaired. |
-775 | 0xFFFFFCF9 | ERR_INVALID_OID_FORMAT | Failed object identifier (OID) check during a schema extension operation. If this error is encountered during schema synchronization, you should run DSRepair on the servers involved. |
-776 | 0xFFFFFCF8 | ERR_DS_AGENT_CLOSING | A request is rejected because the DIB directory is being closed. |
-777 | 0xFFFFFCF7 | ERR_SPARSE_FILTER_VIOLATION | Attempting to add invalid DirXML replication filters. Or attempting to change to attributes of a DS entry that is contained in filtered replicas on that server, but the filtered replicas do not contain these attributes. (Applies to eDirectory 8.5 and above.) |
-778 | 0xFFFFFCF6 | ERR_VPVECTOR_CORRELATION_ERR | Internal error. (Not currently used; applies to eDirectory 8.5 and above.) |
-779 | 0xFFFFFCF5 | ERR_CANNOT_GO_REMOTE | A DS request was made but cannot be serviced by any of the local replicas; however, the application cannot connect to any of the referred servers because it is logged in to and authenticated to the local server only. The application must perform a full login to the tree and not just a local login. |
-780 | 0xFFFFFCF4 | ERR_REQUEST_NOT_SUPPORTED | The requested action is not supported by the current version of NDS/eDirectory. |
-781 | 0xFFFFFCF3 | ERR_ENTRY_NOT_LOCAL | The object is not found in any of the local replicas. |
-782 | 0xFFFFFCF2 | ERR_ROOT_UNREACHABLE | Unable to contact [Root] for tree-walking purposes. |
-783 | 0xFFFFFCF1 | ERR_VRDIM NOT_INITIALIZED | A driver is requested to start via the ConsoleOne administration snap-in, but the DirXML interface module (VRDIM) is not currently loaded. This error appears only when the VRDIM has been explicitly unloaded. |
-784 | 0xFFFFFCF0 | ERR_WAIT_TIMEOUT | This error is returned from a routine when a specified time limit for a timeout value has been exceeded. This is not necessarily an error condition. |
-785 | 0xFFFFFCEF | ERR_DIB_ERROR | An unknown error was encountered in the DIB subsystem. |
-786 | 0xFFFFFCEE | ERR_DIB_IO_FAILURE | An unknown I/O error was encountered in the DIB subsystem. |
-787 | 0xFFFFFCED | ERR_ILLEGAL_SCHEMA ATTRIBUTE | The specified attribute is invalid. |
-788 | 0xFFFFFCEC | ERR_SCHEMA_PARTITION | An unknown error was detected in the schema partition. |
-789 | 0xFFFFFCEB | ERR_INVALID_TEMPLATE | The error is returned when the subjectDN (the object that will be granted a right) in an ACL template is not one of [Self] , [Root] , [Public] , or [Creator] . (An ACL template is the ACL of a class definition that is automatically added to the object of that class when it is created.) |
-790 | 0xFFFFFCEA | ERR_OPENING_FILE | The operating system returns this error to eDirectory when eDirectory made a call to the operating system to open a file. This error may be transitory. Restarting DS or the server may resolve the problem. |
-791 | 0xFFFFFCE9 | ERR_DIRECT_OPENING_FILE | The operating system returns this error to eDirectory when eDirectory made a call to the operating system to open a file in direct I/O mode. This error may be transitory. Restarting DS or the server may resolve the problem. |
-792 | 0xFFFFFCE8 | ERR_CREATING_FILE | The operating system returns this error to eDirectory when eDirectory made a call to the operating system to create a file. This error may be transitory. Restarting DS or the server may resolve the problem. |
-793 | 0xFFFFFCE7 | ERR_DIRECT_CREATING_FILE | The operating system returns this error to eDirectory when eDirectory made a call to the operating system to create a file in direct I/O mode. This error may be transitory. Restarting DS or the server may resolve the problem. |
-794 | 0xFFFFFCE6 | ERR_READING_FILE | The operating system returns this error to eDirectory when eDirectory is reading from a file. This error may be transitory. Restarting DS or the server may resolve the problem. |
-795 | 0xFFFFFCE5 | ERR_DIRECT_READING_FILE | The operating system returns this error to eDirectory when eDirectory is reading from a file in direct I/O mode. This error may be transitory. Restarting DS or the server may resolve the problem. |
-796 | 0xFFFFFCE4 | ERR_WRITING_FILE | The operating system returns this error to eDirectory when eDirectory is writing to a file. This error may be transitory. Restarting DS or the server may resolve the problem. |
-797 | 0xFFFFFCE3 | ERR_DIRECT_WRITING_FILE | The operating system returns this error to eDirectory when eDirectory is writing to a file in direct I/O mode. This error may be transitory. Restarting DS or the server may resolve the problem. |
-798 | 0xFFFFFCE2 | ERR_POSITIONING_IN_FILE | The operating system returns this error to eDirectory when eDirectory is positioning within a file. This error may be transitory. Restarting DS or the server may resolve the problem. |
-799 | 0xFFFFFCE1 | ERR_GETTING_FILE_SIZE | The operating system returns this error to eDirectory when eDirectory is getting the file size. This error may be transitory. Restarting DS or the server may resolve the problem. |
-800 through -6000 | 0xFFFFFCE0 through 0xFFFFE890 | | These are not DS error codes; they are used by other Novell products. |
-6001 | 0xFFFFE88F | ERR_TRUNCATING_FILE | The operating system returns this error to eDirectory when eDirectory is truncating a file. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6002 | 0xFFFFE88E | ERR_PARSING_FILE_NAME | The operating system returns this error to eDirectory when eDirectory is parsing a filename. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6003 | 0xFFFFE88D | ERR_CLOSING_FILE | The operating system returns this error to eDirectory when eDirectory is closing a file. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6004 | 0xFFFFE88C | ERR_GETTING_FILE_INFO | The operating system returns this error to eDirectory when eDirectory is getting file information (such as file attributes). This error may be transitory. Restarting DS or the server may resolve the problem. |
-6005 | 0xFFFFE88B | ERR_EXPANDING_FILE | The operating system returns this error to eDirectory when eDirectory is expanding a file. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6006 | 0xFFFFE88A | ERR_GETTING_FREE_BLOCKS | The operating system returns this error to eDirectory when eDirectory is getting free disk blocks from the file system. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6007 | 0xFFFFE889 | ERR_CHECKING_FILE_EXISTENCE | The operating system returns this error to eDirectory when eDirectory is checking to see whether a file exists. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6008 | 0xFFFFE888 | ERR_DELETING_FILE | The operating system returns this error to eDirectory when eDirectory is deleting a file. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6009 | 0xFFFFE887 | ERR_RENAMING_FILE | The operating system returns this error to eDirectory when eDirectory is renaming a file. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6010 | 0xFFFFE886 | ERR_INITIALIZING_IO_SYSTEM | The operating system returns this error to eDirectory when eDirectory is initializing to perform file I/O operations. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6011 | 0xFFFFE885 | ERR_FLUSHING_FILE | The operating system returns this error to eDirectory when eDirectory is flushing data from the system cache to disk. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6012 | 0xFFFFE884 | ERR_SETTING_UP_FOR READ | The operating system returns this error to eDirectory when eDirectory is setting up to perform file read operations. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6013 | 0xFFFFE883 | ERR_SETTING_UP_FOR WRITE | The operating system returns this error to eDirectory when eDirectory is setting up to perform file write operations. This error may be transitory. Restarting DS or the server may resolve the problem. |
-6014 | 0xFFFFE882 | ERR_OLD_VIEW | A consistent snapshot of the database could not be maintained for the requested operation. This error could occur if a query has been posed against a very large database and the query results in a scan search. If the search runs for more than 40 minutes, the database aborts the operation and returns this error. It is also possible for transactions that have run for less than 40 minutes to be aborted if the database is in a state where it is trying to reclaim roll-back space (for example, if the rollback log file has grown too large). The 40-minute timeout value is not changeable at this time. |
-6015 | 0xFFFFE881 | ERR_SERVER_IN_SKULK | The local server can't send outbound data to another server because the target server is currently receiving inbound data (either from the local server or another server in the same replica ring). This is a transitory error, and the NDS replica synchronization process will resolve it. |
-6016 | 0xFFFFE880 | ERR_RETURNING_PARTIAL_RESULTS | An error has occurred during a search or read operation, and the entry being returned as the result contains partial values. This is a nonfatal error. The client might attempt to retrieve and use the partial results that have been returned. This error is specifically returned during a lookup of dynamic group memberships when the search fails for some reason (perhaps due to being unable to contact some servers). |
-6017 | 0xFFFFE87F | ERR_NO_SUCH_SCHEMA | The requested schema definition does not exist. You should check to ensure that the schema synchronization process runs without error. |
-6018 | 0xFFFFE87E | ERR_SERIAL_NUM_MISMATCH | This can happen when an incremental DS backup (of the roll-forward log [RLF] files) is being restored and the serial number of the database stored in the incremental backup's header does not match the serial number of the database. Generally, this means that an attempt is being made to restore an incremental backup from another database. |
-6019 | 0xFFFFE87D | ERR_BAD_RFL_DB_SERIAL_NUM | This can happen when the serial number of the database stored in the header of the RFL file that is being restored does not match the serial number of the database. Generally, this means that an attempt is being made to restore an RFL file from another database. |
-6020 | 0xFFFFE87C | ERR_BAD_ RFL_SERIAL_NUM | This can happen when the serial number of the database stored in the header of the RFL file that is being restored does not match the serial number of the database or the prior RFL file. Generally, this means that an attempt is being made to restore an RFL file from another database. |
-6021 | 0xFFFFFE7B | ERR_INVALID_FILE_SEQUENCE | This can happen when the sequence number or incremental backup ID of the RFL file that is being restored does not match the expected number stored in the database. |
-6022 | 0xFFFFE87A | ERR_RFL_TRANS_GAP | During recovery (after a server crash) or during a database restore operation, gaps in the transactions recorded in the log were detected due to one or more RFL files having been damaged. Using DSRepair may rectify the problem. |
-6023 | 0xFFFFE879 | ERR_BAD_RFL_FILE_NUMBER | The RFL file number desired does not match the file number recorded in the RFL file's header. Specifying the wrong RFL file during a database restore operation causes this error. |
-6024 | 0xFFFFE878 | ERR_RFL_FILE_NOT_FOUND | A RFL file required for the database restore could not be found in the NDS.RFL directory. You should use one of the methods described in the "Locating the DIB" section in Chapter 3 to check for the existence of RFL files. You should restore missing files from backup if possible. |
-6025 | 0xFFFFE877 | ERR_BACKUP_ACTIVE | The requested action cannot be performed while a database backup is running. |
-6026 | 0xFFFFE876 | ERR_RFL_DEVICE_FULL | The disk/volume hosting the RFL files is full. |
-6027 | 0xFFFFE875 | ERR_UNSUPPORTED_VERSION | The file format of the backup data set is not supported by the running version of the DS module. This is caused by trying to restore a newer version of the eDirectory database by using an older version of the DS module. |
-6028 | 0xFFFFE874 | ERR_MUST_WAIT_CHECKPOINT | An operation was requested at a time when eDirectory had to force a checkpoint. (A checkpoint operation is eDirectory flushing all dirty cache buffers to disk.) |
-6029 | 0xFFFFE873 | ERR_ATTR_MAINT_IN_PROGRESS | This transitory error condition is reported when a query is made against one or more attributes that are currently being maintained (that is, reorganized for more optimal storage). |
-6030 | 0xFFFFE872 | ERR_ABORT_TRANSACTION | A problem has been encountered during an update operation. Because of the nature of the problem, the active update transaction cannot be committed and has been rolled back. |
-6031 | 0xFFFFE871 | ERR_SETTING_FILE_INFO | This error is returned if eDirectory is unable to change a file's attributes. This error is returned on NetWare if the Rename Inhibit flag of a file cannot be cleared. Other platforms do not currently return this error. |
-6032 | 0xFFFFE870 | ERR_REPLICA_RING_CHANGED | The local database is unaware of replica ring changes that occurred after the database was restored. This error may be due to some RFL files not being processed during a restore or a server being forcibly removed from the replica ring and the ring being altered while the server is down. |
-6033 | 0xFFFFE86F | ERR_NOT_PARTITION_ROOT | A partition join operation has occurred, and the local database is unaware of it. An object that was once a partition root is no longer a partition root. This error may be due to some RFL files not being processed during a restore or a server being forcibly removed from the replica ring and the ring being altered while the server is down. |
-6034 | 0xFFFFE86E | ERR_SERVER_NOT_UP_TO DATE | A discrepancy was found when checking the transitive vectors. The restored database is missing data that the other servers in the replica ring expect to be there. This error may be due to some RFL files not being processed during a restore. |
-6035 | 0xFFFFE86D | ERR_INCONSISTENT_BACKUP | Invalid data has been detected in the backup set during a database restore operation. This is usually the result of a checksum error detected in the backup set during block verification. |
-6036 | 0xFFFFE86C | ERR_NO_SUCH_INDEX | If this error is reported while the database is being upgraded by a new version of eDirectory, it is an informational error. This is because the operationally required indexes are unavailable until the upgrade completes. However, if this error happens under other circumstances, an internal error may have occurred, and if using DSRepair or restarting the server does not resolve the error, it should be reported to Novell. |
-6037 | 0xFFFFE86B | ERR_INDEX_OFFLINE | If this error is reported while the database is being upgraded by a new version of eDirectory, it is an informational error. This is because the operationally required indexes are unavailable until the upgrade completes. However, if this error occurs under other circumstances, an internal error may have occurred, and if using DSRepair or restarting the server does not resolve the error, it should be reported to Novell. |
-6038 | 0xFFFFE86A | ERR_CLOSING_DATABASE | Some other components of the system have the database open, and eDirectory is unable to close it. This is generally a transitory error, but it may take several minutes for all components to relinquish access. |
-6039 | 0xFFFFE869 | ERR_OBJECT_OP_DISABLED | The current system configuration prohibits any type of operation (such as changing the DS password) on this object. |
-6040 | 0xFFFFE868 | ERR_OP_STARTED | This is more of a status code than an error. It means that the requested operation started as expected. |
-6041 | 0xFFFFE867 | ERR_OP_ABORTED | This is more of a status code than an error. It means that the requested operation was successfully cancelled. |
-6042 | 0xFFFFE866 | ERR_OP_FAILED | The requested operation failed. |
-6043 | 0xFFFFE865 | ERR_OP_IN_PROGRESS | The requested operation is already in progress. |
-6044 | 0xFFFFE864 | ERR_NO_VALUE | A parameter in the FLAIM initialization file ( NDSDB.INI ) that is supposed to have a value associated with it (such as the cache setting) does not have a value. The default value is used instead. |
-6045 | 0xFFFFE863 | ERR_PARAM_NOT_FOUND | A query is made for a certain parameter in the FLAIM initialization file, but that parameter doesn't exist. |
-6046 | 0xFFFFE862 | ERR_VALUE_TOO_LARGE | A value passed to eDirectory exceeds the maximum value size that can be stored in the database (64,000 characters). |
-6047 through -6999 | 0xFFFFE861through 0xFFFFE4F9 | | Reserved for future DS error codes. |