67.0 TEXTUTIL-utility_name
The messages listed in this section might be initiated by one or more text or print utilities. The specific utility name is shown in the prefix to the message when displayed on the screen.
-
10: The system could not load overlay file name_RUN.OVL.
-
15: The system error library file filename is missing.
-
16: The error portal cannot be created during program initialization.
-
17: The system could not create a new portal because the portal control block table is full.
-
18: The system could not allocate additional memory.
-
19: The system cannot create a portal with a height of number and a width of number because it is too large.
-
20: The system could not seek a specific position in file name.
-
21: An End_Of_File error was returned while attempting to read file name. The read request was for number bytes.
-
22: File name could not be read. The read request was for number bytes.
-
23: File name should have had number bytes read from it.
-
24: The system could not push a list onto the stack because the list stack is already full.
-
25: The system could not pop a list from the stack because the list stack is empty.
-
26: The system cannot display the utility header with the current date and time.
-
28: The system could not allocate number bytes of additional memory.
-
29: File name could not be opened.
-
30: File name could not be closed.
-
31: File name should have had number bytes written to it.
-
32: The system could not write to file name. The write request was for number bytes.
-
33: The first element of the list could not be obtained because the list is empty.
-
35: The current list cannot be restored with list buffer number number because the buffer number is invalid.
-
36: The current list cannot be saved because the list save buffer number number is invalid.
-
37: A section of memory that was previously allocated could not be freed.
-
38: The bindery is locked. Normally the bindery is only locked if the supervisor is backing up volume SYS:. No information can be obtained until the supervisor unlocks the bindery.
-
39: Server name does not respond.
-
40: Server name is not connected.
-
41: Your station is already attached to the maximum number of servers allowed. You must detach from at least one server before you can attach to server name.
-
42: Server name does not have any free connection slots. Another user must detach from it before you can attach to it.
-
43: You are already attached to server name.
-
65: The system could not write the information to bindery object name property name.
-
69: The portal information cannot be obtained because no portal is currently selected.
-
70: File name could not be created.
-
72: Either the string passed to EditPortalString was longer than the maximum length allowed, or the string was not properly initialized.
-
76: The system could not change the file attributes of file name. The mode was number.
-
79: The procedure EditText failed because the default text was longer than the maximum length allowed.
-
82: The paste buffer is empty.
-
83: The text buffer is full.
-
85: The marked block is too big for the available memory.
-
88: Dynamic message number number could not be set because no dynamic message pointer for that number exists.
-
90: The name of the server at connection slot number could not be obtained.
-
91: The system could not locate the Help Librarian data file name and will not be able to provide help for this utility.
-
92: The system could not read the Help Librarian data file name and will not be able to provide help for this utility.
-
93: The system is using an invalid version of the Help Librarian data file name and will not be able to provide help for this utility.
-
95: The text is too long to fit in the current portal.
-
96: No portal is currently selected to display the text.
-
108: No server is attached.
-
109: A read error occurred during attempt to read the overlay file name_RUN.OVL.
-
110: The overlay file name_RUN.OVL is the wrong version for this utility.
-
114: The system called GetError, but the specified procedure has been deleted.
-
180: The system called GetListIndex with element name, but that element is not found in the currently selected list.
-
181: AlignChangedList was called with the element name, but that element was not found in the currently selected list.
-
182: AlignListDisplay was called with the element name, but that element was not found in the currently selected list.
-
183: File name could not be found.
-
187: The system called PushHelpContext to push context number number onto the stack, but the help context stack is already full.
-
188: You cannot return to a previous Help context at this point because no previous Help context is left on the stack.
-
189: The Help context could not be set to number number, because only number Help contexts are defined. Help context numbers are zero-based.
-
197: Connection information could not be obtained about connection number number.
-
198: The palette stack is full.
-
199: The palette stack is empty.
-
202: The message queue is full.
-
203: There is either a lack of dynamic workspace or an I/O failure.
-
205: Directory name cannot be deleted because the directory is currently being used by another station.
-
207: The object password could not be changed.
-
209: A temporary drive handle could not be created.
-
210: The drive handle could not be deallocated.
-
211: File name could not be deleted because the file is either in use or queued to be printed.
-
212: The specified drive is invalid.
-
213: The specified directory cannot be found.
-
214: Server name cannot be found.
-
217: Information about the preferred server could not be obtained.
-
218: The system could not get the directory trustee paths and the access level of object ID value on volume number.
-
219: The specified drive handle is invalid.
-
221: The specified server name is not attached.
-
222: File name cannot be found.
-
223: You do not have rights to change the mode of file name.
-
224: You do not have rights to create the directory name.
-
225: Directory name already exists.
-
228: The system encountered invalid parameters.
-
229: The specified path is not locatable.
-
230: The specified drive in path path is not a local drive.
-
231: The target and the path are separate local drives.
-
233: The specified volume cannot be found.
-
234: The DOS environment could not be found.
-
235: Environment variable variable could not be found in the DOS environment.
-
236: No error was returned from this function call.
-
237: Connection number number is invalid.
-
238: The new environment is larger than the maximum size available. The new variable is string.
-
239: Specified server in path path cannot be found.
-
240: The specified server in path path is not attached.
-
242: Object ID value could not be found in the server bindery.
-
243: The name of object ID value could not be obtained.
-
244: The new property could not be added to bindery object name. The new property was name.
-
245: Additional memory cannot be allocated for the extra element name in the current list.
-
248: Additional memory cannot be allocated for an extra field in the current form.
-
249: Trustee ID value could not be added to the specified directory.
-
250: Trustee ID value could not be deleted from the specified directory.
-
251: The specified directory could not be scanned for its trustees.
-
253: An error occurred while file name was being copied to file name. Number bytes of the requested number bytes were copied.
-
256: File name could not be renamed to name because the specified path does not exist.
-
257: File name could not be renamed to name because a file with the same name already exists.
-
258: File name could not be renamed to name because the file is currently being used.
-
259: File name could not be renamed to name because the directory handle was invalid.
-
260: File name could not be renamed to name because the new file name is illegal.
-
261: File name could not be renamed to name because this station has no file rename privileges in the specified directory.
-
262: File name could not be renamed to name because the server is out of dynamic workspace.
-
272: The specified path does not exist.
-
321: The system could not unlink file name because the file was not found.
-
322: The system could not unlink file name because the specified path was not found.
-
323: The system could not unlink file name because access was denied.
-
334: File name could not be closed because the specified file handle is invalid.
-
337: File name could not be created because the specified directory could not be found.
-
338: File name could not be created because too many files are open.
-
339: File name could not be created because access was denied.
-
340: File name could not be opened because the specified files could not be found.
-
341: File name could not be opened because the specified directory could not be found.
-
342: File name could not be opened because too many files are already open.
-
343: File name could not be opened because access was denied.
-
344: File name could not be opened because the specified access code is invalid.
-
345: File name could not be read because access was denied. The read request was for number bytes.
-
346: File name could not be read because the specified file handle was invalid. The read request was for number bytes.
-
347: Directory name could not be created because the specified path was not found.
-
348: Directory name could not be created because access was denied.
-
349: The system could not write to file name because access was denied. The write request was for number bytes.
-
350: The system could not write to file name because the specified file handle was invalid. The write request was for number bytes.
-
354: The combined width of the program header and the version number is greater than 34. This means that the header will be overwritten by the date and time for certain days in certain months. Shorten the header message.
-
385: The new bindery object name could not be created. The maximum number of bindery objects specified during installation has been reached. You must increase the number of bindery objects available on this server.
-
415: File pattern path_string cannot be erased because some of the files in the directory are currently being used by another station.
-
416: The server does not have enough memory to complete the request.
-
417: Either the file with the specified file handle could not be closed, or the bindery failed.
-
418: The file was successfully closed, but the queue job could not be started.
-
421: Error number occurred during attempt to get a directory path from a directory handle.
-
425: Create Queue was passed an invalid queue name (name).
-
533: The Unicode files cannot be found.
-
541: The specified volume does not exist.
-
555: The system could not get physical volume information for volume object name.
-
561: The system was not able to allocate a buffer for the current operation.
-
562: The system was not able to read the volume objects in the current context.
-
563: The system was not able to retrieve a count of volume objects in the current context.
-
564: The system was not able to read the name of a volume object in the current context.
-
565: The current context has not been set properly.
-
566: The system was not able to set the current context.
-
567: The system was not able to get a connection number to access volume object name.
-
568: The system was not able to get a connection ID for server name.
-
569: An invalid volume object string was entered.
-
572: The system could not reset the context after escaping from the Browse option.
-
574: The system could not create a portal in which to display the function key help line.
-
575: The system could not create a portal in which to display information area text.
-
576: An incorrect version of the system help file SYS$HELP.HEP was found. The correct version is version. System help will be disabled.
-
577: The message file found utility_name.MSG is an incorrect version. The correct version is version. See your network supervisor for assistance.
-
578: The help file found (name.HEP) is an incorrect version. The correct version is version. Program help will be disabled.
-
588: The system was unable to parse the specified path.
-
589: The system received an invalid path for the current server mode.
-
590: An error occurred while attempting to build a class list. It is likely that the workstation is out of memory.
-
591: The path must contain a full drive specification, including a :.
-
592: Directory_name is part of the current tree.
-
593: The system could not read the network address for directory_name.
10: The system could not load overlay file name_RUN.OVL.
Source:
utility name in message prefix prefix
Possible Cause:
This problem could mean the file is missing or not in the proper search path.
Action:
Make sure the directory where the .OVL file is located is in the search path.
Possible Cause:
The workstation does not have enough memory.
15: The system error library file filename is missing.
Source:
utility name in message prefix prefix
Possible Cause:
The file is missing or not in the proper search path.
Action:
Check the drive mappings to make sure the file is located in the correct search path.
16: The error portal cannot be created during program initialization.
Source:
utility name in message prefix
Possible Cause:
The workstation has insufficient memory.
Possible Cause:
An internal problem occurred in the program.
Action:
If the error persists, contact a Novell support provider.
17: The system could not create a new portal because the portal control block table is full.
Source:
utility name in message prefix
Possible Cause:
Too many screens are active at one time. This is a program logic error.
Action:
Contact a Novell support provider.
18: The system could not allocate additional memory.
Source:
utility name in message prefix
Possible Cause:
The workstation does not have sufficient memory to complete the attempted operation.
19: The system cannot create a portal with a height of number and a width of number because it is too large.
Source:
utility name in message prefix
Action:
Contact a Novell support provider.
20: The system could not seek a specific position in file name.
Source:
utility name in message prefix
Possible Cause:
The user does not have access rights to the file.
Action:
Make sure the file is flagged properly.
Possible Cause:
A file is corrupted.
Action:
If the user has a corrupted file, replace it, if possible.
Possible Cause:
A hardware failure occurred.
Action:
Find out if other users and workstations are experiencing the same problem. If so, contact a Novell support provider. If the problem persists and is isolated to this workstation, check the hardware and cabling.
21: An End_Of_File error was returned while attempting to read file name. The read request was for number bytes.
Source:
utility name in message prefix
Possible Cause:
The user does not have access rights to the file.
Action:
Make sure the file is flagged properly.
Possible Cause:
A file is corrupted.
Action:
If the user has a corrupted file, replace it, if possible.
Possible Cause:
A hardware failure occurred.
Action:
Find out if other users and workstations are experiencing the same problem. If so, contact a Novell support provider. If the problem persists and is isolated to this workstation, check the hardware and cabling.
22: File name could not be read. The read request was for number bytes.
Source:
utility name in message prefix
Possible Cause:
The user does not have access rights to the file.
Action:
Make sure the file is flagged properly.
Possible Cause:
A file is corrupted.
Action:
If the user has a corrupted file, replace it, if possible.
Possible Cause:
A hardware failure occurred.
Action:
Find out if other users and workstations are experiencing the same problem. If so, contact a Novell support provider. If the problem persists and is isolated to this workstation, check the hardware and cabling.
23: File name should have had number bytes read from it.
Source:
utility name in message prefix
Possible Cause:
The user does not have access rights to the file.
Action:
Make sure the file is flagged properly.
Possible Cause:
A file is corrupted.
Action:
If the user has a corrupted file, replace it, if possible.
Possible Cause:
A hardware failure occurred.
Action:
Find out if other users and workstations are experiencing the same problem. If so, contact a Novell support provider. If the problem persists and is isolated to this workstation, check the hardware and cabling.
24: The system could not push a list onto the stack because the list stack is already full.
Source:
utility name in message prefix
Possible Cause:
To initialize a new list, the old list must be pushed onto the stack. The program could not accommodate the request as described. Too many lists are active in the program at one time. This is a program logic error.
Action:
Contact a Novell support provider.
25: The system could not pop a list from the stack because the list stack is empty.
Source:
utility name in message prefix
Possible Cause:
The program attempted to retrieve a list when none was saved. This is a program logic error.
Action:
Contact a Novell support provider.
26: The system cannot display the utility header with the current date and time.
Source:
utility name in message prefix
Possible Cause:
The most likely cause of this error is a text string that is too long to display. This could result from messages expanding due to translation.
Action:
Contact a Novell support provider.
28: The system could not allocate number bytes of additional memory.
Source:
utility name in message prefix
Possible Cause:
The workstation does not have sufficient memory to complete the attempted operation.
29: File name could not be opened.
Source:
utility name in message prefix
Possible Cause:
The user does not have access rights to the file.
Action:
Make sure the file is flagged properly.
Possible Cause:
A file is corrupted.
Action:
If the user has a corrupted file, replace it, if possible.
Possible Cause:
A hardware failure occurred.
Action:
Find out if other users and workstations are experiencing the same problem. If so, contact a Novell support provider. If the problem persists and is isolated to this workstation, check the hardware and cabling.
30: File name could not be closed.
Source:
utility name in message prefix
Possible Cause:
The user does not have access rights to the file.
Action:
Make sure the file is flagged properly.
Possible Cause:
A file is corrupted.
Action:
If the user has a corrupted file, replace it, if possible.
Possible Cause:
A hardware failure occurred.
Action:
Find out if other users and workstations are experiencing the same problem. If so, contact a Novell support provider. If the problem persists and is isolated to this workstation, check the hardware and cabling.
31: File name should have had number bytes written to it.
Source:
utility name in message prefix
Possible Cause:
The user does not have access rights to the file.
Action:
Make sure the file is flagged properly.
Possible Cause:
A file is corrupted.
Action:
If the user has a corrupted file, replace it, if possible.
Possible Cause:
A hardware failure occurred.
Action:
Find out if other users and workstations are experiencing the same problem. If so, contact a Novell support provider. If the problem persists and is isolated to this workstation, check the hardware and cabling.
32: The system could not write to file name. The write request was for number bytes.
Source:
utility name in message prefix
Possible Cause:
The user does not have access rights to the file.
Action:
Make sure the file is flagged properly.
Possible Cause:
A file is corrupted.
Action:
If the user has a corrupted file, replace it, if possible.
Possible Cause:
A hardware failure occurred.
Action:
Find out if other users and workstations are experiencing the same problem. If so, contact a Novell support provider. If the problem persists and is isolated to this workstation, check the hardware and cabling.
33: The first element of the list could not be obtained because the list is empty.
Source:
utility name in message prefix
Possible Cause:
The program expected an active list and there was none. This is a program logic error.
Action:
Contact a Novell support provider.
35: The current list cannot be restored with list buffer number number because the buffer number is invalid.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
36: The current list cannot be saved because the list save buffer number number is invalid.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
37: A section of memory that was previously allocated could not be freed.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
38: The bindery is locked. Normally the bindery is only locked if the supervisor is backing up volume SYS:. No information can be obtained until the supervisor unlocks the bindery.
Source:
utility name in message prefix
Explanation:
This is a temporary inconvenience.
Action:
Wait a few minutes and try again.
39: Server name does not respond.
Source:
utility name in message prefix
Possible Cause:
The user is not attached to the server.
Action:
Make sure the user is attached to the server, and try again.
Possible Cause:
The server is down or malfunctioning.
Action:
Make sure the server is running and functioning properly.
40: Server name is not connected.
Source:
utility name in message prefix
Possible Cause:
The most likely cause is that the workstation is not attached to this server. This could be a cabling problem.
Action:
Check the cabling, or make sure the workstation is attached to the server, and try again.
41: Your station is already attached to the maximum number of servers allowed. You must detach from at least one server before you can attach to server name.
Source:
utility name in message prefix
Possible Cause:
The user has tried to attach to more servers than the user is allowed to.
Action:
Detach from at least one server before attempting to attach to the new server.
42: Server name does not have any free connection slots. Another user must detach from it before you can attach to it.
Source:
utility name in message prefix
Explanation:
The server indicated in the message does not have any free connection slots.
Action:
Make sure another user detaches from the server before this user attempts to attach to it.
43: You are already attached to server name.
Source:
utility name in message prefix
Explanation:
This is a status message indicating that user tried to attach to a server the user is already attached to.
65: The system could not write the information to bindery object name property name.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
69: The portal information cannot be obtained because no portal is currently selected.
Source:
utility name in message prefix
Possible Cause:
The program expected an active portal when there was none. This is a program logic error.
Action:
Contact a Novell support provider.
70: File name could not be created.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
72: Either the string passed to EditPortalString was longer than the maximum length allowed, or the string was not properly initialized.
Source:
utility name in message prefix
Possible Cause:
This is probably an internal program logic error, though it could be caused by message expansion during translation.
Action:
Contact a Novell support provider.
76: The system could not change the file attributes of file name. The mode was number.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
79: The procedure EditText failed because the default text was longer than the maximum length allowed.
Source:
utility name in message prefix
Possible Cause:
This is probably an internal program logic error, though it could be caused by message expansion during translation.
Action:
Contact a Novell support provider.
82: The paste buffer is empty.
Source:
utility name in message prefix
Explanation:
This is a status message indicating that user tried to retrieve a data block from the paste buffer, but nothing was in the buffer.
83: The text buffer is full.
Source:
utility name in message prefix
Possible Cause:
The text block the user marked is too large to hold in the text buffer.
Action:
Mark and process several smaller text blocks instead of trying to process a single large block.
85: The marked block is too big for the available memory.
Source:
utility name in message prefix
Possible Cause:
The text block the user marked is too large to hold in the workstation’s memory.
Action:
Mark and process several smaller text blocks instead of trying to process a single large block.
88: Dynamic message number number could not be set because no dynamic message pointer for that number exists.
Source:
utility name in message prefix
Possible Cause:
A bad parameter was passed to the call. This is an internal program logic error.
Action:
Contact a Novell support provider.
90: The name of the server at connection slot number could not be obtained.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
91: The system could not locate the Help Librarian data file name and will not be able to provide help for this utility.
Source:
utility name in message prefix
Possible Cause:
The version of the Help file is outdated or corrupted, the search drive is incorrect, or the workstation has connection problem.
Action:
If the file is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact a Novell support provider.
92: The system could not read the Help Librarian data file name and will not be able to provide help for this utility.
Source:
utility name in message prefix
Possible Cause:
The version of the Help file is outdated or corrupt, the search drive is incorrect, or the workstation has a connection problem.
Action:
If the file is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact a Novell support provider.
93: The system is using an invalid version of the Help Librarian data file name and will not be able to provide help for this utility.
Source:
utility name in message prefix
Possible Cause:
An outdated version of the Help file is in the search path.
Action:
Replace the outdated file with a current version.
95: The text is too long to fit in the current portal.
Source:
utility name in message prefix
Possible Cause:
This is probably an internal program logic error, though it could be caused by message expansion from translation.
Action:
Contact a Novell support provider.
96: No portal is currently selected to display the text.
Source:
utility name in message prefix
Possible Cause:
The program expected an active portal when there was none. This is a program logic error.
Action:
Contact a Novell support provider.
108: No server is attached.
Source:
utility name in message prefix
Possible Cause:
The user tried to execute a command on a server other than the default server, but was not attached to that server. The user must be attached to a server before he or she can use it.
Action:
Do one or both of the following:
-
Use the WHOAMI utility to list the servers to which the user is logged in or attached; then specify one of these servers when the user executes the utility. To see server attachments, use the /B option (syntax: SERVER /B).
-
Use the LOGIN utility to attach to the desired server; then map a drive to the server and use the new drive mapping in the command. Be sure to use the /NS option to attach; otherwise, the user will lose the default option.
109: A read error occurred during attempt to read the overlay file name_RUN.OVL.
Source:
utility name in message prefix
Possible Cause:
The user is using an outdated or corrupted version of the overlay file, the search drive is incorrect, or the workstation has a connection problem.
Action:
If the file is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact a Novell support provider.
110: The overlay file name_RUN.OVL is the wrong version for this utility.
Source:
utility name in message prefix
Possible Cause:
An outdated version of the Help file is in the search path.
Action:
Replace the outdated file with a current version.
114: The system called GetError, but the specified procedure has been deleted.
Source:
utility name in message prefix
Possible Cause:
The most likely cause of this problem is an outdated or corrupted version of the error file TEXUTIL.IDX.
Action:
Get a new version of the error file.
Possible Cause:
Another possibility is hardware problems.
Action:
If the problem persists, check the hardware and cabling. If the problem persists, contact a Novell support provider.
180: The system called GetListIndex with element name, but that element is not found in the currently selected list.
Source:
utility name in message prefix
Possible Cause:
The list processing functions are out of sync. This error is usually caused by a program logic problem.
Action:
Contact a Novell support provider.
181: AlignChangedList was called with the element name, but that element was not found in the currently selected list.
Source:
utility name in message prefix
Possible Cause:
The list processing functions are out of sync. This error is usually caused by an internal program logic error.
Action:
Contact a Novell support provider.
182: AlignListDisplay was called with the element name, but that element was not found in the currently selected list.
Source:
utility name in message prefix
Possible Cause:
The list processing functions are out of sync. This error is usually caused by an internal program logic error.
Action:
Contact a Novell support provider.
183: File name could not be found.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid filename, or an internal system error occurred.
Action:
Try again using a valid filename. If the problem persists, contact a Novell support provider.
187: The system called PushHelpContext to push context number number onto the stack, but the help context stack is already full.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
188: You cannot return to a previous Help context at this point because no previous Help context is left on the stack.
Source:
utility name in message prefix
Possible Cause:
The user was already at the front of the Help context stack. An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
189: The Help context could not be set to number number, because only number Help contexts are defined. Help context numbers are zero-based.
Source:
utility name in message prefix
Possible Cause:
The program passed an invalid number to the PushHelpContext() or SetHelpContext() function. This problem is usually caused by an internal program logic error. However, it could be caused by an outdated or corrupted Help file.
Action:
Make sure the version of the Help file is correct. If it is, contact a Novell support provider.
197: Connection information could not be obtained about connection number number.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
198: The palette stack is full.
Source:
utility name in message prefix
Possible Cause:
Too many calls were made to the PushPalette() function without making any calls to PopPalette(). This error is usually an internal program logic error.
Action:
Contact a Novell support provider.
199: The palette stack is empty.
Source:
utility name in message prefix
Possible Cause:
A call was made to the PopPalette() function without a corresponding call to PushPalette(). This error is usually an internal program logic error.
Action:
Contact a Novell support provider.
202: The message queue is full.
Source:
utility name in message prefix
Explanation:
This is a status message indicating that the message queue is full.
203: There is either a lack of dynamic workspace or an I/O failure.
Source:
utility name in message prefix
Possible Cause:
The workstation needs more memory.
Possible Cause:
An internal system error has occurred.
Action:
Continue if possible. If not, restart the workstation. If the problem persists, contact a Novell support provider.
205: Directory name cannot be deleted because the directory is currently being used by another station.
Source:
utility name in message prefix
Possible Cause:
The user cannot delete this directory while another workstation is using it.
Action:
Wait until the directory is free; then try again. You might want to check to make sure you should delete the directory.
207: The object password could not be changed.
Source:
utility name in message prefix
Possible Cause:
An internal system error occurred.
Action:
Continue if possible. If not, restart the workstation. If the problem persists, contact a Novell support provider.
209: A temporary drive handle could not be created.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred. Another possibility is that the workstation does not have enough memory available to complete the operation.
210: The drive handle could not be deallocated.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
211: File name could not be deleted because the file is either in use or queued to be printed.
Source:
utility name in message prefix
Possible Cause:
The user cannot delete a file when it is in use or in a print queue.
Action:
Wait until the file is no longer being used; then try again.
212: The specified drive is invalid.
Source:
utility name in message prefix
Possible Cause:
The specified drive is invalid.
Action:
Make sure that the user specifies a valid drive.
213: The specified directory cannot be found.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid directory name.
Action:
Make sure the directory name is valid. Then try again.
Possible Cause:
An internal system error has occurred.
Action:
If the problem persists, contact a Novell support provider.
214: Server name cannot be found.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid server name.
Action:
Make sure the name specified is valid, then try again.
Possible Cause:
The server is down or offline.
Action:
Make sure that the user is connected to the server and the server is operating properly.
Possible Cause:
An internal system error has occurred.
Action:
If the problem persists, contact a Novell support provider.
217: Information about the preferred server could not be obtained.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
218: The system could not get the directory trustee paths and the access level of object ID value on volume number.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
219: The specified drive handle is invalid.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
221: The specified server name is not attached.
Source:
utility name in message prefix
Possible Cause:
The user has specified a server that cannot be found. The user is not attached to the server, the server is offline, or the user typed the server name incorrectly.
Action:
Make sure the server is attached to the network and that the server is operating properly; then try again, using the correct server name.
222: File name cannot be found.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
223: You do not have rights to change the mode of file name.
Source:
utility name in message prefix
Explanation:
NetWare’s rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.
Action:
Obtain the necessary rights to complete this task.
224: You do not have rights to create the directory name.
Source:
utility name in message prefix
Explanation:
NetWare’s rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.
Action:
Obtain the necessary rights to complete this task.
225: Directory name already exists.
Source:
utility name in message prefix
Possible Cause:
The user attempted to give a directory a name already assigned to another directory.
Action:
Choose a different name for the directory.
228: The system encountered invalid parameters.
Source:
utility name in message prefix
Possible Cause:
The utility could not set up a new drive path because invalid parameters were specified. The utility will attempt to continue.
Action:
If the user cannot continue, restart the workstation. If the problem persists, contact a Novell support provider.
229: The specified path is not locatable.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid path, or an internal system error occurred.
Action:
Make sure the path is valid. If the user cannot continue, restart the workstation.
230: The specified drive in path path is not a local drive.
Source:
utility name in message prefix
Explanation:
The drive assigned to this path must be a local (non-network) drive.
Action:
Try again, using a local drive.
231: The target and the path are separate local drives.
Source:
utility name in message prefix
Possible Cause:
The specified target is on a different local drive from the path specified.
Action:
Make sure the target and source path are on the same local drive.
233: The specified volume cannot be found.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid path.
Action:
Make sure the volume exists and is on the path the user specified. If so, restart the workstation.
Possible Cause:
An internal system error occurred.
Action:
If the problem persists, contact a Novell support provider.
234: The DOS environment could not be found.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
235: Environment variable variable could not be found in the DOS environment.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
236: No error was returned from this function call.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred. This message often is associated with a call to get volume information when a volume number is given.
Action:
If necessary, restart the workstation. If the problem persists, contact a Novell support provider.
237: Connection number number is invalid.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid connection number.
Action:
Give the user a list of valid connection numbers.
238: The new environment is larger than the maximum size available. The new variable is string.
Source:
utility name in message prefix
Explanation:
This is a status message indicating that the user specified an environment size that was too large. The program has assigned a size within the acceptable range.
239: Specified server in path path cannot be found.
Source:
utility name in message prefix
Possible Cause:
The user typed the path or server name incorrectly.
Action:
Try again, making sure the path and server name are correct.
240: The specified server in path path is not attached.
Source:
utility name in message prefix
Possible Cause:
The user is not attached to the specified server, or the server is offline, or the server is not functioning properly.
Action:
Attach to the server. Check the hardware and cabling.
242: Object ID value could not be found in the server bindery.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid object ID, or an internal error occurred.
Action:
Try again, making sure to use a valid ID.
243: The name of object ID value could not be obtained.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
244: The new property could not be added to bindery object name. The new property was name.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
245: Additional memory cannot be allocated for the extra element name in the current list.
Source:
utility name in message prefix
Possible Cause:
The workstation does not have sufficient memory to add additional objects to the list.
248: Additional memory cannot be allocated for an extra field in the current form.
Source:
utility name in message prefix
Possible Cause:
The workstation does not have enough memory to complete this operation.
249: Trustee ID value could not be added to the specified directory.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
250: Trustee ID value could not be deleted from the specified directory.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
251: The specified directory could not be scanned for its trustees.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
253: An error occurred while file name was being copied to file name. Number bytes of the requested number bytes were copied.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
256: File name could not be renamed to name because the specified path does not exist.
Source:
utility name in message prefix
Possible Cause:
The user attempted to rename a file to a path that does not exist.
Action:
Rename the file to an existing path.
257: File name could not be renamed to name because a file with the same name already exists.
Source:
utility name in message prefix
Possible Cause:
The user attempted to rename a file using a name that already exists.
Action:
Rename the file with a different name.
258: File name could not be renamed to name because the file is currently being used.
Source:
utility name in message prefix
Possible Cause:
The user attempted to rename a file that is currently being used.
Action:
Wait until the file is not longer being used; then rename the file.
259: File name could not be renamed to name because the directory handle was invalid.
Source:
utility name in message prefix
Possible Cause:
An internal system error has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
260: File name could not be renamed to name because the new file name is illegal.
Source:
utility name in message prefix
Possible Cause:
The user tried to give the file a name reserved by DOS or one that contains control characters (such as * and ?).
Action:
Give the file a valid name.
261: File name could not be renamed to name because this station has no file rename privileges in the specified directory.
Source:
utility name in message prefix
Explanation:
NetWare’s rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.
Action:
Obtain the necessary rights to complete this task.
262: File name could not be renamed to name because the server is out of dynamic workspace.
Source:
utility name in message prefix
Possible Cause:
The server does not have enough memory.
272: The specified path does not exist.
Source:
utility name in message prefix
Possible Cause:
The path the user specified does not exist.
Action:
Make sure that the user specifies an existing path.
321: The system could not unlink file name because the file was not found.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
322: The system could not unlink file name because the specified path was not found.
Source:
utility name in message prefix
Possible Cause:
An internal system error has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
323: The system could not unlink file name because access was denied.
Source:
utility name in message prefix
Explanation:
NetWare’s rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.
Action:
Obtain the necessary rights to complete this task.
334: File name could not be closed because the specified file handle is invalid.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
337: File name could not be created because the specified directory could not be found.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid path when the user tried to create the file.
Action:
Type a valid path.
338: File name could not be created because too many files are open.
Source:
utility name in message prefix
Possible Cause:
The number of open files allowed on the system has been exceeded.
Action:
Close one or more open files, or wait until another user closes a file; then try again.
339: File name could not be created because access was denied.
Source:
utility name in message prefix
Explanation:
NetWare’s rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.
Action:
Obtain the necessary rights to complete this task.
340: File name could not be opened because the specified files could not be found.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid filename or mistyped the path. Another possibility is that an internal system error has occurred.
Action:
Try again, making sure the filename and path are valid and typed correctly. If the problem persists, contact a Novell support provider.
341: File name could not be opened because the specified directory could not be found.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid filename or mistyped the path. Another possibility is that an internal system error has occurred.
Action:
Try again, making sure the filename and path are valid and typed correctly. If the problem persists, contact a Novell support provider.
342: File name could not be opened because too many files are already open.
Source:
utility name in message prefix
Possible Cause:
The number of open files allowed on the system has been exceeded.
Action:
Close one or more open files, or wait until another user closes a file; then try again.
343: File name could not be opened because access was denied.
Source:
utility name in message prefix
Explanation:
NetWare’s rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.
Action:
Obtain the necessary rights to complete this task.
344: File name could not be opened because the specified access code is invalid.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid access code.
Action:
Use a valid access code.
345: File name could not be read because access was denied. The read request was for number bytes.
Source:
utility name in message prefix
Explanation:
NetWare’s rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.
Action:
Obtain the necessary rights to complete this task.
346: File name could not be read because the specified file handle was invalid. The read request was for number bytes.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation.If the problem persists, contact a Novell support provider.
347: Directory name could not be created because the specified path was not found.
Source:
utility name in message prefix
Possible Cause:
The user mistyped the path. Another possibility is that an internal system error has occurred.
Action:
Try again, making sure the path is valid and typed correctly. If the problem persists, contact a Novell support provider.
348: Directory name could not be created because access was denied.
Source:
utility name in message prefix
Explanation:
NetWare’s rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.
Action:
Obtain the necessary rights to complete this task.
349: The system could not write to file name because access was denied. The write request was for number bytes.
Source:
utility name in message prefix
Explanation:
NetWare’s rights security system controls which directories, subdirectories, and files a user can access and what the user is allowed to do with them.
Action:
Obtain the necessary rights to complete this task.
350: The system could not write to file name because the specified file handle was invalid. The write request was for number bytes.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
354: The combined width of the program header and the version number is greater than 34. This means that the header will be overwritten by the date and time for certain days in certain months. Shorten the header message.
Source:
utility name in message prefix
Possible Cause:
The text string is too wide to fit, possibly as a result of expansion during translation. (No more than 34 characters are allowed for the program name and version in the header.)
Action:
Contact a Novell support provider.
385: The new bindery object name could not be created. The maximum number of bindery objects specified during installation has been reached. You must increase the number of bindery objects available on this server.
Source:
utility name in message prefix
Possible Cause:
The new bindery object indicated in the message could not be created because the maximum number of bindery objects has been reached.
Action:
Modify the configuration file to allow more bindery objects on the server.
415: File pattern path_string cannot be erased because some of the files in the directory are currently being used by another station.
Source:
utility name in message prefix
Possible Cause:
The user cannot delete files that are being used by another user.
Action:
Wait until all the files are closed; then try again.
416: The server does not have enough memory to complete the request.
Source:
utility name in message prefix
417: Either the file with the specified file handle could not be closed, or the bindery failed.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. Novell support provider
418: The file was successfully closed, but the queue job could not be started.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Try again. If the problem persists, contact a Novell support provider.
421: Error number occurred during attempt to get a directory path from a directory handle.
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
425: Create Queue was passed an invalid queue name (name).
Source:
utility name in message prefix
Possible Cause:
An internal system error probably has occurred.
Action:
Restart the workstation. If the problem persists, contact a Novell support provider.
533: The Unicode files cannot be found.
Source:
utility name in message prefix
541: The specified volume does not exist.
Source:
utility name in message prefix
Possible Cause:
The user specified an invalid volume name.
Action:
Try again, using a valid volume name.
555: The system could not get physical volume information for volume object name.
Source:
utility name in message prefix
Possible Cause:
An internal error prevented the program from getting the volume information.
Action:
Restart the utility and try again. If the problem persists, contact a Novell support provider.
561: The system was not able to allocate a buffer for the current operation.
Source:
utility name in message prefix
Possible Cause:
The most likely explanation is that the workstation does not have enough memory.
562: The system was not able to read the volume objects in the current context.
Source:
utility name in message prefix
Possible Cause:
The database is corrupt, the search drive is incorrect, or the workstation has a connection problem.
Action:
If the database is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact a Novell support provider.
563: The system was not able to retrieve a count of volume objects in the current context.
Source:
utility name in message prefix
Possible Cause:
An internal error prevented the program from getting the volume information.
Action:
Restart the utility and try again. If the problem persists, contact a Novell support provider.
564: The system was not able to read the name of a volume object in the current context.
Source:
utility name in message prefix
Possible Cause:
The database is corrupt, the search drive is incorrect, or the workstation has a connection problem.
Action:
If the database is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact a Novell support provider.
565: The current context has not been set properly.
Source:
utility name in message prefix
Possible Cause:
The Novell eDirectory object name incorrect.
Action:
Make sure the object name is typed correctly. (Use ConsoleOne to verify the correct name.)
Possible Cause:
The workstation does not have enough memory to set up the context.
566: The system was not able to set the current context.
Source:
utility name in message prefix
Possible Cause:
The eDirectory object name incorrect.
Action:
Make sure the object name is typed correctly. (Use ConsoleOne to verify the correct name.)
Possible Cause:
The workstation does not have enough memory to set up the context.
567: The system was not able to get a connection number to access volume object name.
Source:
utility name in message prefix
Possible Cause:
The database is corrupted, the search drive is incorrect, or the workstation has a connection problem.
Action:
If the database is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact a Novell support provider.
568: The system was not able to get a connection ID for server name.
Source:
utility name in message prefix
Possible Cause:
For some unexpected reason, this utility could not obtain information about a particular server. No other information is available.
Action:
Try issuing the command again from a different drive. If the problem persists, contact a Novell support provider.
569: An invalid volume object string was entered.
Source:
utility name in message prefix
Possible Cause:
The volume object name the user entered is invalid.
Action:
Make sure the user is specifying a valid volume object name.
572: The system could not reset the context after escaping from the Browse option.
Source:
utility name in message prefix
Possible Cause:
An internal program error occurred.
Action:
Try again. If the problem persists, contact a Novell support provider.
574: The system could not create a portal in which to display the function key help line.
Source:
utility name in message prefix
Possible Cause:
This error could indicate lack of workstation memory or an internal problem in the program.
575: The system could not create a portal in which to display information area text.
Source:
utility name in message prefix
Possible Cause:
This error could indicate lack of workstation memory or an internal problem in the program.
576: An incorrect version of the system help file SYS$HELP.HEP was found. The correct version is version. System help will be disabled.
Source:
utility name in message prefix
Possible Cause:
When the system tried to initialize the SYS$HELP.HEP file, it could not 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 subdirectory of the NLS directory as specified by the NWLANGUAGE variable. The NLS directory in this instance is itself a subdirectory 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 can be found in the user’s login script or in the AUTOEXEC.BAT file.
-
The first directory found under the child NLS subdirectory of the load directory.
-
The first directory found under the sibling NLS subdirectory of the load directory.
Action:
Find a current version of the system help file and copy it to a directory that is mapped to an existing search drive, or map a search drive to the file.
577: The message file found utility_name.MSG is an incorrect version. The correct version is version. See your network supervisor for assistance.
Source:
utility name in message prefix
578: The help file found (name.HEP) is an incorrect version. The correct version is version. Program help will be disabled.
Source:
utility name in message prefix
Possible Cause:
When the utility tried to initialize the utility_name.HEP file, it could not 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 subdirectory of the NLS directory as specified by the NWLANGUAGE variable. The NLS directory in this instance is itself a subdirectory 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 are 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 help file and copy it to a directory that is mapped to an existing search drive, or map a search drive to the file.
588: The system was unable to parse the specified path.
Source:
utility name in message prefix
Possible Cause:
The program could not find the directory path because the user specified a directory path that does not exist or mistyped the directory path.
Action:
Use the FILER utility to examine the directory. Type the directory path correctly. The correct syntax is as follows:
Server\ volume: directory\ subdirectory\ file
or
Drive: directory\ subdirectory\ file
The user can use the MAP command or the NETUSER utility to map a network drive to a directory; then the user can specify the drive, rather than the directory path, in the command.
589: The system received an invalid path for the current server mode.
Source:
utility name in message prefix
Possible Cause:
This is probably an internal error in the program.
Action:
Try again. If the problem persists, contact a Novell support provider.
590: An error occurred while attempting to build a class list. It is likely that the workstation is out of memory.
Source:
utility name in message prefix
Possible Cause:
The workstation does not have enough memory.
591: The path must contain a full drive specification, including a :.
Source:
utility name in message prefix
Possible Cause:
The user specified an incomplete drive designation.
Action:
Specify a complete designation. Be sure the drive name is followed by a colon (:).
592: Directory_name is part of the current tree.
Source:
utility name in message prefix
Possible Cause:
The user tried to add a directory name to the tree, but a directory with that name is already in the tree.
Action:
If the user is trying to add a directory that is already in the tree, no action is necessary. Otherwise, assign a different name to the directory the user wants to add.
593: The system could not read the network address for directory_name.
Source:
utility name in message prefix
Possible Cause:
The database is corrupt, the search drive are incorrect, or the workstation has a connection problem.
Action:
If the database is in the proper search path and is a current version, try replacing it with a backup. Make sure the workstation is connected to the network. Try again. If the problem persists, contact a Novell support provider.