NetWare Directory Services

Error Codes

June, 1995

Disclaimer

Novell, Inc. makes no representations or warranties with respect to the contents or use of this manual, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Novell, Inc.

122 East 1700 South

Provo, UT 84606

Trademarks

Novell and NetWare are registered trademarks of Novell, Inc.

NetWare Directory Services Error Codes

June, 1995

The suggestions contained in this list are general and may need to be modified to apply to your specific situation. Temporary errors are a normal part of the loosely consistent DS database, so don't be alarmed by errors that come and go. Remember BE PATIENT and DON'T PANIC about temporary errors.

Definitions

Source Server: The server where the DSTRACE error is displayed.

Target Server: The server whose name is listed in DSTRACE with the error message.

Send All Objects: An option available in the 4.1 DSREPAIR under "Advanced Options", "Replica and partition operations", <select partition>, "Send all objects to every replica in the ring." Send All Objects will send only updated or missing information from the source server to every other server in the replica list (including the Master replica). Sometimes a better option is "Receive all objects from the master to this replica" (available from the same menu as Send all Objects) because receiving from the master involves only two servers in the synchronization. The disadvantage of Receive All Objects is that the Master replica then completely replaces the information on the source server's replica. If you use the option to Send All Objects, please see the section on Send All Objects below.

Receive All Objects: Also available in the 4.1 DSREPAIR under "Advanced Options", "Replica and partition operations", <select partition>, "Receive all objects from the master to this replica." This option is better than Send all objects in some ways because it generates less traffic. However, Receive All Objects cannot be used unless the Master replica has the good copy and the server with the problem copy is 4.1. Receive All Objects is essentially the same as deleting the replica from the problem server and then adding it back through Partition Manager. In both cases the information on the source server is overwritten by the information on the server holding the Master replica. If you cannot use a Receive All Objects, you will need to do a Send All Objects.

Special Note on Send All Objects

In 4.1, the option to "Send All Objects" is available from within the DSREPAIR utility and allows the administrator to send missing or updated information from one replica to every other replica in a partition. This is similar to a Repair Time stamps or Receive All Objects except that 1) Repair Time stamps and Receive All Objects always take information from the Master replica and Send All Objects allows you to choose the replica from which to send information; and 2) Repair Time stamps and Receive All Objects will overwrite data on the target replicas while Send All Objects merely sends information from the source server while not writing over anything the target may have in addition to what the source is sending. For instance, user SAM may have a phone number on FS1 with no E-mail address, but FS2 may think that SAM has an E-mail address but no phone number. If you were to do a Send All Objects from FS1 on SAM's partition, FS2 would then get the phone number in addition to keeping the E-mail address.

Send All Objects generates quite a bit of traffic since the source server resends all data in the partition to all servers in the replica list. It is also easy to do a Send/Receive All Objects from a bad replica and therefore corrupt all the other replicas, so please be careful about performing any of these options and make sure you check the validity of the replica you use as the source before executing any of these commands. Also be sure to send the trace to a file (SET DSTRACE=ON, SET DSTRACE=+SYNC, SET TTF=ON, SET DSTRACE=*R, execute the Send All Objects command, wait for Send All Objects to complete, then SET TTF=OFF) to ensure you can track down any errors that may occur during the synchronization.

If a Send All Objects is executed but a server in the replica list is down, the Send will continue to try to update each server in the replica list with all the objects until it can get an ALL PROCESSED=YES on the operation. So, if after performing a Send All Objects, there are 2 iterations of ALL PROCESSED=NO, do a SET DSTRACE=*D<replica RootEntryID> to abort the Send (there is NO option to do this through DSREPAIR). The replica rootEntryID can be found by loading DSRepair on the server from which you executed the Send, choosing Advanced Options, selecting Replica and partition operations, choosing a partition, then selecting Display replica information. Find the partition in question and look at the third line under the title Partition Information and Servers in the Replica Ring. This eight digit number is the Replica rootEntryID. After canceling the Send, check the DSTRACE.DBG (in SYS:SYSTEM after sending the trace to file) for errors. Resolve any errors you find here before repeating the Send.

It can be dangerous to do ANY of these options in a mixed environment (a tree containing both 4.0x and 4.1 servers) if there are any rename problems (objects which have been renamed to #_#, i.e. 3_2, due to name collisions). Therefore, check for renames before issuing a Send All Objects or a Receive All Objects. If renames exist and there are errors in DSTRACE which are normally resolved by a Send All Objects or Receive All Objects, do a SET DSTRACE=+SYNC and try deleting the object immediately preceding the error. If there are too many objects with errors, or the error is on an object which cannot be deleted easily (i.e. a container or server object), then try removing the replica from the target server. Remember that Send All Objects and Receive All Objects can cause renames to propagate through further name collisions.

NetWare Directory Services Error Codes

NO_SUCH_ENTRY	-601	0xFFFFFDA7	FDA7

Explanation: This error to a server during DSTRACE usually means that an entry is missing from the entry record table on the source server.

Client Action: Check the context specified for the object name entered. If the command line input was the object name, check the work station's context. Make sure that it points to the correct level of the Directory 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 that the types are correct. It is common to get this error when trying to delete bindery type objects through NWADMIN or the 4.02 version of NETADMIN. Use the 4.01 version of NETADMIN to delete bindery type objects from a 4.0x server. This should not be a problem in 4.1.

Server Action: Do a SET DSTRACE=+SYNC on both the source and the target server (and any other servers in the replica list) to see which object is returning the -601 error and what errors the target server is getting in return. If the object is not a server, try deleting it. If the object with the error is a server object, see if DSTRACE returns any other errors besides -601. Address those errors, if any. If there are no additional errors, do a Send All Objects (see note on Send All Objects at the beginning of this document) from the server reporting the error (the source server), or Receive All Objects from the target server (but this will only help if the source server is the Master). BUT BEWARE! Send All Objects CAUSES A LOT OF TRAFFIC!

NO_SUCH_VALUE	-602	0xFFFFFDA6	FDA6

Explanation: The requested property value could not be found. 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 that a value of an object being synched is missing from the target server. This error may be a temporary condition that exists due to the loosely consistent nature of Directory Services.

Server Action: What error are you seeing on the target server? You may see one of the following without an error code:

1.	Error unable to communicate	--	Look in DSTRACE for the object with the problem (SET DSTRACE=+SYNC). This is probably a problem with either the public key or the remote ID. Run DSREPAIR to verify remote server IDs. If errors appear there, run this same option once more to verify remote server IDs. If you get a -602 or -603 in DSREPAIR when verifying remote server IDs, call your Novell Authorized Service Center for support. Be aware, however, that a public key cannot be repaired unless there is at least one server in the tree authenticating without problems to the target server. The server authenticating OK to the target server must also have a real copy of the target server object, so it must have a replica (other than a subordinate reference) of the partition holding the target server object. If this is only a 2 server tree, the target server will need to be removed from the tree and reinstalled.

2.	Error sending updates	--	Look in DSTRACE for the object with the problem (SET DSTRACE=+SYNC) and try deleting the object.

NO_SUCH_ATTRIBUTE	-603	0xFFFFFDA5	FDA5

Explanation: 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.

Client Action: Insure that the property being requested is a valid DS property (check spelling and syntax). Use NLIST.EXE to determine if the property exists for the specified object. For example, NLIST user=username /d will show all of the properties and there values for the specified user name. (note: to see all of the properties associated to the object requires supervisor rights to the object in question. Browse rights are given by default.) We have seen this error when users try to edit properties that are grayed out in the utilities (so are not supported in the current DS schema). This error can also occur when there are schema synchronization problems in a mixed tree (4.0x and 4.1 servers in the same tree).

Server Action: This is basically the same as a -602 error except that you get a -602 on a multi-valued property and a -603 on a single-valued property. What error are you seeing on the target server? You may see one of the following without an error code:

1.	Error unable to communicate	--	Look in DSTRACE for the object with the problem (SET DSTRACE=+SYNC). This is probably a problem with either the public key or the remote ID. Run DSREPAIR to verify remote server IDS. If errors appear there, run this same option once more to verify remote server IDS. If you get a -602 or -603 in DSREPAIR when verifying remote server IDs, call your Novell Authorized Service Center for support. Be aware, however, that a public key cannot be repaired unless there is at least one server in the tree authenticating without problems to the target server. The server authenticating OK to the target server must also have a real copy of the target server object, so it must have a replica (other than a subordinate reference) of the partition holding the target server object. If this is only a 2 server tree, the target server will need to be removed from the tree and reinstalled.

2.	Error sending updates	--	Look in DSTRACE for the object with the problem (SET DSTRACE=+SYNC) and try deleting the object. If there is currently a mixed environment in the tree or if there ever were 4.1 servers in a now completely 4.0x tree, then this could be a schema problem. Run the Global Schema Update option in DSREPAIR on a 4.1 server. If there are no longer any 4.1 servers in the tree, or if the Global Schema Update does not fix the problem, down the server with the master replica of the partition returning the error and then bring it back up. Upon startup, the server will force a schema update and this will usually correct a schema problem.

NO_SUCH_CLASS	-604	0xFFFFFDA4	FDA4

Explanation: An object class that does not exist in the Directory is being referenced by a utility. Object Class in Directory Services is similar to the 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 v4.0 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 Directory Services. The shipping set of NetWare v4.0 utilities only display valid object Classes. NetWare v4.1 allows the schema to be extended, so this error in 4.1 may point to schema synchronization problems.

NO_SUCH_PARTITION	-605	0xFFFFFDA3	FDA3

Explanation: A partition with the specified name does not exist.

Action: Insure that the partition name requested is valid and is a valid object name.

ENTRY_ALREADY_EXISTS	-606	0xFFFFFDA2	FDA2

Explanation: 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.

NOT_EFFECTIVE_CLASS	-607	0xFFFFFDA1	FDA1

Explanation: This error indicates that the class being used to create the specified object is a non-effective class and cannot be used when creating an object. There are two types of object classes in the Directory, effective and non-effective. 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). User would be one example of an effective Class. Non-effective classes are used as super classes to define information associated with various effective classes.

Action: The standard Novell utilities that ship with NetWare v4.0x 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.

ILLEGAL_ATTRIBUTE	-608	0xFFFFFDA0	FDA0

Explanation: An attempt was made to add a property that is illegal to an object. The Directory Services schema determines what properties can be inherited by an object class. (refer to the Directory Services Schema documentation if available.) This error can also occur in mixed trees (4.0x and 4.1 servers in the same tree) or in upgraded trees (when 4.0x servers have been upgraded to 4.1) when a server does not have the correct schema.

Client Action: You can not add the specified property to the specified object.

Server Action: Do a SET DSTRACE=+SYNC and then SET DSTRACE=*H to see the object causing the error. If the object is not a server object, try deleting it. In the case of a schema problem, run Global Schema Update from a 4.1 server. If there are no longer any 4.1 servers in the tree or if Global Schema Update does not correct the problem, down the server with the master replica of the partition showing errors and then bring it back up. Upon startup, the server will force a schema update which usually corrects these schema problems. If the problem persists, call your Novell Authorized Service Center for support.

MISSING_MANDATORY	-609	0xFFFFFD9F	FD9F

Explanation: This error indicates that 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 supplied for the given property. This error can also occur in mixed trees (4.0x and 4.1 servers in the same tree) when a server does not have the correct schema.

Client Action: Input the required information when creating the object.

Server Action: Do a SET DSTRACE=+SYNC and then SET DSTRACE=*H to see the object causing the error. If the object is not a server object, try deleting it. In the case of a schema problem, run Global Schema Update from a 4.1 server. If there are no longer any 4.1 servers in the tree or if Global Schema Update does not correct the problem, down the server with the master replica of the partition showing errors and then bring it back up. Upon startup, the server will force a schema update which usually corrects these schema problems. If the problem persists, call your Novell Authorized Service Center for support.

ILLEGAL_DS_NAME	-610	0xFFFFFD9E	FD9E

Explanation: Illegal Directory Names are those which are too long (more than 255 characters) or ones which contain illegal character combinations. The '\' character may be followed only by a '.' or '=' or '+' or '\'.

ILLEGAL_CONTAINMENT	-611	0xFFFFFD9D	FD9D

Explanation: 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 Directory Services.

Action: Go to the appropriate container to create the object.

CANT_HAVE_MULTIPLE_VALUES	-612	0xFFFFFD9C	FD9C

Explanation: This error indicates that 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.

SYNTAX_VIOLATION	-613	0xFFFFFD9B	FD9B

Explanation: 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 object does not exist. This error is also seen during the install or upgrade to 4.1.

Client Action: For most cases, verify that the object name being added as a value is correct.

Server Action: If a new 4.1 server hangs during install while copying over the directory services objects, check the DSTRACE screen of the server with the master replica of the partition where the new 4.1 is being installed. If the master is giving errors, run DSREPAIR on the master. If still problems, do a SET DSTRACE=+SYNC to find the object returning the error and check the description field (and any other field which accepts a string) for any unusual ASCII characters. Correct the corruption or delete the object and the replica should complete copying to the new server.

We have also seen this error when a bindery-type object (usually created by a 3rd party program) becomes corrupt. If the -613 errors are on these types of objects, delete all objects created by the program and then reinstall the program.

DUPLICATE_VALUE	-614	0xFFFFFD9A	FD9A

Explanation: An attempt was made to add a duplicate value to the specified property.

Action: Enter a different value.

ATTRIBUTE_ALREADY_EXISTS	-615	0xFFFFFD99	FD99

Explanation: 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, you will need to delete the property in order to create it again with the new value.

MAXIMUM_ENTRIES_EXIST	-616	0xFFFFFD98	FD98

Explanation: This error indicates that 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. Some of these entries are used by the Directory itself.

Action: For the current version of the Directory, you have reached the maximum number of objects that can be created. To continue you will need to delete objects that are no longer needed.

DATABASE_FORMAT	-617	0xFFFFFD97	FD97

INCONSISTENT_DATABASE	-618	0xFFFFFD96	FD96

Explanation: This error indicates that an error has been encountered in the database itself. Usually this error means that the number of entries in a container does not match the number stored in the container's entry. When this error occurs during synchronization, the target server has a corrupted database.

Action: Run DSREPAIR ONCE. If this error persists after running DSREPAIR the first time, consult your Novell Authorized Service Center. By running DSREPAIR a second time, the original .OLD database files will be overwritten and it may not be possible to restore their former DIB.

INVALID_COMPARISON	-619	0xFFFFFD95	FD95

Explanation: An attempt was made to either compare two properties that are not comparable or to use an invalid compare syntax.

Action: Check the syntax and verify that the properties are comparable.

COMPARISON_FAILED	-620	0xFFFFFD94	FD94

TRANSACTIONS_DISABLED	-621	0xFFFFFD93	FD93

Explanation: This error indicates that Transaction Tracking (TTS) has been disabled for the server on which the Directory operation is taking place. When TTS is disabled, Directory Service 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 disable because the SYS volume is full, login to the file server, delete unnecessary files from the SYS volume, and type "ENABLE TTS" at the file server. If you are unable to login to the file server, try running VREPAIR on volume SYS and selecting "purge deleted files" from the VREPAIR menu. If there still is not enough space, put another drive into the server and span the SYS volume across both drives to give SYS more space.

INVALID_TRANSPORT	-622	0xFFFFFD92	FD92

SYNTAX_INVALID_IN_NAME	-623	0xFFFFFD91	FD91

REPLICA_ALREADY_EXISTS	-624	0xFFFFFD90	FD90

Explanation: This error indicates that a replica of the specified partition already exists on the server.

Action: Select a different server.

TRANSPORT_FAILURE	-625	0xFFFFFD8F	FD8F

Explanation: This error indicates the inability to communicate across the network either between a client and a server or between two servers.

Action: Check for SAP filtering of the DS SAP types of 26B and 278. Check cabling, the LAN card, and the LAN driver. Make sure that they can RCONSOLE to the target server. Does typing DISPLAY SERVERS on the source server show the target server? Are other servers also showing this -625 error to the same target server? Can workstations attach and login to the target server from the same segment as the source server? Have them type RESET ROUTERS and then type SET DSTRACE=*U at the source server to flag all servers as UP and retry communicating with them. This error is almost ALWAYS a LAN issue. Occasionally a change of the server's name, a move of the server object, or a change to the internal ipx number can also cause this error. Run DSREPAIR with the option to repair network addresses on the source server to check the internal ipx number of the target server--the change may not have completed successfully. This error will also been seen when trying to communicate with servers having locked databases (i.e. with DSDUMP or DSREPAIR).

ALL_REFERRALS_FAILED	-626	0xFFFFFD8E	FD8E

Explanation: The object could not be found, but it is still possible that the object does exist but that a server could not communicate with the server holding a copy of the object. The target server tried to walk the tree by contacting all other servers in the replica ring and was unable to do so. This error is commonly seen when partition management is requested and the requested operation cannot occur because a key server is inaccessible. Invalid creation time stamps can also return this error.

Server Action: Run DSREPAIR with the options to repair network addresses and to verify remote server IDs.. Check the replica rings to verify that there is one master replica for the partition in question. Check the replica states and make sure they are all "ON." Resolve whatever problems you find in the DSREPAIR.LOG file. Look in DISPLAY SERVERS and see if the tree name is present. If not, check the issues with -625 errors (including SAP filtering). If creation time stamps are invalid running the 4.1 DSREPAIR with the option to Check External References (under Advanced Options--only available in newer DSREPAIRs) should repair this issue.

CANT_REMOVE_NAMING_VALUE	-627	0xFFFFFD8D	FD8D

Explanation: Can't remove naming value. An attempt was made to delete the naming property.

Action: Rename the object, then delete the property.

OBJECT_CLASS_VIOLATION	-628	0xFFFFFD8C	FD8C

Explanation: An object class violation has occurred.

Server Action: This can happen when the source server's objects are unknown, but the objects are fine on the target server. Isolate the bad replica by either locking the databases with DSREPAIR and then running Net or NWAdmin to view the objects or by using DSVIEW (available on NetWire). Then delete the bad replica and add it back again through Partition Manager (verifying first that the master is a good copy).

A schema synchronization problem can also generate this error. Run the Global Schema Update option in DSREPAIR on a 4.1 server. If there are no longer any 4.1 servers in the tree, or if the Global Schema Update does not fix the problem, down the server with the master replica of the partition returning the error and then bring it back up. Upon startup, the server will force a schema update and this will usually correct a schema problem.

ENTRY_IS_NOT_LEAF	-629	0xFFFFFD8B	FD8B

Explanation: This error indicates that 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 does contain objects 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.

DIFFERENT_TREE	-630	0xFFFFFD8A	FD8A

ILLEGAL_REPLICA_TYPE	-631	0xFFFFFD89	FD89

Explanation: This error indicates that a request was made of a replica, but the replica was the wrong type and therefore the request could not complete.

Server Action: This is usually seen at the file server console when attempting to SET BINDERY CONTEXT. Bindery context requires a writable replica (either a read/write or a master) in order to be set. Verify that the server has a writable replica of the partition containing the container to which you are attempting to set the bindery context.

SYSTEM_FAILURE	-632	0xFFFFFD88	FD88

Explanation: This error indicates that 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. When a server returns a -632 during synchronization, this may be because authentication could not complete due to an error in the public key--the key is the right key, but it is corrupt (not the right format). This error can also be returned in DSTRACE when the server is unable to open the local database. However, -632 is just a general error which means that the process being attempted failed. This may be because the server(s) being contacted was busy, down, or that the source server could not authenticate to it.

Symptom: After upgrading a server, the DS is unable to open the database. SET DSTRACE=ON and then SET DSTRACE=+MISC. Then dismount and remount the SYS volume. Check the DSTRACE screen and confirm that a -632 error is returned when DS tries to open the database. If so, the database is corrupted. DS will need to be removed from the server and reinstalled (either from another replica in the tree or, if a single server environment, from backup).

Server Action: Run DSREPAIR with the option to verify remote server IDS on every server in the replica list. Then go back and run DSREPAIR a second time with the option to verify remote server IDs on every server in the replica list. If the remote server id check returns a -632 after running it the second time, call your Novell Authorized Service Center. Otherwise, try to resolve the process which failed.

INVALID_ENTRY_FOR_ROOT	-633	0xFFFFFD87	FD87

Explanation: An attempt was made to either restore or move an object which is flagged as a partition root, but whose base class is not a container, or perform a split at an object whose base class is not a container.

NO_REFERRALS	-634	0xFFFFFD86	FD86

Explanation: This means that the target server does not have a copy of what the source server is requesting. In other words, the source server has no objects which match the request and has no referrals on which to search for the object.

Action:	This is not a serious error, but just a response. This error will usually resolve itself.

REMOTE_FAILURE	-635	0xFFFFFD85	FD85

Explanation: In order 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 will be returned.

Action: The target server does not have the correct information about the source server. This is often caused by a problem with local to remote IDs or the server object. Run DSREPAIR with the option to verify remote server IDs on every server in the replica list. Then go back and run DSREPAIR a second time with the option to verify remote server IDs on all servers in the replica list. Resolve any errors found after the second run of DSREPAIR.

UNREACHABLE_SERVER	-636	0XFFFFFD84	FD84

PREVIOUS_MOVE_IN_PROGRESS	-637	0XFFFFFD83	FD83

Explanation: 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 for a move to complete will vary--depending on the size of the replica, the number of replicas, and condition of the communication links between all the servers holding the replicas. This error can be caused by a moved object which lost the original object (the primary obituary) or by a broken partition.

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. If the object still cannot be moved, load the 4.1 DSREPAIR with -m (LOAD DSREPAIR -M) and then run Repair Local Database (For 4.0x DSREPAIR, type LOAD DSREPAIR -A, Select Options, toggle A until it reads "Find obituaries for move and move-inhibit"). View the DSREPAIR.LOG file which will display objects which have move obituaries. Verify that the problem objects and all their attributes have successfully moved to the new location (by running NWAdmin or Netadmin and viewing the objects). If so, load the 4.1 DSREPAIR with -MR (load the 4.0x DSREPAIR with -A, Select Options, then toggle A until it reads "Purge obituaries for move and move-inhibit") which will then delete the move obituaries for those problem objects. Use SET DSTRACE=+J and SET DSTRACE=*F to verify that the purger ran successfully.

NO_CHARACTER_MAPPING	-638	0XFFFFFD82	FD82

INCOMPLETE_AUTHENTICATION	-639	0XFFFFFD81	FD81

INVALID_CERTIFICATE	-640	0xFFFFFD80	FD80

INVALID_REQUEST	-641	0xFFFFFD7F	FD7F

Explanation: The server did not understand the request. For example, a client workstation could have sent an incorrect verb.

Server Action: This can be caused by a non-synchronized schema. Run the 4.1 DSREPAIR and do a Global Schema Update. This error can also be a response error, so check for errors on the target server and resolve any you may find there first.

INVALID_ITERATION	-642	0xFFFFFD7E	FD7E

Explanation: A client workstation sent an invalid iteration handle.

SCHEMA_IS_NONREMOVABLE	-643	0xFFFFFD7D	FD7D

Explanation: An attempt was made to delete an NDS structure or configuration.

SCHEMA_IS_IN_USE	-644	0xFFFFFD7C	FD7C

Explanation: An attempt was made to delete an NDS configuration or structure (such as a container object) that still contains an object using that structure.

Action: First delete the object or property, then delete the structure.

CLASS_ALREADY_EXISTS	-645	0xFFFFFD7B	FD7B

Explanation: This error indicates that the object Class being created already exists as a Class in the schema of the Directory. (see also: ERR_NO_SUCH_CLASS -604 0xFFFFFDA4)

Action: This error should only occur in a utility that updates the schema of the Directory. Determine the utility causing the error.

BAD_NAMING_ATTRIBUTES	-646	0xFFFFFD7A	FD7A

NOT_ROOT_PARTITION	-647	0xFFFFFD79	FD79

Explanation: An attempt was made to execute a function that is required on the root partition. Either the client did not pass in the root partition name or the client attempted to perform the function somewhere besides the root partition.

INSUFFICIENT_STACK	-648	0xFFFFFD78	FD78

INSUFFICIENT_BUFFER	-649	0xFFFFFD77	FD77

Explanation: The server ran out of memory. The operating system will self-correct this error.

Action: Be patient. See "Resolving Server Memory Problems" in Supervising the Network.

AMBIGUOUS_CONTAINMENT	-650	0xFFFFFD76	FD76

AMBIGUOUS_NAMING	-651	0xFFFFFD75	FD75

DUPLICATE_MANDATORY	-652	0xFFFFFD74	FD74

DUPLICATE_OPTIONAL	-653	0xFFFFFD73	FD73

PARTITION_BUSY	-654	0xFFFFFD72	FD72

Explanation: 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) will result in this error.

Server Action: This is a normal error immediately after a partition operation has been initiated. If this error does not go away, in the 310 build of the DS this error can indicate that the target server does not think that the source server has a copy of that partition. Confirm this through DSREPAIR.LOG or by watching DSTRACE. Try running PTEST (4.0x) or Cancel Partition Operation (4.1) to abort the partition operation on the source server. Can also remove the source server from the tree or call your Novell Authorized Service Center for support.

MULTIPLE_REPLICAS	-655	0xFFFFFD71	FD71

Explanation: An internal error that appears as a result of a programming error, not a system inconsistency.

CRUCIAL_REPLICA	-656	0xFFFFFD70	FD70

Explanation: An attempt was made to perform one of the following illegal operations on a master replica: remove it, change its replica type (which is correctly done by changing the replica type of another server's replica to the master which will indirectly force the master to become a read/write), or request that it receive all updates from the master. This error can also be caused by attempting to add a replica to the server where the master of that replica already exists.

SCHEMA_SYNC_IN_PROGRESS	-657	0xFFFFFD6F	FD6F

Explanation: The function could not be completed because Directory synchronization is in progress.

Action: Wait a while and try again.

SKULK_IN_PROGRESS	-658	0xFFFFFD6E	FD6E

Explanation: The function could not be completed because replica synchronization is in progress.

Action: Wait a while and try again.

TIME_NOT_SYNCHRONIZED	-659	0xFFFFFD6D	FD6D

Explanation: 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 a time stamp. If a replica on a server has issued a time stamp and the time on that server is set back, in 4.0x 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. In other words, users will be able to login to the directory fine, but no objects can be edited through the utilities. In 4.1, the directory will issue synthetic time stamps on objects in order to allow them to be modified yet still not allow illegal time stamps. The server console will display a synthetic time error when the server time is behind the DS time.

Action: Check DSTRACE for other errors first and resolve any you find. Then Repair Time stamps (found in the 4.1 DSREPAIR) which will reset the time stamps to the current server time. The 4.0x equivalent of Repair Time stamps is Rebuild Replicas and is performed from Partition Manager. This action will delete the objects from all replicas except the Master and then recopy all objects from the Master copy to all other replicas. BEWARE! If the Master copy was corrupt in any way, that corruption will be propagated out to the other replicas when a Repair Time stamps or Rebuild Replicas action is performed. Repair Time stamps or Rebuild Replicas can also cause considerable traffic on the network. You may have to do this on a partition by partition basis.

RECORD_IN_USE	-660	0xFFFFFD6C	FD6C

DS_VOLUME_NOT_MOUNTED	-661	0xFFFFFD6B	FD6B

DS_VOLUME_IO_FAILURE	-662	0xFFFFFD6A	FD6A

DS_LOCKED	-663	0xFFFFFD69	FD69

Explanation: The Directory database is locked on the server. This error will be seen in DSTRACE when the source server is trying to synch with the target server which has a locked database. There will be no activity in the TRACE screen on the server with the locked database. The server with the problem will often get an error trying to open the directory when mounting the SYS volume. We have seen this error occur when DSREPAIR is loaded on the server, when DSDUMP has the directory locked, when the hard drive on the server is going bad, and when a new 4.02 server install does not complete properly.

Action: Try running DSREPAIR on the server (but only run DSREPAIR ONCE. If DSREPAIR is run more than once, the .old database files are overwritten). If DSREPAIR doesn't fix the problem, try downing the server and bringing it back up again. If DSREPAIR and downing the server do not fix this error, the server may need to be removed from the tree (**IMPORTANT--If you remove DS from a 4.01 server, you will lose trustee assignments! The trustee assignments will be backed up for a 4.02 or 4.1 server during removal of DS, though). If this is a new server with no replicas on it, remove DS from the server. If they don't want to remove DS from the server, escalate the call. When the DS is locked, the normal removal of DS on a 4.02 server may not complete properly. You may need to load install with the -dsremove switch (LOAD INSTALL - DSREMOVE) and then try to remove DS through install. This will most likely return an error about being unable to remove DS but will perform the removal anyway--try loading install with the -dsremove switch again and try the removal a second time and DSI should report that DS was already removed from the server. DON'T USE -DSREMOVE UNLESS THE NORMAL REMOVAL WON'T WORK! The -dsremove switch will ignore errors and warnings and may not perform all the steps necessary to do a clean removal.

OLD_EPOCH	-664	0xFFFFFD68	FD68

Explanation: This is an NDS time stamp error.

NEW_EPOCH	-665	0xFFFFFD67	FD67

Explanation: This is an NDS time stamp error.

INCOMPATIBLE_DS_VERSION	-666	0xFFFFFD66	FD66

Explanation: This error occurs when performing operations requiring the same schema, but there are servers involved in the operation with dissimilar schema.

Symptom: Partition Manager returns this error when a partition operation is requested and the server with the Master replica is 4.1 and there are other servers in the replica list which are 4.0x servers (this includes servers holding subordinate reference replicas). DSREPAIR for 4.1 may also return this error during a remote to local ID check.

Server Action: Most partition operations involving a 4.1 server as the server holding the Master will not be able to complete to v4.0x servers. The v4.0x servers in the replica list must be upgraded to v4.1 before the partition operation will be able to complete. If the Master replica were on a v4.02 server, you would not have this particular problem. If this error is seen in DSREPAIR during a remote to local ID check, do a SET DSTRACE=!V on the 4.1 server. This will reset the list of restricted versions (DS versions which are restricted from synchronization) to the default, which is DS 290 and above.

PARTITION_ROOT	-667	0xFFFFFD65	FD65

Explanation: This error indicates that the object being manipulated is the root of a Directory Services partition. This error would most commonly appear when attempting to delete a container object that is a partition root.

Action: Using the partition management tools, merge this partition into the parent partition.

ENTRY_NOT_CONTAINER	-668	0xFFFFFD64	FD64

Explanation: An illegal function was attempted on a leaf object.

FAILED_AUTHENTICATION	-669	0xFFFFFD63	FD63

Explanation: An invalid password was sent. Authentication failed. When this error is seen in DSTRACE when one server tries to synch with another, the most likely problems are either the remote ID or the public key.

Server Action: Try running DSREPAIR with the option to verify remote server IDs on the source server and all other servers in the replica list. If there are errors in the DSREPAIR.LOG file, run DSREPAIR with the option to verify remote server IDs once more on every server in the replica list. This should correct a problem with the remote ID being incorrect. The other scenario is when the source server is either using or looking at the wrong public key (the key is the right format, but is for the wrong object). If the problem is the public key, then:

a)	If the source server has a REAL copy of the target server object (so if the source server has a Master, R/W, or R/O replica of the partition containing the target server object) then check to see if the other servers in that replica list (for the partition containing the target server object) are able to authenticate to the target server. If another server CAN authenticate fine, then do a Send All Objects (see note on Send All Objects at the end of this document) from the good server, or Receive All Objects on the target server (but only if the server with the "good" copy has the Master). BE CAREFUL AND DON'T SEND A BAD PUBLIC KEY!!! Also, remember that Send All Objects generate a lot of traffic. If no servers can authenticate to the target server, remove DS from the target server and reinstall it back into the tree or call your Novell Authorized Service Center for support.

b)	If the source server has a subordinate reference replica or no replica of the partition containing the target server object, then the external reference to that object will need to be re-backlinked. Call your Novell Authorized Service Center for support.

INVALID_CONTEXT	-670	0xFFFFFD62	FD62

NO_SUCH_PARENT	-671	0xFFFFFD61	FD61

NO_ACCESS	-672	0xFFFFFD60	FD60

Explanation: The client does not have sufficient results to complete the requested operation. This error in DSTRACE means that the target server's replica list doesn't match the source server's replica list.

Server Action: Compare the replica ring information for all the servers in the replica list (available though Display Replica Information). If you confirm that the target server doesn't have the source server in it's replica list, then either remove DS from the target server or call your Novell Authorized Service Center for support.

REPLICA_NOT_ON	-673	0xFFFFFD5F	FD5F

Explanation: The replica is in the process of 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).

Server Action: Wait. If the replica is stuck, look for the error that is preventing the replica from turning "on" and address that problem.

INVALID_NAME_SERVICE	-674	0xFFFFFD5E	FD5E

INVALID_TASK	-675	0xFFFFFD5D	FD5D

INVALID_CONN_HANDLE	-676	0xFFFFFD5C	FD5C

INVALID_IDENTITY	-677	0xFFFFFD5B	FD5B

DUPLICATE_ACL	-678	0xFFFFFD5A	FD5A

PARTITION_ALREADY_EXISTS	-679	0xFFFFFD59	FD59

TRANSPORT_MODIFIED	-680	0xFFFFFD58	FD58

ALIAS_OF_AN_ALIAS	-681	0xFFFFFD57	FD57

AUDITING_FAILED	-682	0xFFFFFD56	FD56

INVALID_API_VERSION	-683	0xFFFFFD55	FD55

SECURE_NCP_VIOLATION	-684	0xFFFFFD54	FD54

MOVE_IN_PROGRESS	-685	0xFFFFFD53	FD53

NOT_LEAF_PARTITION	-686	0xFFFFFD52	FD52

CANNOT_ABORT	-687	0xFFFFFD51	FD51

CACHE_OVERFLOW	-688	0xFFFFFD50	FD50

INVALID_SUBORDINATE_COUNT	-689	0xFFFFFD4F	FD4F

INVALID_RDN	-690	0xFFFFFD4E	FD4E

MOD_TIME_NOT_CURRENT	-691	0xFFFFFD4D	FD4D

INCORRECT_BASE_CLASS	-692	0xFFFFFD4C	FD4C

MISSING_REFERENCE	-693	0xFFFFFD4B	FD4B

Explanation: A required reference is missing from the object. This error is frequently seen in the 4.1 utilities when trying to delete an object with a zero creation timestamp.

Server Action: Run the latest version of the 4.1 DSRepair on the server. This will give objects with missing creation timestamps a valid timestamp. If the object continues to give a -693 error during deletion, then there is still a server in that partition's replica list with a zero creation timestamp for that object. Run the latest DSRepair on each server in that partition's replica list.

LOST_ENTRY	-694	0xFFFFFD4A	FD4A

AGENT_ALREADY_REGISTERED	-695	0xFFFFFD49	FD49

DS_LOADER_BUSY	-696	0xFFFFFD48	FD48

DS_CANNOT_RELOAD	-697	0xFFFFFD47	FD47

REPLICA_IN_SKULK	-698	0xFFFFFD46	FD46

Explanation: The replica is busy skulking and no other replica processes will be done until the skulk has completed.

Server Action: Usually this error will go occur as a normal part of a partition operation and will resolve itself. If this error does not go away, check for other errors as reasons for the partition operation not completing successfully. Remember that the master replica is controlling all partition operations.

FATAL	-699	0xFFFFFD45	FD45

Explanation: An unrecoverable error has occurred and the operation cannot be completed. This error can be caused by a variety of problems.

Server Action: Go to the target server and look for a response TRACE error (turn off the DSTRACE filters by using a setting like FFFF6FF7 or 8164B19 in 4.0x or a8164b91 in 4.1). Sometimes you will see an error without an error code (such as "skulk lost entry") which can also be important. Resolve the error on the target server. Treat a "skulk lost entry" error the same as a -601 error.

Other Error Codes

-1 FFFFFFFF	"DSERR_INSUFFICIENT_SPACE"

-119 FFFFFF89	"DSERR_BUFFER_TOO_SMALL"

-120 FFFFFF88	"DSERR_VOLUME_FLAG_NOT_SET "

-121 FFFFFF87	"DSERR_NO_ITEMS_FOUND"

-122 FFFFFF86	"DSERR_CONN_ALREADY_TEMPORARY"

-123 FFFFFF85	"DSERR_CONN_ALREADY_LOGGED_IN"

-124 FFFFFF84	"DSERR_CONN_NOT_AUTHENTICATED"

-125 FFFFFF83	"DSERR_CONN_NOT_LOGGED_IN"

-126 FFFFFF82	"DSERR_NCP_BOUNDARY_CHECK_FAILED"

-127 FFFFFF81	"DSERR_LOCK_WAITING"

-128 FFFFFF80	"DSERR_LOCK_FAIL"

-129 FFFFFF7F	"DSERR_OUT_OF_HANDLES"

-130 FFFFFF7E	"DSERR_NO_OPEN_PRIVILEGE"

-131 FFFFFF7D	"DSERR_HARD_IO_ERROR"

-132 FFFFFF7C	"DSERR_NO_CREATE_PRIVILEGE "

-133 FFFFFF7B	"DSERR_NO_CREATE_DELETE_PRIV"

-134 FFFFFF7A	"DSERR_R_O_CREATE_FILE"

-135 FFFFFF79	"DSERR_CREATE_FILE_INVALID_NAME"

-136 FFFFFF78	"DSERR_INVALID_FILE_HANDLE "

-137 FFFFFF77	"DSERR_NO_SEARCH_PRIVILEGE "

-138 FFFFFF76	"DSERR_NO_DELETE_PRIVILEGE "

-139 FFFFFF75	"DSERR_NO_RENAME_PRIVILEGE "

-140 FFFFFF74	"DSERR_NO_SET_PRIVILEGE"

-141 FFFFFF73	"DSERR_SOME_FILES_IN_USE"

-142 FFFFFF72	"DSERR_ALL_FILES_IN_USE"

-143 FFFFFF71	"DSERR_SOME_READ_ONLY"

-144 FFFFFF70	"DSERR_ALL_READ_ONLY"

-145 FFFFFF6F	"DSERR_SOME_NAMES_EXIST"

-146 FFFFFF6E	"DSERR_ALL_NAMES_EXIST"

-147 FFFFFF6D	"DSERR_NO_READ_PRIVILEGE"

-148 FFFFFF6C	"DSERR_NO_WRITE_PRIVILEGE"

-149 FFFFFF6B	"DSERR_FILE_DETACHED"

-150 FFFFFF6A	"DSERR_NO_ALLOC_SPACE"

-150 FFFFFF6A	"DSERR_TARGET_NOT_A_SUBDIR"

-150 FFFFFF6A	"ERR_INSUFFICIENT_MEMORY"

-151 FFFFFF69	"DSERR_NO_SPOOL_SPACE"

-152 FFFFFF68	"DSERR_INVALID_VOLUME"

-153 FFFFFF67	"DSERR_DIRECTORY_FULL"

-154 FFFFFF66	"DSERR_RENAME_ACROSS_VOLUME"

-155 FFFFFF65	"DSERR_BAD_DIR_HANDLE"

-156 FFFFFF64	"DSERR_INVALID_PATH"

-156 FFFFFF64	"DSERR_NO_SUCH_EXTENSION"

-157 FFFFFF63	"DSERR_NO_DIR_HANDLES"

-158 FFFFFF62	"DSERR_BAD_FILE_NAME"

-159 FFFFFF61	"DSERR_DIRECTORY_ACTIVE"

-160 FFFFFF60	"DSERR_DIRECTORY_NOT_EMPTY "

-161 FFFFFF5F	"DSERR_DIRECTORY_IO_ERROR"

-162 FFFFFF5E	"DSERR_IO_LOCKED"

-163 FFFFFF5D	"DSERR_TRANSACTION_RESTARTED"

-164 FFFFFF5C	"DSERR_RENAME_DIR_INVALID"

-165 FFFFFF5B	"DSERR_INVALID_OPENCREATE_MODE"

-166 FFFFFF5A	"DSERR_ALREADY_IN_USE"

-167 FFFFFF59	"DSERR_INVALID_RESOURCE_TAG"

-168 FFFFFF58	"DSERR_ACCESS_DENIED"

-190 FFFFFF42	"DSERR_INVALID_DATA_STREAM "

-191 FFFFFF41	"DSERR_INVALID_NAME_SPACE"

-192 FFFFFF40	"DSERR_NO_ACCOUNTING_PRIVILEGES"

-193 FFFFFF3F	"DSERR_NO_ACCOUNT_BALANCE"

-194 FFFFFF3E	"DSERR_CREDIT_LIMIT_EXCEEDED"

-195 FFFFFF3D	"DSERR_TOO_MANY_HOLDS"

-196 FFFFFF3C	"DSERR_ACCOUNTING_DISABLED "

-197 FFFFFF3B	"DSERR_LOGIN_LOCKOUT"

-198 FFFFFF3A	"DSERR_NO_CONSOLE_RIGHTS"

-208 FFFFFF30	"DSERR_Q_IO_FAILURE"

-209 FFFFFF2F	"DSERR_NO_QUEUE"

-210 FFFFFF2E	"DSERR_NO_Q_SERVER "

-211 FFFFFF2D	"DSERR_NO_Q_RIGHTS "

-212 FFFFFF2C	"DSERR_Q_FULL"

-213 FFFFFF2B	"DSERR_NO_Q_JOB"

-214 FFFFFF2A	"DSERR_NO_Q_JOB_RIGHTS"

-214 FFFFFF2A	"DSERR_UNENCRYPTED_NOT_ALLOWED"

-215 FFFFFF29	"DSERR_Q_IN_SERVICE"

-215 FFFFFF29	"DSERR_DUPLICATE_PASSWORD"

-216 FFFFFF28	"DSERR_Q_NOT_ACTIVE"

-216 FFFFFF28	"DSERR_PASSWORD_TOO_SHORT"

-217 FFFFFF27	"DSERR_Q_STN_NOT_SERVER"

-217 FFFFFF27	"DSERR_MAXIMUM_LOGINS_EXCEEDED"

-218 FFFFFF26	"DSERR_Q_HALTED"

-218 FFFFFF26	"DSERR_BAD_LOGIN_TIME"

-219 FFFFFF25	"DSERR_Q_MAX_SERVERS"

-219 FFFFFF25	"DSERR_NODE_ADDRESS_VIOLATION"

-220 FFFFFF24	"DSERR_LOG_ACCOUNT_EXPIRED "

-222 FFFFFF22	"DSERR_BAD_PASSWORD"

-223 FFFFFF21	"DSERR_PASSWORD_EXPIRED"

-224 FFFFFF20	"DSERR_NO_LOGIN_CONN_AVAILABLE"

-232 FFFFFF18	"DSERR_WRITE_TO_GROUP_PROPERTY"

-233 FFFFFF17	"DSERR_MEMBER_ALREADY_EXISTS"

-234 FFFFFF16	"DSERR_NO_SUCH_MEMBER"

-235 FFFFFF15	"DSERR_PROPERTY_NOT_GROUP"

-236 FFFFFF14	"DSERR_NO_SUCH_VALUE_SET"

-237 FFFFFF13	"DSERR_PROPERTY_ALREADY_EXISTS"

-238 FFFFFF12	"DSERR_OBJECT_ALREADY_EXISTS"

-239 FFFFFF11	"DSERR_ILLEGAL_NAME"

-240 FFFFFF10	"DSERR_ILLEGAL_WILDCARD"

-241 FFFFFF0F	"DSERR_BINDERY_SECURITY"

-242 FFFFFF0E	"DSERR_NO_OBJECT_READ_RIGHTS"

-243 FFFFFF0D	"DSERR_NO_OBJECT_RENAME_RIGHTS"

-244 FFFFFF0C	"DSERR_NO_OBJECT_DELETE_RIGHTS"

-245 FFFFFF0B	"DSERR_NO_OBJECT_CREATE_RIGHTS"

-246 FFFFFF0A	"DSERR_NO_PROPERTY_DELETE_RIGHTS"

-247 FFFFFF09	"DSERR_NO_PROPERTY_CREATE_RIGHTS"

-248 FFFFFF08	"DSERR_NO_PROPERTY_WRITE_RIGHTS"

-249 FFFFFF07	"DSERR_NO_PROPERTY_READ_RIGHTS"

-250 FFFFFF06	"DSERR_TEMP_REMAP"

-251 FFFFFF05	"DSERR_UNKNOWN_REQUEST"

-251 FFFFFF05	"DSERR_NO_SUCH_PROPERTY"

-251 FFFFFF05	"ERR_REQUEST_UNKNOWN"

-252 FFFFFF04	"DSERR_MESSAGE_QUEUE_FULL"

-252 FFFFFF04	"DSERR_TARGET_ALREADY_HAS_MSG"

-252 FFFFFF04	"DSERR_NO_SUCH_OBJECT"

-253 FFFFFF03	"DSERR_BAD_STATION_NUMBER"

-254 FFFFFF02	"DSERR_BINDERY_LOCKED"

Action: Make sure login is enabled on the target server

-254 FFFFFF02	"DSERR_DIR_LOCKED"

-254 FFFFFF02	"DSERR_SPOOL_DELETE"

-254 FFFFFF02	"DSERR_TRUSTEE_NOT_FOUND"

-255 FFFFFF01	"DSERR_HARD_FAILURE"

-255 FFFFFF01	"DSERR_FILE_NAME"

-255 FFFFFF01	"DSERR_FILE_EXISTS "

-255 FFFFFF01	"DSERR_CLOSE_FCB"

-255 FFFFFF01	"DSERR_IO_BOUND"

-255 FFFFFF01	"DSERR_NO_SPOOL_FILE"

-255 FFFFFF01	"DSERR_BAD_SPOOL_PRINTER"

-255 FFFFFF01	"DSERR_BAD_PARAMETER"

-255 FFFFFF01	"DSERR_NO_FILES_FOUND"

-255 FFFFFF01	"DSERR_NO_TRUSTEE_CHANGE_PRIV "

-255 FFFFFF01	"DSERR_TARGET_NOT_LOGGED_IN"

-255 FFFFFF01	"DSERR_TARGET_NOT_ACCEPTING_MSGS"

-255 FFFFFF01	"DSERR_MUST_FORCE_DOWN"

-255 FFFFFF01	"ERR_OF_SOME_SORT"

-301 FFFFFED3	"ERR_NOT_ENOUGH_MEMORY"

-302 FFFFFED2	"ERR_BAD_KEY"

-303 FFFFFED1	"ERR_BAD_CONTEXT "

-304 FFFFFED0	"ERR_BUFFER_FULL"

-305 FFFFFECF	"ERR_LIST_EMPTY"

-306 FFFFFECE	"ERR_BAD_SYNTAX"

-307 FFFFFECD	"ERR_BUFFER_EMPTY"

-308 FFFFFECC	"ERR_BAD_VERB"

-309 FFFFFECB	"ERR_EXPECTED_IDENTIFIER"

-310 FFFFFECA	"ERR_EXPECTED_EQUALS"

-311 FFFFFEC9	"ERR_ATTR_TYPE_EXPECTED"

-312 FFFFFEC8	"ERR_ATTR_TYPE_NOT_EXPECTED"

-313 FFFFFEC7	"ERR_FILTER_TREE_EMPTY"

-314 FFFFFEC6	"ERR_INVALID_OBJECT_NAME"

-315 FFFFFEC5	"ERR_EXPECTED_RDN_DELIMITER"

-316 FFFFFEC4	"ERR_TOO_MANY_TOKENS"

-317 FFFFFEC3	"ERR_INCONSISTENT_MULTIAVA"

-318 FFFFFEC2	"ERR_COUNTRY_NAME_TOO_LONG"

-319 FFFFFEC1	"ERR_SYSTEM_ERROR"

-320 FFFFFEC0	"ERR_CANT_ADD_ROOT"

-321 FFFFFEBF	"ERR_UNABLE_TO_ATTACH"

-322 FFFFFEBE	"ERR_INVALID_HANDLE"

-323 FFFFFEBD	"ERR_BUFFER_ZERO_LENGTH "

-324 FFFFFEBC	"ERR_INVALID_REPLICA_TYPE"

-325 FFFFFEBB	"ERR_INVALID_ATTR_SYNTAX"

-326 FFFFFEBA	"ERR_INVALID_FILTER_SYNTAX"

-328 FFFFFEB8	"ERR_CONTEXT_CREATION"

-329 FFFFFEB7	"ERR_INVALID_UNION_TAG"

-330 FFFFFEB6	"ERR_INVALID_SERVER_RESPONSE"

-331 FFFFFEB5	"ERR_NULL_POINTER"

-332 FFFFFEB4	"ERR_NO_SERVER_FOUND"

-333 FFFFFEB3	"ERR_NO_CONNECTION"

-334 FFFFFEB2	"ERR_RDN_TOO_LONG"

-335 FFFFFEB1	"ERR_DUPLICATE_TYPE"

-336 FFFFFEB0	"ERR_DATA_STORE_FAILURE"

-337 FFFFFEAF	"ERR_NOT_LOGGED_IN"

-338 FFFFFEAE	"ERR_INVALID_PASSWORD_CHARS"

-339 FFFFFEAD	"ERR_FAILED_SERVER_AUTHENT"

-340 FFFFFEAC	"ERR_TRANSPORT"

-341 FFFFFEAB	"ERR_NO_SUCH_SYNTAX"

-342 FFFFFEAA	"ERR_INVALID_DS_NAME"

-343 FFFFFEA9	"ERR_ATTR_NAME_TOO_LONG "

-344 FFFFFEA8	"ERR_INVALID_TDS"

-345 FFFFFEA7	"ERR_INVALID_DS_VERSION"

-346 FFFFFEA6	"ERR_UNICODE_TRANSLATION"

-347 FFFFFEA5	"ERR_SCHEMA_NAME_TOO_LONG "

-348 FFFFFEA4	"ERR_UNICODE_FILE_NOT_FOUND "

-349 FFFFFEA3	"ERR_UNICODE_ALREADY_LOADED"

-350 FFFFFEA2	"ERR_NOT_CONTEXT_OWNER"

-351 FFFFFEA1	"ERR_ATTEMPT_TO_AUTHENTICATE_0"

-352 FFFFFEA0	"ERR_NO_WRITABLE_REPLICAS"

-353 FFFFFE9F	"ERR_DN_TOO_LONG"

-354 FFFFFE9E	"ERR_RENAME_NOT_ALLOWED"