77.0 Common Workstation Utilities Error Messages
The following error messages are common to most workstation utilities:
901: You are not attached to the specified server.
Source:
FLAG.EXE, PURGE.EXE, RIGHTS.EXE
Possible Cause:
The user tried to execute a command on a server other than the default server to which the user was not attached.
Action:
Specify a path to the utility on the appropriate server.
Action:
Attach to the desired server, and then map a drive to the server and use the new drive mapping in the command. Use the /NS option to attach; otherwise, you will lose the default option.
903: The command line syntax is invalid.
Source:
CX.EXE, FLAG.EXE, LOGOUT.EXE, MAP.EXE, PURGE.EXE, RIGHTS.EXE, SETPASS.EXE
Explanation:
The format of the command was incorrect.
Action:
Make sure the syntax, path, and optional parameters are correct. Use the online help screens to view the correct command line syntax.
905: This utility was unable to initialize the country information.
Source:
FLAG.EXE, LOGIN.EXE, LOGOUT.EXE, MAP.EXE, RIGHTS.EXE, SETPASS.EXE
Explanation:
This utility was unable to get the country information from the workstation.
Possible Cause:
The workstation’s operating system configuration is not correct.
Action:
Make sure that the workstation’s operating system configuration is correct.
906: The Unicode files cannot be found.
Source:
CAPTURE.EXE, CX.EXE
Explanation:
The Unicode files for the current language code page and country cannot be found.
Action:
Verify that the Unicode files for the current code page and country are located in the SYS:PUBLIC\NLS directory.
907: This utility cannot open the translation table SCHEMA.XLT.
Source:
source file in message
Explanation:
In the DOS, Windows, and OS/2 environments, the program searches the following areas for the translation files.
-
The current directory.
-
The load directory (the directory containing the current utility’s EXE file). This is usually the PUBLIC directory.
-
The NLS directory that is located within the load directory (the directory containing the current utility’s EXE file). If the Unicode files are not found in the NLS directory within the load file, the program searches the NLS directory that is a sibling of the load directory (that is, at the same level as the load directory). Note: The NWLanguage environment variable does not apply here.
-
The PATH and DPATH (for OS/2 only) environment variables. These environment variables can be found in the user’s login script or AUTOEXEC.BAT file.
Action:
Make sure these files are loaded into the PUBLIC directory and that the workstation has a search drive mapped to the PUBLIC directory; then try the operation again. If the problem persists, contact a Novell support provider.
908: The specified path is invalid.
Source:
FLAG.EXE, PURGE.EXE, RIGHTS.EXE
Explanation:
The operating system could not find the directory path.
Possible Cause:
The specified directory path does not exist, or the user mistyped the directory path.
Action:
Examine the directory. Type the directory path correctly.
909: You are not mapped to the specified drive.
Source:
FLAG.EXE, PURGE.EXE, RIGHTS.EXE
Possible Cause:
The user specified a local hard disk or a network drive that has not been defined.
Action:
View the workstation’s network drive mappings. If necessary, map a drive to the directory, and then try the command again.
910: This utility was unable to parse the specified path.
Source:
FLAG.EXE, RIGHTS.EXE
Explanation:
The program could not find the directory path.
Possible Cause:
The specified a directory path does not exist, or the user mistyped the directory path.
Action:
Examine the directory. Type the directory path correctly. The correct syntax is as follows:
SERVER\VOLUME:DIRECTORY\SUBDIRECTORY\FILES
or
DRIVE_LETTER:DIRECTORY\SUBDIRECTORY\FILES
911: Directory Services is not active at this time.
Source:
FLAG.EXE
Possible Cause:
The user made an Novell eDirectory request on a server that is not an eDirectory server.
Action:
Make sure that the workstation client supports eDirectory requests.
Possible Cause:
The user does not have a connection to an eDirectory server.
Action:
Make sure that eDirectory is active on the server to which the request is made.
912: The specified file cannot be found.
Source:
FLAG.EXE
Possible Cause:
The user specified an invalid filename.
Action:
Type the file name correctly.
Possible Cause:
The file is not part of the path.
Action:
Make sure that the file is part of the path.
913: The specified directory cannot be found.
Source:
FLAG.EXE, RIGHTS.EXE
Possible Cause:
The user specified an invalid directory name.
Action:
Type the directory name correctly.
Possible Cause:
The directory is not part of the path.
Action:
Make sure that the directory is part of the path
914: The specified file or directory cannot be found.
Source:
FLAG.EXE, RIGHTS.EXE
Possible Cause:
The user specified an invalid filename or directory name.
Action:
Type the filename or directory name correctly.
Possible Cause:
The file or directory is not part of the path.
Action:
Make sure that the file or directory is part of the path.
915: The specified volume does not exist.
Source:
FLAG.EXE, LOGIN.EXE, MAP.EXE
Possible Cause:
The volume in the specified path is not valid.
Action:
Make sure the volume is valid and mounted.
916: This utility only supports 25 levels of directories.
Source:
FLAG.EXE, PURGE.EXE, RIGHTS.EXE
Explanation:
This utility supports only 25 levels of directories.
Action:
Limit the network directories to 25 levels.
917: This utility was unable to set the context.
Source:
CAPTURE.EXE, CX.EXE, FLAG.EXE, RIGHTS.EXE
Possible Cause:
The user typed in the eDirectory object name incorrectly.
Action:
Make sure that you have typed the object name correctly.
Possible Cause:
The workstation does not have enough memory to set up the context.
918: This utility was unable to get connection information. Error code: code.
Source:
LOGIN.EXE, LOGOUT.EXE
Explanation:
For some unexpected reason, this utility was unable to obtain information about a particular server.
919: This utility could not create a connection list. Error code.
Source:
LOGIN.EXE, LOGOUT.EXE, MAP.EXE, SETPASS.EXE
Explanation:
The utility failed in its attempt to create a list of all the connections to which the workstation is currently attached.
Possible Cause:
The error code identifies a specific reason for the failure.
920: This utility was unable to allocate number bytes of memory.
Source:
CX.EXE, LOGIN.EXE, LOGOUT.EXE, MAP.EXE, SETPASS.EXE
Possible Cause:
During its processing, the utility attempted to allocate more memory. No additional memory was available, so the program was unable to allocate the specified number of bytes.
921: Either the supervisor has locked the bindery or volume SYS: is not mounted.
Source:
CAPTURE.EXE, LOGIN.EXE, MAP.EXE, SETPASS.EXE
Possible Cause:
The volume SYS: is not mounted.
Action:
Make sure that volume SYS: is mounted. (Type VOLUMES at the server console to determine whether the volume SYS: has been mounted.)
Possible Cause:
The supervisor has locked the bindery.
Action:
If volume SYS: is mounted, make sure that the bindery is not closed.
922: Intruder detection lockout has disabled this account.
Source:
CAPTURE.EXE, LOGIN.EXE, MAP.EXE, SETPASS.EXE
Explanation:
A user has tried to log in to the account without supplying the correct password within the allowed number of login attempts. The user cannot use the account until it is reopened by the network supervisor.
Possible Cause:
The network supervisor can limit any account on the server to a specific number of login attempts to protect the account from intrusion by unauthorized persons.
Action:
Contact the network supervisor to enable the account, or wait a specified period of time for the account to become enabled again (default: 15 minutes).
923: An unexpected error has occurred. Error code: code.
Source:
CAPTURE.EXE, LOGIN.EXE, MAP.EXE, SETPASS.EXE
Explanation:
An unexpected error occurred.
Action:
Try the operation again. If the error persists, contact a Novell support provider. For information on the specific error code, search the Error Codes online documentation.
924: All drives are in use.
Source:
LOGIN.EXE, MAP.EXE
Possible Cause:
Every drive from Z: down to the local drives is in use. This utility cannot map any more drives.
Action:
Delete a mapping to a drive not being currently used.
925: The server specified is a Personal NetWare server. You cannot attach to a Personal NetWare server with this utility. Use the Personal NetWare utilities to access this connection.
Source:
CAPTURE.EXE, LOGIN.EXE, MAP.EXE, PURGE.EXE, SETPASS.EXE
Explanation:
This utility is not compatible with a Personal NetWare server.
Action:
Use the corresponding Personal NetWare utility.
970: The attempt to open the Unicode table files failed.
Source:
CX.EXE, FLAG.EXE, LOGIN.EXE, LOGOUT.EXE, MAP.EXE, PURGE.EXE, RIGHTS.EXE, SETPASS.EXE
Explanation:
The Unicode table files could not be opened for an unknown reason.
Possible Cause:
The cause of the error is probably other than those listed in messages 971 through 975.
Action:
Try the following:
-
Close files you do not need to have open at the present time.
-
Free up memory on the workstation. See Section A.1, Resolving Workstation Memory Problems.
-
Make sure the user has rights to access the directory where the Unicode table are kept.
-
Make sure the directory where the Unicode files are kept is in the search path.
-
Make sure the Unicode files are the most current version and are not corrupted.
If after doing all the listed actions the problem still persists, contact a Novell support provider.
971: The workstation does not have enough memory to load the Unicode table files.
Source:
CX.EXE, FLAG.EXE, LOGIN.EXE, LOGOUT.EXE, MAP.EXE, PURGE.EXE, RIGHTS.EXE, SETPASS.EXE
Explanation:
During its processing, this utility needed more memory and attempted to allocate more. No more available memory is available.
972: Access to the Unicode table files was denied.
Source:
CX.EXE, FLAG.EXE, LOGIN.EXE, LOGOUT.EXE, MAP.EXE, PURGE.EXE, RIGHTS.EXE, SETPASS.EXE
Explanation:
The user does not have sufficient rights to open and read the Unicode files.
Action:
If appropriate, give the user the necessary rights.
973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number .
Source:
CX.EXE, FLAG.EXE, LOGIN.EXE, LOGOUT.EXE, MAP.EXE, PURGE.EXE, RIGHTS.EXE, SETPASS.EXE
Explanation:
The file extension shown in parentheses represents the country code the workstation is using, which is set in CONFIG.SYS. For example, *.001 is US English. The country code might be different from the one shown here.
In the DOS, Windows, and OS/2 environments, the program searches the following areas for the Unicode files:
-
The current directory (for DOS and OS/2 environments) or the Windows directory.
-
The load directory (the directory containing the current utility’s .EXE file). Normally this will be the PUBLIC directory.
-
The NLS directory that is located within the load directory (the directory containing the current utility’s .EXE file). If the Unicode files are not found in the NLS directory within the load directory, the program searches the NLS directory that is a sibling of the load directory (that is, at the same level as the load directory). Note: The NWLanguage environment variable does not apply here.
-
The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found either in the user’s login script or in the AUTOEXEC.BAT file.
The following four files must be in one of these locations of the user’s search drive, or this error message is displayed:
code_page_UNI.country_id
UNI_code_page.country_id
UNI_MON.country_id
UNI_COL.country_id
Action:
Make sure that these four files are loaded into the PUBLIC directory and that the user has a search drive mapped to PUBLIC; then try the operation again.
If you have a search drive mapped to PUBLIC and the files still cannot be found there or in any other locations listed, use the NPATH utility to determine the Unicode files required for the workstation and their location. If the problem persists, contact a Novell support provider.
974: The Unicode table files are corrupt.
Source:
CX.EXE, FLAG.EXE, LOGIN.EXE, LOGOUT.EXE, MAP.EXE, PURGE.EXE, RIGHTS.EXE, SETPASS.EXE
Possible Cause:
The Unicode files are not the correct version or they are corrupt.
Action:
Replace the Unicode files with a current, uncorrupted copy of the files.
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:
CX.EXE, FLAG.EXE, LOGIN.EXE, LOGOUT.EXE, MAP.EXE, PURGE.EXE, RIGHTS.EXE, SETPASS.EXE
Possible Cause:
This utility came up in eDirectory mode but failed to open the Unicode table files. Too many files are already open.
Action:
Close any files you do not need to have open or modify the CONFIG.SYS file to increment the number that Files is set to. For example, change files=20 to files=30.
991: An error occurred in function_name. Error code: code.
Source:
source file in error
Explanation:
An unexpected error has occurred.
Action:
For information about a specific error code, search the Error Codes online documentation. Retry the operation a couple of times. Also be sure no associated problems have occurred (such as the network going down, a connection being lost, or previous errors having occurred and been ignored). If the problem persists, contact a Novell support provider.
998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance.
Source:
CX.EXE, FLAG.EXE, LOGIN.EXE, LOGOUT.EXE, MAP.EXE, nver.exe, RIGHTS.EXE, SETPASS.EXE
Explanation:
When the utility tried to initialize the utility_name.MSG file, it was unable to find a correct version of the file within the existing search drives. A file was found, but it was an incorrect version. The following areas were searched:
-
The current directory.
-
The NWLANGUAGE environment variable directory. If the NWLANGUAGE variable is set, it should contain a directory name or names which specify a language (for example, ENGLISH or FRENCH). The files are searched for in a child directory of the NLS directory as specified by the NWLANGUAGE variable. The NLS directory in this instance is itself a child directory of the load directory. (The load directory contains the current utility’s .EXE file.)
-
The load directory (the directory containing the current utility’s .EXE file). This is normally the PUBLIC directory.
-
The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found in the user’s login script or in the AUTOEXEC.BAT file.
-
The directories found under the child NLS subdirectory of the load directory.
-
The directories found under the sibling NLS subdirectory of the load directory.
Action:
Find a current version of the message file and copy it to a directory that is mapped to an existing search drive, or map a search drive to the file.
999: The message file for this utility cannot be found.
Source:
CX.EXE, FLAG.EXE, LOGIN.EXE, LOGOUT.EXE, MAP.EXEMAP.EXE, RIGHTS.EXE, SETPASS.EXE
Explanation:
When the utility tried to initialize the utility_name.MSG file, it was unable to find the file within the existing search drives. The following areas were searched:
-
The current directory.
-
The NWLANGUAGE environment variable directory. If the NWLANGUAGE variable is set, it should contain a directory name or names which specify a language (for example, ENGLISH or FRENCH). The files are searched for in a child directory of the NLS directory as specified by the NWLANGUAGE variable. The NLS directory in this instance is itself a child directory of the load directory. (The load directory contains the current utility’s .EXE file.)
-
The load directory (the directory containing the current utility’s .EXE file). This is normally the PUBLIC directory.
-
The PATH and DPATH (for OS/2 only) environment variables. These environment variables may be found either in the user’s login script or in the AUTOEXEC.BAT file.
-
The directories found under the child NLS subdirectory of the load directory.
-
The directories found under the sibling NLS subdirectory of the load directory.
Action:
Find a current version of the message file. Then, copy it to a directory that is mapped to an existing search drive, or map a search drive to the directory containing the file.