No such entry. The object name entered could not be found in the context specified. The name may have been mistyped. The workstation's context may be incorrect for the object being sought. The leading dots or trailing dots may have been used incorrectly.
Action: Check the context specified for the object name entered. If the command line input was the object name, check the workstation's context. Make sure that it points to the correct level of the Directory tree for the object name specified. If the input includes the object's full or partial context, make sure that the leading and trailing dots are specified appropriately and the types are correct.
FFFFFDA6
-602
No such value. The requested property value could not be found.
Action: Use NLIST to determine if the value exists for the specified property. If this error is encountered during the login or authentication process, this error usually means that either the user's or the server's public keys could not be located. If this is the case, regenerate the user's key pair by changing the password with utilities.
An occurrence of this error during the synchronization process between servers means one of the public keys cannot be located or the replica lists of one of the servers contains inconsistent results. This error may be a temporary condition that exists do to the loosely consistent nature of NetWare Directory Services.
FFFFFDA5
-603
No such attribute. The requested property could not be found. In the Directory, if a property does not contain a value then the property does not exist for the specific object.
Action: Ensure that the property being requested is a valid DS property (check spelling and syntax). Use NLIST to determine if the property exists for the specified object. For example, NLIST user=username/d will show all properties and their values for the specified username. (Note: To see all of the properties associated to the object requires supervisor rights to the object. Browse rights are given by default.)
FFFFFDA4
-604
No such class. An object class that does not exist in the Directory is being referenced by a utility. Object Class in NetWare Directory Services is similar to object Type in the bindery. For example, object type 1 in the bindery is a user object and in the Directory the Object Class is USER. The class indicates the kind of object to be created.
Action: NetWare 4 utilities access only Novell's base schema which must be present for the Directory to operate. Determine what utility is being used to create the object. This utility is attempting to use an Object Class that is currently not defined in NetWare Directory Services. The shipping set of NetWare 4 utilities only displays valid Object Classes.
FFFFFDA3
-605
No such partition. A partition with the specified name does not exist. A partition in the directory is named by the root object of the specified partition. The very first partition in the Directory is [Root] which is the top of the directory.
Action: Ensure that the partition name requested is valid and is a valid object name.
FFFFFDA2
-606
Entry already exists. An attempt was made to add an object at the same level as a preexisting object of the same name but not necessarily the same Class.
Action: Specify a different name for the object being added or rename the existing object.
FFFFFDA1
-607
Not effective class. This error indicates that the class being used to create the specified object is a noneffective class and cannot be used when creating an object. there are two types of object classes in the Directory, effective and noneffective. All effective classes can be used when creating objects (the class being used to create the specified object is referred to as the "base class" of the object). Users is one example of an effective class. Noneffective classes are used as super classes to define information associated with various effective classes.
Action: The standard Novell utilities that ship with NetWare 4 only allow effective classes to be used when creating objects. Find out what utility is being used to create the object. This utility is not following the rules of the specified object.
FFFFFDA0
-608
Illegal attribute. An attempt was made to add a property that is illegal to an object. The NetWare Directory Services schema determines what properties can be inherited by an object class. (Refer to the NetWare Directory Services Schema documentation if available.)
Action: You cannot add the specified property to the specified object.
FFFFFD9F
-609
Missing mandatory. One or more of the mandatory properties for the object being created is missing. Each object class in the Directory has a set of mandatory properties (properties that must contain a value before the object can be created). For example, a User object in the Directory is required to have a Common Name (CN) and a Surname. Without these properties, the object will not be created. A property exists only if there is a value specified for the given property.
Action: Input the required information when creating the object.
FFFFFD9E
-610
Illegal DS name. Illegal Directory Names are those which are too long (more than 255 characters) or contain illegal character combinations. The "\' character can only be followed by a "." or "=" or "+" or "\".
FFFFFD9D
-611
Illegal containment. The containment rules of the Directory specify where an object class may appear in relation to other objects in the Directory tree. For example, the object Class Country can only be created at the top of the Directory, the object Class User can only be created under Organizations and Organizational Units. The Schema enforces the containment rules for NetWare Directory Services.
Action: Go to the appropriate container to create the object.
FFFFFD9C
-612
Can't have multiple values. The specified property is single valued. All properties are either single or multi valued. For example, the Group Membership property is multi-valued. A user can be a member of multiple groups. the Group Membership property exists once and contains multiple group names (values).
Action: For this property (information category in the utility), only one value (piece of information) can be supplied.
FFFFFD9B
-613
Syntax violation. An attribute value being added to an object is incorrect. This error is most often encountered if that value is the name of another object and that does not exist.
Action: For most cases, verify that the object name being added as a value is correct.
FFFFFD9A
-614
Duplicate value. An attempt was made to add a duplicate value to the specified property.
Action: Enter a different value.
FFFFFD99
-615
Attribute already exists. An attempt was made to add a property that already exists.
Action: If the attribute is multi valued, just add the specified value to the existing property. If the property is singled valued, delete the property and create it again with the new value.
FFFFFD98
-616
Maximum entries exist. The maximum entries (objects) exist in the directory tree. The maximum number of objects that can be created in the Directory is FFFFFF (3 bits of FF) which equals 16,777,220 decimal.
Action: For the current version of the Directory, you have reached the maximum number of objects that can be created. To continue, delete objects that are no longer needed.
FFFFFD97
-617
Database format. The database format is invalid.
FFFFFD96
-618
Inconsistent database. The server has detected an inconsistent database. Usually this means that the number of entries in a container does not match the number stored in the container's entry.
Action: Run DSREPAIR.
FFFFFD95
-619
Invalid comparison. An attempt was made to (1) compare two properties that are not comparable or (2) use an invalid compare syntax.
FFFFFD94
-620
Comparison failed. A comparison of some kind failed.
FFFFFD93
-621
Transactions disabled. The Transaction Tracking Service (TTS) has been disabled for the sever on which the Directory operation is taking place. When TTS is disables Directory Services operations which require modifying the database on that server are disabled as well.
Action: At the console prompt of the file server, type "ENABLE TTS". If TTS was disabled because volume SYS: is full, login into the server and delete unnecessary files from volume SYS: and then type "ENABLE TTS" at the console.
FFFFFD92
-622
Invalid transport. The type of transport passed in to the server is not supported by the server.
FFFFFD91
-623
Syntax invalid in name. The syntax for the name provided is invalid.
FFFFFD90
-624
Replica already exists. A replica of the specified partition already exists on the server.
Action: Select a different server. It is recommend that a partition should have NO more than seven or eight replicas.
FFFFFD8F
-625
Transport failure. The server is unable to communicate across the network for one or more of the following reasons: a server is down, a bridge or other physical connection is down between servers, or a server cannot be found.
Action: Check cabling and LAN communications. Check the server names and network addresses. Make sure that they have not changed since this server has been installed into the Directory. If they have, set them back to the original settings (if available) and see if the error goes away. Once all the connections have been reestablished, it may take up to 5 minutes before this message goes away.
FFFFFD8E
-626
All referrals failed. All referrals failed. The object could not be found. It is possible that the object exists, but the server could not communicate with the server holding a copy of the object. This error message is common when partition management is requested and events cannot occur because a server is inaccessible. This may be a temporary condition during partition functions.
FFFFFD8D
-627
Can't remove naming value. An attempt was made to delete the naming property. You must rename the object, then delete the property.
FFFFFD8C
-628
Object class violation. An object class violation has occurred.
FFFFFD8B
-629
Entry is not leaf. The object being deleted or modified is not a leaf object. A container object that does not contain any objects is considered a leaf object, and therefore can be deleted. If you attempt to delete a container object that contains object of any Class, the following error is returned. "The utility can't delete Object_Class=Object_name because it is not a leaf object." A container object that is a partition root can not be deleted.
Action: Delete all objects under the container object that is being deleted or modified. If the object is a partition root, merge the partition with the parent partition and then delete the object.
FFFFFD8A
-630
Different tree. No information is available.
FFFFFD89
-631
Illegal replica type. A replica needed to perform this function was not found. Typically you will receive this error when you attempt to set your bindery context at the server console and the server does not have a Read Write replica of the container you are attempting to reference in the bindery context.
Action: Use Partition Manager to add a replica that includes the bindery context to that server.
FFFFFD88
-632
System failure. Unexpected results have occurred. For example, the client requested that the Directory return a network address attribute and the Directory actually returned a public key attribute. This condition may be temporary. While the client usually returns errors in the -301 to -399 range, the client as well as the server returns this error during the authentication process.
FFFFFD87
-633
Invalid entry for Root. An invalid entry for the root was made.
FFFFFD86
-634
No referrals. The server has no objects that match the request and has no referrals on which to search for the object.
FFFFFD85
-635
Remote failure. To complete some operations, a server will need to contact another server. If this is not possible (due to a link being down, for example), this error is returned.
FFFFFD84
-636
Unreachable server.
FFFFFD83
-637
Previous move in progress. Once an object has been moved from one context in the Directory to another, the Directory will not allow that object to be moved again until all replicas of that object have been updated. The length of time will vary depending on the size of the replica, the number of replicas, and the condition of the communication links between all the servers holding the replicas.
Action: Leave the object in its current context until it can be moved again. This may require that the object be left in its new context for several minutes.
FFFFFD82
-638
No character mapping.
FFFFFD81
-639
Incomplete authentication.
FFFFFD7F
-641
Invalid request. The server did not understand the request. For example, a verb sent by a client workstation could be incorrect.
FFFFFD7E
-642
Invalid iteration. An iteration handle sent by a client workstation is invalid.
FFFFFD7D
-643
Schema is nonremovable. An attempt was made to delete an NDS structure or configuration.
FFFFFD7C
-644
Schema is in use. An attempt was made to delete an NDS configuration or structure (such as a container object) that still contains an object using that structure. You must first delete the object or property, then delete the structure.
FFFFFD7B
-645
Class already exists. The object Class being created already exists as a Class in the schema of the Directory. (See -604).
Action: This error should only occur in a utility that updated the schema of the Directory. NetWare 4 does not include a utility to modify the schema. Determine the utility causing the error.
FFFFFD7A
-646
Bad naming attributes. Invalid naming properties were used.
FFFFFD79
-647
Not Root partition. An attempt was made to execute a function that is required on the root partition. Either (1) the client did not pass in the root partition name, or (2)\x110011the client attempted to perform the function somewhere besides the root partition.
FFFFFD78
-648
Insufficient stack. The server stack was not large enough.
FFFFFD77
-649
Insufficient buffer. The server ran out of memory.
Action: See "Resolving Server Memory Problems" in Supervising the Network.
FFFFFD76
-650
Ambiguous containment. An attempt was made to create an NDS definition for a class that contained an ambiguous containment rule.
FFFFFD75
-651
Ambiguous naming. An attempt was made to create an NDS definition for a class that contained an ambiguous containment name.
FFFFFD74
-652
Duplicate mandatory. An attempt was made to create an NDS definition for a class that contained a duplicate mandatory name.
FFFFFD73
-653
Duplicate optional. An attempt was made to create an NDS definition for a class that contained a duplicate optional name.
FFFFFD72
-654
Partition busy. Another partition operation is currently taking place. For example, if a request has previously been issued to split a partition, a second request for a split (even at another point in the same partition) results in this error.
Action: Wait for the previous partition operation to synchronize completely.
FFFFFD71
-655
Multiple replicas. No information is available.
FFFFFD70
-656
Crucial replica. No information is available.
FFFFFD6F
-657
Schema sync in progress. The function could not be completed, because Directory synchronization is in progress. Wait awhile and try again.
FFFFFD6E
-658
Skulk in progress. The function could not be completed because replica synchronization is in progress. Wait awhile and try again.
FFFFFD6D
-659
Time not synchronized. NetWare Directory Services uses time stamps to determine the order of events that take place in the Directory. Time Synchronization Services has been implemented to maintain a consistent time across the network. Modification operations require the issuance of time stamp. If a replica on a server has issued a time stamp and the time on that server is set back, no further modification operations may take place until the time on the server moves past the last modification time on the partition. This applies only to operations that modify, not those that just read information.
Action: Use Partition Manager's Rebuild Replicas to reset the time stamps to the current time and then wait for the replicas to synchronize. You may have to do this on a partition by partition basis.
FFFFFD6C
-660
Record in use. The requested record is already in use.
FFFFFD6B
-661
DS volume not mounted. The Directory Services volume is not mounted.
FFFFFD6A
-662
DS volume IO failure. An I/O failure occurred on the Directory Services volume.
FFFFFD69
-663
DS locked. The Directory database is locked on the server.
Action: It may be necessary to run SDREPAIR on the server.
FFFFFD68
-664
Old epoch. This is an NDS time stamp error.
FFFFFD67
-665
New epoch. This is an NDS time stamp error.
FFFFFD65
-667
Partition root. The object being manipulated is the root of a Directory Services partition. This error appears most often when attempting to delete a container object that is a partition root.
Action: Use the partition management tools to merge this partition into the parent partition.
FFFFFD64
-668
Entry not container. An illegal function was attempted on a leaf object.
FFFFFD63
-669
Failed authentication. The Directory database is locked on the server.
An invalid password was sent. Authentication failed.
FFFFFD61
-671
No such parent. A parent was specified that does not exist.
FFFFFD60
-672
No access. The client does not have sufficient results to perform the requested operation.
FFFFFD5F
-673
Replica not on. The replica is being created on a server. Until all the object information has been received on that server, the replica is "off" (not available for use by Directory clients).
Action: Wait until the replica is created on the other server.
FFFFFD5A
-678
Duplicate ACL. No information is available.
FFFFFD59
-679
Partition already exists. An attempt was made to create a partition that already exists.
FFFFFD58
-680
An attempt was made to use a reference that is not a subordinate reference.
FFFFFD57
-681
Alias of an alias. An attempt was made to use an alias of an alias.
FFFFFD56
-682
Auditing failed. One of the following explanations may apply:
The auditing function failed.
FFFFFD55
-683
Invalid API version. An invalid application API is being used. You will need to update your software.
FFFFFD54
-684
Secure NCP violation. No information is available.
FFFFFD45
-699
Unknown. An unrecoverable error has occurred and the operation cannot be completed.
