PmUkSA @ @i @0FAiTable1@ColA9 ColB9ColA10 ColB10ColA12 ColB12ColA13 ColB13ColA14 ColB14ColA15 ColB15ColA16 ColB16ColA17 ColB17ColA18 ColB18ColA19 ColB19ColA20 ColB20ColA21 ColB21ColA22 ColB22ColA23 ColB23ColA24 ColB24ColA25 ColB25@ &n @"Data.app @OB Table1 .Description dCode d"Long Hex dHex dMemo  dMemo2  dMemo3  dMemo4  dMemo5  dMemo6  dMemo7  dMemo8  dMemo9  dMemoA  dMemoB  dMemoC  ddC               OOOOOOOOOOOOOOOO               OOOOOOOOOOOOOOOOc@O& * @\cefd\c efd.A@71@ .12 3 7 C &nsikX E+U NO_SUCH_ENTRY-601 0xFFFFFDA7FDA7UExplanation: 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 commandline 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 theleading 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 NETADMINto 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 returningthe -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 thisiwill only help if the source server is the Master). BUT BEWARE! Send All Objects CAUSES A LOT OF TRAFFIC!U NO_SUCH_VALUE-602 0xFFFFFDA6FDA6UExplanation: 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 thetarget 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, runUthis 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 unlessthere 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 asubordinate 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= 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.UDIFFERENT_TREE-630 0xFFFFFD8AFD8AUILLEGAL_REPLICA_TYPE-631 0xFFFFFD89FD89Explanation: 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 whenattempting 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 attemptingto set the bindery context.USYSTEM_FAILURE-632 0xFFFFFD88FD88UExplanation: 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 betemporary. 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 becauseauthentication 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,Uthe 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 databaseis 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 onevery 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.K ReV`TUINVALID_ENTRY_FOR_ROOT-633 0xFFFFFD87FD87Explanation: 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.U NO_REFERRALS-634 0xFFFFFD86FD86Explanation: 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.aAction: This is not a serious error, but just a response. This error will usually resolve itself.UREMOTE_FAILURE-635 0xFFFFFD85FD85Explanation: 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 correctinformation 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 DSREPAIRa 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.UUNREACHABLE_SERVER-636 0xFFFFFD84FD84UPREVIOUS_MOVE_IN_PROGRESS-637 0xFFFFFD83FD83UExplanation: 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 completewill 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 whichUwill 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 -MRN(load the 4.0x DSREPAIR with -A, Select Options, then toggle A until it reads |) which will then delete the move obituaries for those problem objects. Use SET DSTRACE=+J and SET DSTRACE=*F to verify thatthe purger ran successfully.UNO_CHARACTER_MAPPING-638 0xFFFFFD82FD82UINCOMPLETE_AUTHENTICATION-639 0xFFFFFD81FD81UINVALID_CERTIFICATE-640 0xFFFFFD80FD80nFU=XeRUINVALID_REQUEST-641 0xFFFFFD7FFD7FExplanation: 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.UINVALID_ITERATION-642 0xFFFFFD7EFD7ECExplanation: A client workstation sent an invalid iteration handle.USCHEMA_IS_NONREMOVABLE-643 0xFFFFFD7DFD7DMExplanation: An attempt was made to delete an NDS structure or configuration.USCHEMA_IS_IN_USE-644 0xFFFFFD7CFD7CExplanation: 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.UCLASS_ALREADY_EXISTS-645 0xFFFFFD7BFD7BExplanation: 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 theAschema of the Directory. Determine the utility causing the error.UBAD_NAMING_ATTRIBUTES-646 0xFFFFFD7AFD7AUNOT_ROOT_PARTITION-647 0xFFFFFD79FD79Explanation: 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.UINSUFFICIENT_STACK-648 0xFFFFFD78FD78YGXNTR UUINSUFFICIENT_BUFFER-649 0xFFFFFD77FD77xExplanation: The server ran out of memory. The operating system will self-correct this error. Action: Be patient. See  in Supervising the Network.UAMBIGUOUS_CONTAINMENT-650 0xFFFFFD76FD76UAMBIGUOUS_NAMING-651 0xFFFFFD75FD75UDUPLICATE_MANDATORY-652 0xFFFFFD74FD74UDUPLICATE_OPTIONAL-653 0xFFFFFD73FD73UPARTITION_BUSY-654 0xFFFFFD72FD72UExplanation: 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 serverhas 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 fromCthe tree or call your Novell Authorized Service Center for support.UMULTIPLE_REPLICAS-655 0xFFFFFD71FD71kExplanation: An internal error that appears as a result of a programming error, not a system inconsistency.UCRUCIAL_REPLICA-656 0xFFFFFD70FD70Explanation: 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 whichwill 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.@HXVUSCHEMA_SYNC_IN_PROGRESS-657 0xFFFFFD6FFD6FExplanation: The function could not be completed because Directory synchronization is in progress. Action: Wait a while and try again.USKULK_IN_PROGRESS-658 0xFFFFFD6EFD6EExplanation: The function could not be completed because replica synchronization is in progress. Action: Wait a while and try again.UTIME_NOT_SYNCHRONIZED-659 0xFFFFFD6DFD6DUExplanation: 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 operationsrequire 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 lastmodification 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.UAction: 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 Replicasand 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, thatcorruption 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 apartition by partition basis.U RECORD_IN_USE-660 0xFFFFFD6CFD6CUDS_VOLUME_NOT_MOUNTED-661 0xFFFFFD6BFD6BUDS_VOLUME_IO_FAILURE-662 0xFFFFFD6AFD6AU DS_LOCKED-663 0xFFFFFD69FD69UExplanation: 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 onthe 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 thedirectory 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 treeU(**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 fromthe 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 removala 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 doa clean removal.O)حLJU OLD_EPOCH-664 0xFFFFFD68FD68-Explanation: This is an NDS time stamp error.U NEW_EPOCH-665 0xFFFFFD67FD67-Explanation: This is an NDS time stamp error.UINCOMPATIBLE_DS_VERSION-666 0xFFFFFD66FD66UExplanation: 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 requestedand 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 returnthis 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 upgradedto 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 onthe 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.UPARTITION_ROOT-667 0xFFFFFD65FD65Explanation: 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 theKpartition management tools, merge this partition into the parent partition.UENTRY_NOT_CONTAINER-668 0xFFFFFD64FD64@Explanation: An illegal function was attempted on a leaf object.UFAILED_AUTHENTICATION-669 0xFFFFFD63FD63UExplanation: 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 IDsonce 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 serverUobject) 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 S copy has the Master). BE CAREFUL AND DON'T SEND A BAD PUBLIC KEY!!! Also, rememberthat 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 sourceserver 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.UINVALID_CONTEXT-670 0xFFFFFD62FD62UNO_SUCH_PARENT-671 0xFFFFFD61FD61D VFTNH^U NO_ACCESS-672 0xFFFFFD60FD60Explanation: 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.UREPLICA_NOT_ON-673 0xFFFFFD5FFD5FExplanation: 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).mServer Action: Wait. If the replica is stuck, look for the error that is preventing the replica from turning  and address that problem.UINVALID_NAME_SERVICE-674 0xFFFFFD5EFD5EU INVALID_TASK-675 0xFFFFFD5DFD5DUINVALID_CONN_HANDLE-676 0xFFFFFD5CFD5CUINVALID_IDENTITY-677 0xFFFFFD5BFD5BU DUPLICATE_ACL-678 0xFFFFFD5AFD5AUPARTITION_ALREADY_EXISTS-679 0xFFFFFD59FD59MARPLTVNRFUTRANSPORT_MODIFIED-680 0xFFFFFD58FD58UALIAS_OF_AN_ALIAS-681 0xFFFFFD57FD57UAUDITING_FAILED-682 0xFFFFFD56FD56UINVALID_API_VERSION-683 0xFFFFFD55FD55USECURE_NCP_VIOLATION-684 0xFFFFFD54FD54UMOVE_IN_PROGRESS-685 0xFFFFFD53FD53UNOT_LEAF_PARTITION-686 0xFFFFFD52FD52U CANNOT_ABORT-687 0xFFFFFD51FD51CJ`DVV B^UCACHE_OVERFLOW-688 0xFFFFFD50FD50UINVALID_SUBORDINATE_COUNT-689 0xFFFFFD4FFD4FU INVALID_RDN-690 0xFFFFFD4EFD4EUMOD_TIME_NOT_CURRENT-691 0xFFFFFD4DFD4DUINCORRECT_BASE_CLASS-692 0xFFFFFD4CFD4CUMISSING_REFERENCE-693 0xFFFFFD4BFD4BExplanation: 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 DSRepairon 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 timestampYfor that object. Run the latest DSRepair on each server in that partition's replica list.U LOST_ENTRY-694 0xFFFFFD4AFD4AUAGENT_ALREADY_REGISTERED-695 0xFFFFFD49FD49EJN]ZZ`VUDS_LOADER_BUSY-696 0xFFFFFD48FD48UDS_CANNOT_RELOAD-697 0xFFFFFD47FD47UREPLICA_IN_SKULK-698 0xFFFFFD46FD46Explanation: 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.UFATAL-699 0xFFFFFD45FD45Explanation: 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 filtersby 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 a2'skulk lost entry' error the same as a -601 error.UDSERR_INSUFFICIENT_SPACE-1 0xFFFFFFFFFFFFUDSERR_BUFFER_TOO_SMALL-119 0xFFFFFF89FF89UDSERR_VOLUME_FLAG_NOT_SET-120 0xFFFFFF88FF88UDSERR_NO_ITEMS_FOUND-121 0xFFFFFF87FF87Afff^jRLVUDSERR_CONN_ALREADY_TEMPORARY-122 0xFFFFFF86FF86UDSERR_CONN_ALREADY_LOGGED_IN-123 0xFFFFFF85FF85UDSERR_CONN_NOT_AUTHENTICATED-124 0xFFFFFF84FF84UDSERR_CONN_NOT_LOGGED_IN-125 0xFFFFFF83FF83UDSERR_NCP_BOUNDARY_CHECK_FAILE-126 0xFFFFFF82FF82UDSERR_LOCK_WAITING-127 0xFFFFFF81FF81UDSERR_LOCK_FAIL-128 0xFFFFFF80FF80UDSERR_OUT_OF_HANDLES-129 0xFFFFFF7FFF7FA\T`dXj``UDSERR_NO_OPEN_PRIVILEGE-130 0xFFFFFF7EFF7EUDSERR_HARD_IO_ERROR-131 0xFFFFFF7DFF7DUDSERR_NO_CREATE_PRIVILEGE-132 0xFFFFFF7CFF7CUDSERR_NO_CREATE_DELETE_PRIV-133 0xFFFFFF7BFF7BUDSERR_R_O_CREATE_FILE-134 0xFFFFFF7AFF7AUDSERR_CREATE_FILE_INVALID_NAME-135 0xFFFFFF79FF79UDSERR_INVALID_FILE_HANDLE-136 0xFFFFFF78FF78UDSERR_NO_SEARCH_PRIVILEGE-137 0xFFFFFF77FF77xA``Z\ZVTZUDSERR_NO_DELETE_PRIVILEGE-138 0xFFFFFF76FF76UDSERR_NO_RENAME_PRIVILEGE-139 0xFFFFFF75FF75UDSERR_NO_SET_PRIVILEGE-140 0xFFFFFF74FF74UDSERR_SOME_FILES_IN_USE-141 0xFFFFFF73FF73UDSERR_ALL_FILES_IN_USE-142 0xFFFFFF72FF72UDSERR_SOME_READ_ONLY-143 0xFFFFFF71FF71UDSERR_ALL_READ_ONLY-144 0xFFFFFF70FF70UDSERR_SOME_NAMES_EXIST-145 0xFFFFFF6FFF6FuAX\^TV`\VUDSERR_ALL_NAMES_EXIST-146 0xFFFFFF6EFF6EUDSERR_NO_READ_PRIVILEGE-147 0xFFFFFF6DFF6DUDSERR_NO_WRITE_PRIVILEGE-148 0xFFFFFF6CFF6CUDSERR_FILE_DETACHED-149 0xFFFFFF6BFF6BUDSERR_NO_ALLOC_SPACE-150 0xFFFFFF6AFF6AUDSERR_TARGET_NOT_A_SUBDIR-150 0xFFFFFF6AFF6AUERR_INSUFFICIENT_MEMORY-150 0xFFFFFF6AFF6AUDSERR_NO_SPOOL_SPACE-151 0xFFFFFF69FF69lAVVbVR\VTUDSERR_INVALID_VOLUME-152 0xFFFFFF68FF68UDSERR_DIRECTORY_FULL-153 0xFFFFFF67FF67UDSERR_RENAME_ACROSS_VOLUME-154 0xFFFFFF66FF66UDSERR_BAD_DIR_HANDLE-155 0xFFFFFF65FF65UDSERR_INVALID_PATH-156 0xFFFFFF64FF64UDSERR_NO_SUCH_EXTENSION-156 0xFFFFFF64FF64UDSERR_NO_DIR_HANDLES-157 0xFFFFFF63FF63UDSERR_BAD_FILE_NAME-158 0xFFFFFF62FF62AZ`^Ld^hVUDSERR_DIRECTORY_ACTIVE-159 0xFFFFFF61FF61UDSERR_DIRECTORY_NOT_EMPTY-160 0xFFFFFF60FF60UDSERR_DIRECTORY_IO_ERROR-161 0xFFFFFF5FFF5FUDSERR_IO_LOCKED-162 0xFFFFFF5EFF5EUDSERR_TRANSACTION_RESTARTED-163 0xFFFFFF5DFF5DUDSERR_RENAME_DIR_INVALID-164 0xFFFFFF5CFF5CUDSERR_INVALID_OPENCREATE_MODE-165 0xFFFFFF5BFF5BUDSERR_ALREADY_IN_USE-166 0xFFFFFF5AFF5AA bT`^j^dVUDSERR_INVALID_RESOURCE_TAG-167 0xFFFFFF59FF59UDSERR_ACCESS_DENIED-168 0xFFFFFF58FF58UDSERR_INVALID_DATA_STREAM-190 0xFFFFFF42FF42UDSERR_INVALID_NAME_SPACE-191 0xFFFFFF41FF41UDSERR_NO_ACCOUNTING_PRIVILEGES-192 0xFFFFFF40FF40UDSERR_NO_ACCOUNT_BALANCE-193 0xFFFFFF3FFF3FUDSERR_CREDIT_LIMIT_EXCEEDED-194 0xFFFFFF3EFF3EUDSERR_TOO_MANY_HOLDS-195 0xFFFFFF3DFF3DWA!`T\RJPPFUDSERR_ACCOUNTING_DISABLED-196 0xFFFFFF3CFF3CUDSERR_LOGIN_LOCKOUT-197 0xFFFFFF3BFF3BUDSERR_NO_CONSOLE_RIGHTS-198 0xFFFFFF3AFF3AUDSERR_Q_IO_FAILURE-208 0xFFFFFF30FF30UDSERR_NO_QUEUE-209 0xFFFFFF2FFF2FUDSERR_NO_Q_SERVER-210 0xFFFFFF2EFF2EUDSERR_NO_Q_RIGHTS-211 0xFFFFFF2DFF2DU DSERR_Q_FULL-212 0xFFFFFF2CFF2CpA"JXhR^R^ZUDSERR_NO_Q_JOB-213 0xFFFFFF2BFF2BUDSERR_NO_Q_JOB_RIGHTS-214 0xFFFFFF2AFF2AUDSERR_UNENCRYPTED_NOT_ALLOWED-214 0xFFFFFF2AFF2AUDSERR_Q_IN_SERVICE-215 0xFFFFFF29FF29UDSERR_DUPLICATE_PASSWORD-215 0xFFFFFF29FF29UDSERR_Q_NOT_ACTIVE-216 0xFFFFFF28FF28UDSERR_PASSWORD_TOO_SHORT-216 0xFFFFFF28FF28UDSERR_Q_STN_NOT_SERVER-217 0xFFFFFF27FF27uA#hJVTf`RZUDSERR_MAXIMUM_LOGINS_EXCEEDED-217 0xFFFFFF27FF27UDSERR_Q_HALTED-218 0xFFFFFF26FF26UDSERR_BAD_LOGIN_TIME-218 0xFFFFFF26FF26UDSERR_Q_MAX_SERVERS-219 0xFFFFFF25FF25UDSERR_NODE_ADDRESS_VIOLATION-219 0xFFFFFF25FF25UDSERR_LOG_ACCOUNT_EXPIRED-220 0xFFFFFF24FF24UDSERR_BAD_PASSWORD-222 0xFFFFFF22FF22UDSERR_PASSWORD_EXPIRED-223 0xFFFFFF21FF21A$hhdV^\hdUDSERR_NO_LOGIN_CONN_AVAILABLE-224 0xFFFFFF20FF20UDSERR_WRITE_TO_GROUP_PROPERTY-232 0xFFFFFF18FF18UDSERR_MEMBER_ALREADY_EXISTS-233 0xFFFFFF17FF17UDSERR_NO_SUCH_MEMBER-234 0xFFFFFF16FF16UDSERR_PROPERTY_NOT_GROUP-235 0xFFFFFF15FF15UDSERR_NO_SUCH_VALUE_SET-236 0xFFFFFF14FF14UDSERR_PROPERTY_ALREADY_EXISTS-237 0xFFFFFF13FF13UDSERR_OBJECT_ALREADY_EXISTS-238 0xFFFFFF12FF12A%RZZdhhhjUDSERR_ILLEGAL_NAME-239 0xFFFFFF11FF11UDSERR_ILLEGAL_WILDCARD-240 0xFFFFFF10FF10UDSERR_BINDERY_SECURITY-241 0xFFFFFF0FFF0FUDSERR_NO_OBJECT_READ_RIGHTS-242 0xFFFFFF0EFF0EUDSERR_NO_OBJECT_RENAME_RIGHTS-243 0xFFFFFF0DFF0DUDSERR_NO_OBJECT_DELETE_RIGHTS-244 0xFFFFFF0CFF0CUDSERR_NO_OBJECT_CREATE_RIGHTS-245 0xFFFFFF0BFF0BUDSERR_NO_PROPERTY_DELETE_RIGHT-246 0xFFFFFF0AFF0AA&jjhNXZT^UDSERR_NO_PROPERTY_CREATE_RIGHT-247 0xFFFFFF09FF09UDSERR_NO_PROPERTY_WRITE_RIGHTS-248 0xFFFFFF08FF08UDSERR_NO_PROPERTY_READ_RIGHTS-249 0xFFFFFF07FF07UDSERR_TEMP_REMAP-250 0xFFFFFF06FF06UDSERR_UNKNOWN_REQUEST-251 0xFFFFFF05FF05UDSERR_NO_SUCH_PROPERTY-251 0xFFFFFF05FF05UERR_REQUEST_UNKNOWN-251 0xFFFFFF05FF05UDSERR_MESSAGE_QUEUE_FULL-252 0xFFFFFF04FF04@'fV^NR\RUDSERR_TARGET_ALREADY_HAS_MSG-252 0xFFFFFF04FF04UDSERR_NO_SUCH_OBJECT-252 0xFFFFFF04FF04UDSERR_BAD_STATION_NUMBER-253 0xFFFFFF03FF03UDSERR_BINDERY_LOCKED-254 0xFFFFFF02FF027Action: Make sure login is enabled on the target serverUDSERR_DIR_LOCKED-254 0xFFFFFF02FF02UDSERR_SPOOL_DELETE-254 0xFFFFFF02\FF02UDSERR_TRUSTEE_NOT_FOUND-254 0xFFFFFF02FF02UDSERR_HARD_FAILURE-255 0xFFFFFF01FF01TA(LPLJT\TVUDSERR_FILE_NAME-255 0xFFFFFF01FF01UDSERR_FILE_EXISTS-255 0xFFFFFF01FF01UDSERR_CLOSE_FCB-255 0xFFFFFF01FF01UDSERR_IO_BOUND-255 0xFFFFFF01FF01UDSERR_NO_SPOOL_FILE-255 0xFFFFFF01FF01UDSERR_BAD_SPOOL_PRINTER-255 0xFFFFFF01FF01UDSERR_BAD_PARAMETER-255 0xFFFFFF01FF01UDSERR_NO_FILES_FOUND-255 0xFFFFFF01FF01nA)fbjXNXDLUDSERR_NO_TRUSTEE_CHANGE_PRIV-255 0xFFFFFF01FF01UDSERR_TARGET_NOT_LOGGED_IN-255 0xFFFFFF01FF01UDSERR_TARGET_NOT_ACCEPTING_MSG-255 0xFFFFFF01FF01UDSERR_MUST_FORCE_DOWN-255 0xFFFFFF01FF01UERR_OF_SOME_SORT-255 0xFFFFFF01FF01UERR_NOT_ENOUGH_MEMORY-301 0xFFFFFED3FED3U ERR_BAD_KEY-302 0xFFFFFED2FED2UERR_BAD_CONTEXT-303 0xFFFFFED1FED1MA*LJJNF\TZUERR_BUFFER_FULL-304 0xFFFFFED0FED0UERR_LIST_EMPTY-305 0xFFFFFECFFECFUERR_BAD_SYNTAX-306 0xFFFFFECEFECEUERR_BUFFER_EMPTY-307 0xFFFFFECDFECDU ERR_BAD_VERB-308 0xFFFFFECCFECCUERR_EXPECTED_IDENTIFIER-309 0xFFFFFECBFECBUERR_EXPECTED_EQUALS-310 0xFFFFFECAFECAUERR_ATTR_TYPE_EXPECTED-311 0xFFFFFEC9FEC9{A+bX\bT``NUERR_ATTR_TYPE_NOT_EXPECTED-312 0xFFFFFEC8FEC8UERR_FILTER_TREE_EMPTY-313 0xFFFFFEC7FEC7UERR_INVALID_OBJECT_NAME-314 0xFFFFFEC6FEC6UERR_EXPECTED_RDN_DELIMITER-315 0xFFFFFEC5FEC5UERR_TOO_MANY_TOKENS-316 0xFFFFFEC4FEC4UERR_INCONSISTENT_MULTIAVA-317 0xFFFFFEC3FEC3UERR_COUNTRY_NAME_TOO_LONG-318 0xFFFFFEC2FEC2UERR_SYSTEM_ERROR-319 0xFFFFFEC1FEC1oA,PVRZ^\`VUERR_CANT_ADD_ROOT-320 0xFFFFFEC0FEC0UERR_UNABLE_TO_ATTACH-321 0xFFFFFEBFFEBFUERR_INVALID_HANDLE-322 0xFFFFFEBEFEBEUERR_BUFFER_ZERO_LENGTH-323 0xFFFFFEBDFEBDUERR_INVALID_REPLICA_TYPE-324 0xFFFFFEBCFEBCUERR_INVALID_ATTR_SYNTAX-325 0xFFFFFEBBFEBBUERR_INVALID_FILTER_SYNTAX-326 0xFFFFFEBAFEBAUERR_CONTEXT_CREATION-328 0xFFFFFEB8FEB8bA-XdNTPNRZUERR_INVALID_UNION_TAG-329 0xFFFFFEB7FEB7UERR_INVALID_SERVER_RESPONSE-330 0xFFFFFEB6FEB6UERR_NULL_POINTER-331 0xFFFFFEB5FEB5UERR_NO_SERVER_FOUND-332 0xFFFFFEB4FEB4UERR_NO_CONNECTION-333 0xFFFFFEB3FEB3UERR_RDN_TOO_LONG-334 0xFFFFFEB2FEB2UERR_DUPLICATE_TYPE-335 0xFFFFFEB1FEB1UERR_DATA_STORE_FAILURE-336 0xFFFFFEB0FEB0aA.Pb`HRTZLUERR_NOT_LOGGED_IN-337 0xFFFFFEAFFEAFUERR_INVALID_PASSWORD_CHARS-338 0xFFFFFEAEFEAEUERR_FAILED_SERVER_AUTHENT-339 0xFFFFFEADFEADU ERR_TRANSPORT-340 0xFFFFFEACFEACUERR_NO_SUCH_SYNTAX-341 0xFFFFFEABFEABUERR_INVALID_DS_NAME-342 0xFFFFFEAAFEAAUERR_ATTR_NAME_TOO_LONG-343 0xFFFFFEA9FEA9UERR_INVALID_TDS-344 0xFFFFFEA8FEA8A/Z\^bbXh^UERR_INVALID_DS_VERSION-345 0xFFFFFEA7FEA7UERR_UNICODE_TRANSLATION-346 0xFFFFFEA6FEA6UERR_SCHEMA_NAME_TOO_LONG-347 0xFFFFFEA5FEA5UERR_UNICODE_FILE_NOT_FOUND-348 0xFFFFFEA4FEA4UERR_UNICODE_ALREADY_LOADED-349 0xFFFFFEA3FEA3UERR_NOT_CONTEXT_OWNER-350 0xFFFFFEA2FEA2UERR_ATTEMPT_TO_AUTHENTICATE_0-351 0xFFFFFEA1FEA1UERR_NO_WRITABLE_REPLICAS-352 0xFFFFFEA0FEA0@i\@LZUERR_DN_TOO_LONG-353 0xFFFFFE9FFE9FUERR_RENAME_NOT_ALLOWED-354 0xFFFFFE9EFE9E/&sik!3y>?!3= 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.UDIFFERENT_TREE-630 0xFFFFFD8AFD8AUILLEGAL_REPLICA_TYPE-631 0xFFFFFD89FD89Explanation: 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 whenattempting 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 attemptingto set the bindery context.USYSTEM_FAILURE-632 0xFFFFFD88FD88UExplanation: 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 betemporary. 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 becauseauthentication 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,Uthe 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 databaseis 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 onevery 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.6iDs<%'`BBbC!3