33.0 LOGIN Messages
The following includes messages from LOGIN.NLM.
LOGIN-X-100: Access has been denied.
Source:
LOGIN.EXE
Explanation:
The user has no rights to log in to the network.
Possible Cause:
The username or password was typed incorrectly.
Action:
Log in again and type the username and password correctly.
Possible Cause:
The username entered does not have an account on the network.
Action:
Make sure that the workstation is logging in to a server or eDirectory™ tree on which the user is defined.
Possible Cause:
On multiserver networks using bindery mode, this message might mean that the user is not on the server to which the NetWare shell connected the workstation.
Action:
If the user is not attached to the server or network desired, specify the server or network in the LOGIN command.
Possible Cause:
The account balance is zero.
Action:
Increase the account balance.
LOGIN-X-105: You are trying to attach to your current tree (current tree name: tree name).
Source:
LOGIN.EXE
Explanation:
The user cannot reattach (INS) to the same tree.
Action:
None required, unless you want to attach to a different tree.
LOGIN-X-110: You are already in a tree and cannot attach to another tree (current tree: tree name).
Source:
LOGIN.EXE
Explanation:
You cannot use INS to attach to a second tree.
Action:
Log out and try again.
LOGIN-X-115: The selected tree (name) cannot be found. Error code: code.
Source:
LOGIN.EXE
Explanation:
LOGIN tried to log the user in to a Directory tree that is either down, is not responding, or does not exist.
Action:
Verify that the Directory tree name was entered correctly and that the network is up and running. For information about a specific error code, search the Error Codes online documentation.
LOGIN-X-130: Access has been denied and you have been logged out.
Source:
LOGIN.EXE
Explanation:
The user has no rights to log in to the network.
Possible Cause:
The username or password was typed incorrectly.
Action:
Log in again and type the username and password correctly.
Possible Cause:
The user does not have an account.
Action:
Log in to a server or eDirectory tree where the user is defined.
Possible Cause:
On multiserver networks using bindery mode, this message may mean that the user is not defined on the server that the NetWare® shell connected the workstation to.
Action:
If the workstation is not connected to the server or network desired, specify the server or network in the LOGIN command.
Possible Cause:
The account balance is zero.
Action:
Increase the account balance.
LOGIN-X-140: This account has expired or been disabled by the supervisor.
Source:
LOGIN.EXE
Possible Cause:
The account has expired. The network supervisor can limit a user’s account to a specific period, after which the account expires and is no longer accessible.
Possible Cause:
The account has been disabled. The network supervisor can disable a user’s account for any reason.
Possible Cause:
The user did not type a password correctly. The network supervisor can limit the number of consecutive failed attempts to log in to a user’s account.
Action:
Enable the user's account.
LOGIN-X-150: You could not be authenticated to server name. (code)
Source:
LOGIN.EXE
Explanation:
Authentication means that the workstation attaches and logs the user in to a server without prompting for the password. In this instance, LOGIN could not authenticate to the specified server.
Possible Cause:
The cause of this error is unknown.
Action:
Log out and try again. For information about a specific error code, search the Error Codes online documentation.If the problem persists, contact a Novell support provider.
LOGIN-X-180: The login script contains a misplaced control command.
Source:
LOGIN.EXE
Explanation:
The parser found a control command (such as ATTACH, MAP, or SET) that LOGIN did not know existed.
Possible Cause:
The control command was correctly parsed, but in an odd position in the line.
Action:
Use the correct syntax.
Possible Cause:
A programming error exists that prevented LOGIN from using all of the commands that the parser used. This is the more likely of the two scenarios.
Action:
If the error persist, contact a Novell support provider.
LOGIN-X-200: The MAP command cannot change local drives.
Source:
LOGIN.EXE
Explanation:
Local drives cannot be changed to or from search drives by using MAP.
Explanation:
A MAP CHANGE command was issued within the login script that referenced a local drive.
Action:
Do not try to change local drives using MAP.
LOGIN-X-210: This server is being used to read login scripts. You cannot log out.
Source:
LOGIN.EXE
Explanation:
LOGIN encountered a LOGOUT command in a login script. LOGIN makes sure you were trying to log out of the same server that it was using to read the login script. If that has happened, various errors could occur; for example, the workstation could hang, or output could be unintelligible.
Action:
Determine which login script was being read and the server on which it resides. Do not try to log out of that server.
LOGIN-X-215: An internal system error occurred during LOGIN’s attempt to canonicalize the context: (name).
Source:
LOGIN.EXE
Explanation:
LOGIN tried to expand the relative name to a full name.
Action:
Try again. If the problem persists, contact a Novell support provider.
LOGIN-X-220: Script file name cannot be included.
Source:
LOGIN.EXE
Explanation:
The login script had a include script file name entry, and LOGIN was unable to include it.
Possible Cause:
No script file exists.
Possible Cause:
The specified path or filename is wrong.
Action:
Make sure that the path and filename specified are correct.
LOGIN-X-240: This utility was unable to open script file name.
Source:
LOGIN.EXE
Explanation:
LOGIN tried to open the specified script file, but the script file was not found or it could not be opened.
Possible Cause:
The script file could not be located.
Action:
Make sure that the login script file is in the directory specified.
Possible Cause:
The user did not have the appropriate rights to access the directory or file.
Action:
Make sure the user has appropriate user access rights to the directory and the file.
LOGIN-X-241: This utility was unable to open profile script script name.
Source:
LOGIN.EXE
Explanation:
LOGIN tried to open the specified script file, but the file was not found or it could not be opened.
Possible Cause:
The script file could not be located.
Action:
Make sure that the login script file is in the directory specified.
Possible Cause:
The user did not have the appropriate rights to access the directory or file.
Action:
Make sure the user has appropriate user access rights to the directory and the file.
LOGIN-X-250: This utility was unable to set the default drive to drive letter.
Source:
LOGIN.EXE
Possible Cause:
An invalid drive was probably specified.
Action:
Validate the drive letter indicated in the login script by first mapping the letter to a valid drive and directory.
LOGIN-X-260: The maximum number of server attachments has been reached.
Source:
LOGIN.EXE
Explanation:
Each NetWare server can be configured in a variety of ways (for example, as a 1000-user, 250-user, or 10-user network). Each configuration allows a certain number of connections.
Action:
Try again after a user has logged out of the server.
LOGIN-X-280: This utility could not get your connection status.
Source:
LOGIN.EXE
Explanation:
LOGIN failed to verify whether the user was logged in.
Action:
Attach using MAP. If this fails, reboot and reestablish all current connections.
LOGIN-X-283: This utility could not get the preferred Directory Services name or connection ID.
Source:
LOGIN.EXE
Explanation:
LOGIN could not find the preferred Directory tree.
Action:
Verify that the preferred Directory tree or server specified in the NET.CFG file is correct.
LOGIN-X-285: A network drive could not be found.
Source:
LOGIN.EXE
Explanation:
LOGIN could not find the first available network drive. If the login attempt fails (for example, if you have entered an incorrect password or an invalid username), the drive mapping is placed on this drive. LOGIN exits if it can not find an available network drive as a fall-back drive.
Action:
Make sure the last drive in CONFIG.SYS is set to a drive other than the Z: drive.
LOGIN-X-287: This utility could not find the preferred server.
Source:
LOGIN.EXE
Explanation:
LOGIN could not find the preferred server as specified in the NET.CFG file.
Action:
Verify that the preferred server in the NET.CFG file is correct.
LOGIN-X-290: This utility was unable to log you out, so you cannot be reattached.
Source:
LOGIN.EXE
Explanation:
Before LOGIN can reattach the user to any server, it must first log the user out. LOGIN’s attempt to log out failed; therefore, it cannot reattach.
Possible Cause:
This error occurs only with the /NS option, which allows the user to remain logged in to other servers or eDirectory trees when the user is logging in to a new server or network.
Action:
Try logging out using the LOGOUT utility; then try to log in using the /NS option.
LOGIN-X-295: This utility could not create a context.
Source:
LOGIN.EXE
Explanation:
LOGIN unsuccessfully tried to allocate a context handle.
Possible Cause:
Memory at the workstation might be low.
Action:
The context for the user's name in the NET.CFG file is incorrect.
Action:
Make sure context for the user's name in the NET.CFG file is correct and try again.
LOGIN-X-310: The workstation date and time could not be set.
Source:
LOGIN.EXE
Explanation:
LOGIN could not synchronize the workstation’s date or time with the server or the eDirectory network’s date or time.
Possible Cause:
An internal memory error in the workstation occurred.
Action:
Save your work and reboot the workstation. If the error persists, turn off the workstation. Wait approximately 15 seconds, turn it on, and log in again.
LOGIN-X-320: An operator in the login script attempted to divide by zero.
Source:
LOGIN.EXE
Possible Cause:
The user did a division by zero in the login script through the DIVISION or MODULUS arithmetic operators.
Action:
Change the login script so that it does not do a division by zero.
LOGIN-X-340: IF statements are nested too deeply. The nesting limit is number levels.
Source:
LOGIN.EXE
Explanation:
The login script can have unlimited IF statements, but the login script is limited to number of nested IF statements indicated in the message.
Example of four levels of nested IF statements:
IF........
IF.........
IF.......
IF.....
......
ENDIF
ENDIF
ENDIF
ENDIF
Action:
Where possible, take the IF statements out of the nested format and placing them after the sequence of nested IF statements.
LOGIN-X-370: The specified search drive does not exist.
Source:
LOGIN.EXE
Explanation:
When the login script uses a SET COMSPEC= or COMSPEC= command and a network drive is specified, LOGIN ensures that the specified drive is a search drive and can be used for the COMSPEC command.
Action:
Before issuing the SET COMSPEC or COMSPEC command, do one of the following steps:
LOGIN-X-380: The line is too long.
Source:
LOGIN.EXE
Possible Cause:
A line in the login script exceeded the maximum limit of 254 bytes.
Action:
Shorten the line or split the command into two commands so that they have the same functionality but occur on two lines.
LOGIN-X-400: A network drive cannot be mapped to a drive that is designated as a local drive.
Source:
LOGIN.EXE
Possible Cause:
The user tried to map a local drive to volume or directory on the network.
Action:
Map the volume or directory from the network to a network drive.
LOGIN-X-410: The supervisor has disabled the login function for this server.
Source:
LOGIN.EXE
Explanation:
This account is locked.
Possible Cause:
The network supervisor can disable the login function temporarily to prevent users from logging in or attaching during system maintenance. Most likely, the network supervisor is doing maintenance work and has disabled the server.
Action:
This condition is usually temporary. Try to log in after the login function has been enabled. If using CAPTURE or NPRINT, attach to another server and use its printer. Make sure that the SYS: volume is mounted on the server. If the problem persists, contact a Novell support provider.
LOGIN-X-430: The following drive mapping operation could not be completed. Mapping. The error code was code.
Source:
LOGIN.EXE
Explanation:
The uesr tried to map a drive to a path that does not exist or cannot be found by LOGIN.
LOGIN-X-440: The operation was attempted on an invalid drive.
Source:
LOGIN.EXE
Possible Cause:
The user tried to manipulate an invalid drive using MAP. For example, if L: had not been previously mapped, entering MAP DEL L: would produce this error.
Action:
Make sure that the command is entered correctly in the login script.Make sure that the drive is mapped correctly.
LOGIN-X-450: This utility was unable to map drive. The limit of 16 search drives was exceeded.
Source:
LOGIN.EXE
Explanation:
The workstation is limited to 16 search drives.
Action:
Delete an unwanted search drive to make room for the drive to be added. To delete the drive, use the MAP DEL search_drive or MAP REM search_drive command.
LOGIN-X-460: The server that you attempted to map a drive to is not accessible. The map command was command.
Source:
LOGIN.EXE
Possible Cause:
The server is probably down. So, LOGIN could not attach to the server.
Action:
Verify that the network is up and running and logging in again.
LOGIN-X-470: The specified drive mapping is an invalid path: path.
Source:
LOGIN.EXE
Explanation:
LOGIN tried to map a drive to a path that does not exist.
Action:
Verify that the users are logged in to the server (if it is a bindery server) that they are trying to map to. Verify that the path exists and that it was typed correctly.
LOGIN-X-480: The MACHINE NAME command is not supported in DOS versions prior to DOS 3.1.
Source:
LOGIN.EXE
Explanation:
When using the MACHINE NAME = command in the login script, the workstation must be running DOS 3.1 or later.
Action:
Upgrade to DOS 3.1 or a later version, or do not use the specified command.
LOGIN-X-500: You do not have an account balance.
Source:
LOGIN.EXE
Possible Cause:
The user does not have an account on this server or in eDirectory.
Action:
Obtain an account or reestablish a previous account.
LOGIN-X-520: Your credit limit has been exceeded.
Source:
LOGIN.EXE
Possible Cause:
LOGIN denied access because the user has no more credit on the server or in eDirectory.
Action:
If appropriate give the user more credit.
LOGIN-X-530: The line contains no end quote.
Source:
LOGIN.EXE
Possible Cause:
A line in the login script does not contain an end quote. For example, WRITE Hello World! is missing the second double quote mark.
Action:
Put the end quote in the login script at the end of the specified line.
LOGIN-X-550: The maximum number of connections allowed on this server has been reached. Wait until another user logs out.
Source:
LOGIN.EXE
Possible Cause:
The user is trying to log in to or attach to a server via the login script, but too many users are already logged in to the server. The servers come with 5, 10, 1000, or other programmed number of user versions.
Action:
Wait until a user logs out (thus freeing a connection that will allow the user to log in), or, if this is a recurring problem, upgrade to a server with a greater number of user connections.
LOGIN-X-560: This utility could not find the label label.
Source:
LOGIN.EXE
Explanation:
The label used in the GOTO command was not found.
Possible Cause:
A common cause of this problem is shown in the following example:
IF FILE_SERVER = 911 THEN GOTO need_help
........
need_hep:
.......
.......
ENDIF
Note that need_help and the label need_hep are spelled differently; therefore, LOGIN cannot find the label specified by the GOTO command. Also, if the colon is left off the label name, LOGIN will not know that it is a label and will not find it.
Action:
Edit the login script. Make sure that the label is spelled correctly and that a colon follows the label name.
LOGIN-X-580: Your password has expired and all grace logins have been used.
Source:
LOGIN.EXE
Possible Cause:
The account is locked because the user did not change an expired password. The network supervisor can limit the number of times a user can log in with an expired password.
Action:
If desired, unlock the user’s account.
LOGIN-X-600: This utility could not interpret the line.
Source:
LOGIN.EXE
Explanation:
LOGIN could not parse the line indicated in the login script.
Action:
Verify that the line has been typed correctly and has the proper syntax.
LOGIN-X-610: The file server does not respond.
Source:
LOGIN.EXE
Explanation:
The workstation or user tried to attach to the server, but the server did not respond.
Possible Cause:
The server lost power or was shut off before the DOWN command was issued.
Explanation:
When a server is brought down, the DOWN command sends a message to all other servers informing them that the server is no longer active. However, if a server is shut off before the DOWN command is issued, all other servers assume that the server is still active. In this situation, the server name still appears when the NLIST command is invoked, even though the server is no longer active. The server can be seen with NLIST up to 15 minutes after it has lost its power or halts abnormally. This error message appears if the user tries to log in to or issue a command on the server in question.
Action:
Try the command again when the server has been brought back up.
Possible Cause:
A broken or loose connection exists on the internetwork between the server and the server the user tried to attach to.
Action:
Make sure the server is connected to the network and try to log in again.
LOGIN-X-630: The NetWare shell is not loaded.
Source:
LOGIN.EXE
Possible Cause:
The user tried to log in to a server without loading the NetWare NETX or VLM™ bindery shell into the workstation's memory. When the workstation is booted, DOS is loaded into the workstation’s memory. The NetWare shell is then loaded on top of DOS. The shell allows the workstation to communicate with the server. A user cannot log in to any server on the network unless the NetWare shell has been loaded into the workstation's memory.
Action:
Give the user a boot diskette that contains both DOS and the NetWare shell files. Then ask the user to try rebooting the workstation and logging in again. If the error persists, the boot diskette may be corrupted.
LOGIN-X-640: Server name is part of domain name. This version of LOGIN is not a NetWare Name Service utility and cannot synchronize passwords in a domain. Use the NetWare Name Service utility SETPASS to change your password.
Source:
LOGIN.EXE
Possible Cause:
LOGIN found that a server the user is attached to is a NetWare Name Service server. This LOGIN version cannot handle NetWare Name Service’s synchronization of passwords.
Action:
Use a NetWare Name Service (NNS) version of SETPASS to synchronize passwords.
LOGIN-X-650: The COMSPEC variable is not supported on this platform.
Source:
LOGIN.EXE
Possible Cause:
The login script contains a COMSPEC variable.
Action:
Do not use the COMSPEC command in the login script when using this platform.
LOGIN-X-660: The DOS BREAK command is not supported on this platform.
Source:
LOGIN.EXE
Possible Cause:
The login script contains a BREAK variable. BREAK is not supported on this platform, only in DOS.
Action:
Do not use the BREAK command in the login script when using this platform.
LOGIN-X-665: The EXIT command followed by a string is not supported on this machine.
Source:
LOGIN.EXE
Possible Cause:
The EXIT command was followed by a text string in the user’s login script.
Action:
Remove the text string that follows the EXIT command in the user’s login script.
LOGIN-X-670: The variable MACHINE NAME is not supported on this platform.
Source:
LOGIN.EXE
Explanation:
The login script contains a MACHINE_NAME variable. MACHINE_NAME is not supported on this platform, only in DOS.
Action:
Do not use the MACHINE_NAME command in the login script when using this platform.
LOGIN-X-680: This platform does not support search drives.
Source:
LOGIN.EXE
Explanation:
The login script contains search drive mappings.
Action:
Do not specify search drive mappings in the login script when using this platform.
LOGIN-X-690: Insufficient memory is available to add the variable to the path environment in mapping: [mapping]
Source:
LOGIN.EXE
Explanation:
There is not enough room in the master environment.
Action:
Increase the size of the master environment. In the CONFIG.SYS file, include the command SHELL=directory of command.com /e:size of master environment. For example:
SHELL=C:\COMMAND.COM /E:1024
LOGIN-X-700: The specified path is invalid.
Source:
LOGIN.EXE
Explanation:
When using the DISPLAY or FDISPLAY command in the login script, the specified file or path was invalid.
Action:
Make sure that the path name is a path. If necessary, correct the path in the login script.
LOGIN-X-710: The password could not be changed. Error code.
Source:
LOGIN.EXE
Explanation:
LOGIN was unable to change the password.
LOGIN-X-720: This utility could not add variable to the local environment variables.
Source:
LOGIN.EXE
Explanation:
This error occurs when you try to map a search drive. LOGIN was unable to add the variable to the local path environment variable. LOGIN will try to update the master environment and, upon successful completion, will try to update its local environment. This error is usually an indication of having too little memory to allocate the new variables.
Action:
Increase the memory available to the workstation. See Section A.1, Resolving Workstation Memory Problems. (Adding more than 640 KB will not correct this error because 640 KB is the maximum that can be used.)
This is not a serious error; however, you will not be able to access those search drives as search drives until login has been completed. These drives will still be mapped as regular drives. Because they were successfully placed in the master environment, they can become search drives after login has been completed.
LOGIN-X-725: The context you want to change to does not exist. You tried to change to: [name]. Your context will be left unchanged.
Source:
LOGIN.EXE
Action:
Verify the name of the context to which you want to change and try logging in again.
LOGIN-X-730: The context [name] is invalid. Your current context will be left unchanged.
Source:
LOGIN.EXE
Action:
Verify the name of the context to which you want to change and try logging in again.
LOGIN-X-740: This utility could not execute external program name.
Source:
LOGIN.EXE
Explanation:
The specified file is not executable or has an invalid executable-file format.
Action:
Execute an executable file. The files usually have the .EXE or .COM extension.
LOGIN-X-750: This utility could not execute external program name. You do not have enough memory space available.
Source:
LOGIN.EXE
Explanation:
For DOS to run a program, it must allocate enough memory to run that program. Programs that are very large will frequently have this problem.
Possible Cause:
The workstation does not have enough memory to execute the command.
LOGIN-X-760: This utility could not execute external program name. The program was not found.
Source:
LOGIN.EXE
Explanation:
LOGIN tried to execute a command using the #command syntax in the login script. However, the program was not found, and LOGIN could not execute the command. For example:
#EMAIL
should execute E-mail. If LOGIN cannot find the program, in the current directory or in the path, it will display this error message.
Action:
Make sure the workstation has a mapping to the directory where the program is located before you try to execute the program. Make sure that you have entered the full path name and the name of the program, as in the following example:
C:\APPS\MAIL\EMAIL
Be sure to copy the program to a location that has a current mapping.
LOGIN-X-770: This utility could not execute external program name. Either the environment is too big or the command line is too long.
Source:
LOGIN.EXE
Possible Cause:
The login script tried to execute a command using the #command. DOS allows only 128 characters on the command line. If the command is too long, it cannot be executed when using DOS, and LOGIN will warn you of this problem.
Action:
Limit the external command, or set the environment string length to 128.
Possible Cause:
The space required for the environment information was greater than 32 KB.
Action:
If possible, divide the command into two separate commands executed one after another.
LOGIN-X-780: This utility could not execute external program name. Error number occurred.
Source:
LOGIN.EXE
Explanation:
For an unknown reason, LOGIN could not execute the external program.
Action:
To get specifics on the error displayed and on the appropriate procedure, contact a Novell support provider.
LOGIN-X-790: The parser string table is full.
Source:
LOGIN.EXE
Possible Cause:
Internally, the parser used by LOGIN is storing strings. The parser string table holds a set number of strings. If the table becomes so full that it cannot hold any more strings, it will report this error.
Action:
Try using fewer commands on a single line in the login script.
LOGIN-X-800: The number of script parameters exceeds the program limit (number).
Source:
LOGIN.EXE
Explanation:
The user has exceeded the number of arguments that can be pass from the command line to the login script. The correct limit is displayed.
Action:
Pass fewer arguments to the login script.
LOGIN-X-810: An invalid string occurred in an EXIT command. The string contained more than number characters.
Source:
LOGIN.EXE
Action:
When using the EXIT command to pass a command to COMMAND.COM, make sure the specified command does not exceed 14 characters.
LOGIN-X-830: You are trying to log in to too many stations simultaneously. The supervisor has limited the number of connections you may have.
Source:
LOGIN.EXE
Possible Cause:
The user is already logged in with the maximum number of workstations allowed.
Action:
Log out of one workstation before logging in from another workstation.
Possible Cause:
The user account is currently being used by the maximum number of users allowed.
Action:
Wait for another user to log out from this account before logging in.
LOGIN-X-840: This utility is unable to set the context to name.
Source:
LOGIN.EXE
Explanation:
LOGIN was unable to set the context to the context specified.
Action:
Try again. If the problem persists, contact a Novell support provider.
LOGIN-X-850: You are trying to log in from an unauthorized station. The supervisor has limited the stations you may log in from.
Source:
LOGIN.EXE
Possible Cause:
The account was accessed from an unauthorized workstation. A network supervisor restricted the account to specific workstation workstations.
Action:
Access the account only from authorized workstations.
LOGIN-X-860: You are trying to log in during an unauthorized time period. The supervisor has limited the times that you may log in.
Source:
LOGIN.EXE
Possible Cause:
The network supervisor has set specific time periods when the user can use the server or eDirectory. The user cannot use the server until the next authorized time period.
Action:
Give the user a list of authorized time periods.
LOGIN-X-870: An unknown error was returned during LOGIN’s attempt to attach. (code)
Source:
LOGIN.EXE
Possible Cause:
An error has occurred that the operating system cannot identify; however, this error message usually indicates that the server or the eDirectory is servicing the maximum number of logged-in users it can accommodate with the amount of memory installed.
Action:
Ask some users to log out of the system temporarily. If the error persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.
LOGIN-X-880: An unknown, but correctly parsed, command was found in the login script.
Source:
LOGIN.EXE
Possible Cause:
A command in the login script was correctly parsed, but LOGIN could not recognize what command it was and could not execute it.
Action:
Make sure that the command has been entered correctly in the login script. A script error has probably occurred that was, somehow, parsed correctly.
LOGIN-X-881: This script command is not supported in this platform or configuration.
Source:
LOGIN.EXE
Possible Cause:
The command could not execute because it is not specific to the platformon which it is being executed. For example, the TREE command is valid only on a multi-tree capable client. It would not be valid on Windows NT*, OS/2*, or when using a Virtual Loadable Module™ (VLM™).
Action:
Remove the invalid platform-specific command from the login script.
LOGIN-X-890: The specified server is unknown.
Source:
LOGIN.EXE
Possible Cause:
The user mistyped the name of the server, specified a server that is not on the network, or specified a server that has been brought down for system maintenance.
Action:
Use NLIST or NETADMIN to list the servers that the station recognizes. Type the name of the server correctly. If the server has been brought down for maintenance, try the command after the server has been brought back up.
LOGIN-X-895: The user does not exist in the specified context.
Source:
LOGIN.EXE
Possible Cause:
The user specified in the command line does not exist.
Action:
Specify a valid username in the command line.
LOGIN-X-903: The command line syntax is invalid.
Source:
LOGIN.EXE
Possible Cause:
The LOGIN command type is not correct.
Action:
Type LOGIN /? for help.
LOGIN-X-905: This utility was unable to initialize the country information.
Source:
LOGIN.EXE
Possible Cause:
The shell or VLM failed to load.
Possible Cause:
Some of the memory is corrupted.
LOGIN-X-915: The specified volume does not exist.
Source:
LOGIN.EXE
LOGIN-X-918: This utility was unable to get connection information. Error code: code.
Source:
LOGIN.EXE
LOGIN-X-919: This utility could not create a connection list. Error code.
Source:
LOGIN.EXE
LOGIN-X-920: This utility does not have enough memory.
Source:
LOGIN.EXE
Explanation:
LOGIN does not have enough workstation conventional memory to execute.
LOGIN-X-921: Either the supervisor has locked the bindery or volume SYS: is not mounted.
Source:
LOGIN.EXE
LOGIN-X-922: Intruder detection lockout has disabled this account.
Source:
LOGIN.EXE
LOGIN-X-923: An unexpected error has occurred. Error code: code.
Source:
LOGIN.EXE
LOGIN-X-924: All drives are in use.
Source:
LOGIN.EXE
LOGIN-X-925: This function is not supported on Personal NetWare servers.
Source:
LOGIN.EXE
LOGIN-X-970: The attempt to open the Unicode table files failed.
Source:
LOGIN.EXE
LOGIN-X-971: The workstation does not have enough memory to load the Unicode table files.
Source:
LOGIN.EXE
LOGIN-X-972: Access to the Unicode table files was denied.
Source:
LOGIN.EXE
LOGIN-X-973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number
Source:
LOGIN.EXE
LOGIN-X-974: The Unicode table files are corrupt.
Source:
LOGIN.EXE
LOGIN-X-975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.
Source:
LOGIN.EXE
LOGIN-X-998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance.
Source:
LOGIN.EXE
LOGIN-X-999: The message file for this utility cannot be found.: Login.msg
Source:
LOGIN.EXE
LOGIN-X-2030: The password for user name on server name has expired.
Source:
LOGIN.EXE
Possible Cause:
The user's account is locked because the password has expired.
The network supervisor can require periodic password changes on accounts to prevent unauthorized access to the accounts. The network supervisor can also assign a grace period during which users can still use their expired passwords before having to choose new ones.
Action:
Use the SETPASS command to change the password. If the current password is used during the user’s grace period, it must be changed before the grace period ends. If the grace period expires and a new password has not been set, the network supervisor will have to change the user account password.
LOGIN-X-2032: The password for user name has expired.
Source:
LOGIN.EXE
Possible Cause:
The user’s account is locked because the password has expired.
The network supervisor can require periodic password changes on accounts to prevent unauthorized access to the accounts. The network supervisor can also assign a grace period during which users can still use their expired passwords before having to choose new ones.
Action:
Use the SETPASS command to change the password. If the current password is used during the user’s grace period, it must be changed before the grace period ends. If the grace period expires and a new password has not been set, the network supervisor will have to change the user account password.
LOGIN-X-2040: This is your last chance to change your password. You have no grace logins remaining.
Source:
LOGIN.EXE
Explanation:
This is the last chance the user has to change the password. If the password is not changed before the user logs out, the user will be denied access to the server or to the eDirectory tree on the next login attempt, and the network supervisor will have to change the account password.
Action:
Change the password using SETPASS or other utilities provided by the client software.
LOGIN-X-2050: The new password was retyped incorrectly.
Source:
LOGIN.EXE
Possible Cause:
When changing the password, the user was prompted to enter a new password and then retype it. The user did not type it exactly the same way the second time as it was typed the first time.
Action:
Have the user retype the password again.
LOGIN-X-2070: The new password has been used previously.
Source:
LOGIN.EXE
Explanation:
The network supervisor can restrict users from using previous passwords.
Action:
Have the user select a password that has not already been used with the account.
LOGIN-X-2080: New password is too short.
Source:
LOGIN.EXE
Possible Cause:
The user tried to define a password that is shorter than the minimum length set by the network supervisor.
Action:
Tell the user to use a longer password.