NetWare Message File: dsmaint ., Tran 1.0 (-Mq 3E*T 2}y D  K r   V |  & <Y:M]t0%FW_|MU2S#]D@s(|\/] !3!M!!#X#'$]$`$$%c%%%%%& &S&&&&&&'5'C''(().)F)_)p)u)))))/*~**+i+++++C,x,,,,----C.i.|.F..3/F///1p11112R222$3K333544444 5W5554666777)8?8r88889:":g::;$;^;;;7<<<3=Alloc MemoryDSEventDSTrace ProcessScreenTimer002: Unable to allocate resource tag.NDS Maintenance4.10001: Unable to allocate memory.003: Unable to open DSMaint Screen.Exit DSMaint?NetWare NDS Maintenance004: A newer version of NWSNUT is required.005: Unable to initialize NWSNUT.006: Unable to create an NWSNUT portal.Use this option to view the log file.Available OptionsUse this option to enable logging of messages to the DSMaint log file (DSMaint.LOG).Use this option to delete the current log file.Displays the current maximum size of the log file. Use this option to change the maximum size. Cannot connect to %02x%02x%02x%02x NDS files already exist on this server. However, the database is closed. If you confirm "yes" in the following box, the NDS files will be renamed and the operation will continue. Rename the files and continue upgrade?An error occurred adding the address to the unavailable list. Error %d. Successfully replaced %s, property name: %s. ExitUnloads the DSMAINT utility from memory. Enter=Select menu Action Alt+F10=Exit Esc=Exit F1=Help Failed replacing %s, property name: %s. Error %d. An error occurred saving stream files from the Directory. Error %d.Verifying server object. Error closing Directory Services Agent. Error %d.The server object does not have the same creation timestamp as the server in BACKUP.DS. Verifying that the server's keys are valid. The keys of server object do not match those of the server in BACKUP.DS. Finished verifying server object has not changed. Restore NDS following hardware upgradeError checking client's rights on the server object. Error %d.This option requires managed rights on the server object. You do not have that level of access. This server holds the only replica of partition %s. Novell recommends at least three replicas of each partition. Successfully created the file BACKUP.DS with this server's NDS data. This file is located in SYS:SYSTEM.Administrator name:Enter the Distinguished Name of a User object that has administrative rights.Press to continue and log in.Press enter to log in.Password:Enter the password for the User object above.Unable to create Directory Services context. Error %d.Object name is invalid. Error %d.An error occurred during the preparation of the server for a hardware upgrade. Error %d.Successfully restored NDS to the server.DSMaint completed preparing this server for a hardwre upgrade. Unable to connect to local server. Error %d.Unable to locate object. Error %d.Unable to log in. Error %d.Begin preparing this server for hardware upgrade Error creating id map file.Reading replica ring of %s. Log in as an administrative userAn error occurred reading the addresses of the local server's object. Error %d. Logging into tree.Please wait ...Wait message too long.NWSComputePortalPosition was called with height = %d and width = %d.Error creating portal.Begin restoring NDS to this server. Successfully read addresses of the local server object. The only replica of this server's object exists on this server. Novell recommends at least three replicas of every partition. There is only one replica of this server's object. Novell recommends at least three replicas of every partition. Search And Replace Server ObjectBegin search at:Enter a container object's Distinguished Name in the Container Name field. DSMaint searches down the Directory from this container.Server name in BACKUP.DS is %s. This server is not in the replica ring of the partition %s. This operation cannot be completed.Failed to open the log file. Esc=Return to main menu Alt+F10=Exit other hotkeys that are definedVerifying the server's creation time. Failed to allocate sufficient memory to view log file.UnicodeCannot verify that server's object is the same as that found in BACKUP.DS. This operation cannot continue. Error %d. Prepares Directory information stored on this server for a planned hardware upgrade of this server.Prepare NDS for hardware upgradeAn error occurred removing the server's key from the database. Error %d.Uses the file created by the 'Prepare NDS for a Hardware Upgrade' option (BACKUP.DS) to restore Directory Information on this server.The database is locked. Please try this operation later.Error occurred in restoring the Directory to this server. Error %d.Replica count %d. Error getting server's key. Error %d.The replica type of the partition %s on this server used to be %s. This operation cannot be completed.Directory Services is functional on this server. This option is not available. DSMaintmasterread/writeread onlysubordinate referenceUnknown Replica TypeName not availablePress to continue.Looking for the server object in the tree. Press enter to begin searching the Directory tree.An error occurred trying to locate the server object in the tree. Error %d. An error occurred duplicating a context. Error %d.An error occurred opening the file %s. Error %d.The length of the distinguished name of the object in this file is too long. Length %d.Verifying server still in replica ring of %s. Verifying connectivity of %s Replace server referencesSearches the Directory and replaces references to this server in other object's Host Server, Host Device, Message (Default) Server properties.Replacement object:Enter the complete name of an object which will be a placeholder for this server's object.This option is not available. The log file DSMAINT.LOG does not exist and the logging option has been disabled.Version %d of the NDS backup file is not compatible with this version of the utility.Warning: This option leaves DS inoperable on this server. The database will NOT open after this operation is complete. If you confirm "Yes" in the following box, the database will be closed and the DS information copied to SYS:SYSTEM\BACKUP.DS. Information needed to reopen DS will be removed from the database. DSREPAIR.NLM cannot put this information back. Do NOT delete the server object or try to change partition/replica configuration during the time this server is out of service. Continue with upgrade?Successfully verified connectivity for the replica %s. An error occurred reading the file %s. Error description %s."An error occured verifying the local server name and internal net address. Error %d.Successfully replaced references to this server's object in Host Server, Host Device, and Messaging Server properties. Found %d references.An error occurred replacing references to this server's object. Error %d.WARNING: This option replaces references to the selected server's object in Home Directory, Host Server, and Host Device properties. Applications which use those properties to determine the physical location of the server will not work correctly until the server object is correctly referenced. If you confirm "yes" in the following box, the operation will continue. Continue with replacing?Failed verifying connectivity for the replica %s. The server name is not the same as that in the backup file. The server name in the backup file is %s. This server data cannot be restored."The server internal address is not the same as that in the backup file. This server data cannot be restored.Creating Replica List Restore server referencesSearches the DS tree at the selected container and replaces the temporary object with this server's object.WARNING: This option searches the DS tree at the specified container looking for the temporary placeholder object which replaced the references to the selected server's object in Host Server, Host Device, and Messaging Server properties. The temporary object will be removed from these properties and the server's object will be added as the value. /************************************************************Failed verifying connectivity of the replicas this server holds. At least one replica of every partition must be reachable in order for this operation to continue. Number of unreachable partitions: %d. An error occurred opening the local agent. Error %d. An error occurred while checking if this server is the only server in the tree. Error %d. An error occurred writing the server's object information to the file. Error %d.An error occurred writing this server's replica information to the file. Error %d.Trying to connect to address %02x%02x%02x%02x Checking address %02x%02x%02x%02x Saving NDS files. Saving stream files. Disabling NDS on this server. Processing partition %s An error occurred opening the namebase. Error %d.Failed searching container %s. Error %d. An error occurred attempting to restore the server object. Error %d.Creating BACKUP.DSRestoring NDSTree name %s Creating new NDS Saved %d references to this server's object.DSMaint DebugDirectory Services API interface versions do not match. DSMaint internal interface version is: %d DSMaint API interface version is: %d Directory Services API interface version is:%d Could not gain access to Directory Services. Either DS.NLM is not loaded or another NLM has already registered with DS. This could be one of DSI.NLM, DSMERGE.NLM, DSBACKER.NLM, or DSREPAIR.NLM. An error occurred writing to the log file.Log file optionsConfigure options for DSMaintenance log file.Error closing log file.Delete current log file:Enable log file:ViewMaximum size of log file (bytes):Log File OptionsCurrent file size:Restoring NDS files from BACKUP.DS Activate Field for input Return to Previous Screen Help Accept Input Abort Change Help Use arrow keys to scroll display. Return to Options Menu Help Esc=Stop DSMaint Alt+F10=ExitError opening file (BACKUP.DS). This file is expected to be in SYS:SYSTEM. Error %d.Begin searching for server references Searching for Server ReferencesCompleted searching for server references. Found %d server references. Begin replacing references to temporary object with server object Restored %d references to the server's object. An error occurred restoring the supervisor object. Error description %s.Replacing References to Temp ObjectTemporary Object:Restoring streams from BACKUP.DS Enter the complete name of the object which has been acting as a placeholder for this server's object.An error has occurred. The context is initialized. You must log in to perform this operation.Enter server being replaced:Enter the distinguished name of the server which is to be replaced.Search and Replace With Server ObjectEnter server name:Enter the distinguished name of the server object which will replace the temporary object.Replica count at time of backup: %d. Replica list on this server at the time of backup: %s, type %s An error occurred verifying the server object. Error %d.The server object does not match the server in the backup file.The server object being replaced is not the local server. When the server %s is removed from the tree, disconnect it from the rest of the network to avoid deleting the volume objects. After this operation completes and after the server is uninstalled, you may need to delete the server object using the partition management utilities.This server was the only server in the tree. Processing of replica information is complete. The length of the tree name is too long. Length %d. Unable to locate object %s. Error %d. An error occurred reading the backup file %s. Error %d.An error occurred attempting to rebuild the base schema. Error %d.An internal error has occurred. Predefined entry IDs are out of alignment.An internal error has occurred. Cannot insert a predefined entry. Error %d.An internal error has occurred in initializing a table.Cannot add a schema object. Error %d.An error has occurred creating an attribute int the base schema. Error %d.An error has occurred defining a class in the base schema. Error %d.An error has occurred creating the definition of a class in the base schema. Error %d.An error has occurred creating one of the pre-defined partitions. Error %d.<<< BAD MESSAGE >>>An error has occurred updating a pre-defined partition. Error %d.Unable to allocate memory for an internal table.Cannot read the entry for the bindery services supervisor object. Error %d.An error occurred updating the bindery services supervisor object. Error %d.An error has occurred. The class definition is greater that the maximum size allowed.Restore local server information after hardware failureUses the file SERVDATA.NDS to restore Directory information on this server.Restoring Directory ServicesThe backup file (%s) indicates this was the only server in the tree. This option is not available. Reinstall the server, restore the objects from a previous NDS object backup, and restore the file system from a previous backup.Restoring NDS from file %s An error occurred during the process of verifying the server object. Error %d.An error occurred while creating a new NDS. Error %d. Server verification Verifying server object from the backup file %s. Finished verifying the server object. Insufficient memory to add the attribute definition.Insufficient memory to define class.Could not gain access to Directory Services Either DS.NLM is not loaded or another NLM has already registered with DS. This could be one of DSMERGE.NLM, DSMAINT.NLM, DSI.NLM, OR DSREPAIR.NLM. An error occurred during the attempt to display an error message. Error %d. Press to continue.Beginning check to determine if this is the only server in the tree.An error occurred determinig if this is the only server in the tree. Error %d. Completed check to determine if this is the only server in the tree. Backing up server-specific NDS dataAn error occurred accessing the backup file. Error %d. An error occurred writing the backup file. Error %d. An error occurred while getting the local server's time information. Error %d. The NDS agent is not open. Please try this operation again at a later time. An error occurred while writing this server's partition information. Error %d. An error occurred while writing this server's entry id information. Error %d. An error occurred while writing this server's suervisor object information. Error %d. An error occurred writing the server's local inforation to the file. Error %d.