These are the NSS error codes included in this section:
-
Common Layer Errors (Range 20000-24999)
-
NW Semantic Agent Specific Errors (Range 22000-22099)
-
CD Specific Errors (Range 22500-22599)
-
ZFS Storage System Specific Errors (Range 24800-24899)
Source:
NSS, Common Layer, General
Explanation:
Server memory is not sufficient to complete the request.
Possible Cause:
Too many NetWare® Loadable Module™ (NLM™) program or applications have been loaded.
Action:
Unload an NLM program or application that does not need to be used. Lower the percentage of memory used by NSS for caching.
20001 zERR BAD CONNECTION ID
Source:
NSS, Common Layer, General
Explanation:
Every client has a connection to the server. When a request comes in from a NetWare Core Protocol™ (NCP) or a NLM program, it supplies a connection ID or station number. NSS uses this number to look up the connection structure. If the connection ID or station number is invalid, then NSS cannot get the connection information it needs to complete the request.
Possible Cause:
Corruption occurred in the connection structures stored on the client or the server.
Action:
Log out and log in to NetWare again.
Source:
NSS, Common Layer, General
Explanation:
The workstation does not have a connection to the server.
Possible Cause:
Connection timed out.
Action:
Log in to NetWare again.
20003 zERR XID NOT SUPPORTED
Source:
NSS, Common Layer, General
Explanation:
If a Loadable Storage Subsystems (LSS) chose not to support a transaction semantic for NSS, this error will be returned for transaction-related requests.
Possible Cause:
An internal programming error occurred.
20004 zERR BUFFER TOO SMALL
Source:
NSS, Common Layer, General
Explanation:
The given buffer is too small.
Possible Cause:
A NLM program passed in a buffer that was too small to perform the requested operation.
Action:
Contact the provider of the NLM program.
20005 zERR RETURN PARA NULL
Source:
NSS, Common Layer, General
Explanation:
The return parameter is null.
Possible Cause:
A NLM program passed in a null parameter where NSS expected a non-null parameter.
Action:
Contact the provider of the NLM program.
20006 zERR QUAD TOO BIG FOR LONG
Source:
NSS, Common Layer, General
Explanation:
The upper 32 bits of a 64-bit number are not zero.
Possible Cause:
A programming error occurred in a NLM program.
Action:
Contact the provider of the NLM program.
20007 zERR CONNECTION NOT LOGGED IN
Source:
NSS, Common Layer, General
Explanation:
The connection has not been logged in to the server.
Possible Cause:
NSS sent a NCP packet to the server that requires the user to be logged in.
Action:
Make sure the user is logged in to the server.
20008 zERR BAD PARAMETER VALUE
Source:
NSS, Common Layer, General
Explanation:
A parameter that was passed to an NSS routine is invalid.
Possible Cause:
A NLM program or NCP packet called an NSS routine with an invalid parameter.
Action:
Contact the provider of the NLM program.
20009 zERR UNABLE TO INIT ADMIN VOL
Source:
NSS, Common Layer, General
Explanation:
The nss_admin volume could not be started.
Possible Cause:
An internal program error occurred during initialization.
20010 zERR INVALID SEMANTIC AGENT ID
Source:
NSS, Common Layer, General
Explanation:
A bad semantic agent ID was given.
Possible Cause:
The user tried to load a NLM program that claimed to be a semantic agent that does not have a valid semantic agent ID for this version of NSS.
Action:
Upgrade NSS to a version that recognizes this NLM program as a semantic agent.
Source:
NSS, Common Layer, General
Explanation:
An invalid state was requested.
Possible Cause:
An internal programming error occurred.
Source:
NSS, Common Layer, General
Explanation:
The operation requested is not supported.
Possible Cause:
A client or a NLM program made an API call that is not supported by NSS.
20013 zERR MEDIA CORRUPTED
Source:
NSS, Common Layer, General
Explanation:
The media is corrupted.
Possible Cause:
A hardware failure occurred.
Action:
Check the hardware.
Possible Cause:
A disk media failure occurred.
Action:
Check the disk media.
Possible Cause:
Invalid data was written to the disk.
Action:
Restore the backup data to the disk.
20099 zERR OBJECT NOT FOUND
Source:
NSS, Common Layer, eDirectory or NDS
Explanation:
The object was not found in eDirectory™ or NDS®.
Possible Cause:
A trustee was used that eDirectory or NDS cannot find in its database.
Action:
Make sure the trustee is valid.
Possible Cause:
A new trustee has not been updated on all replicas.
Action:
Wait for eDirectory or NDS to finish replicating. If the error persists after replication is complete, run DSREPAIR.
Source:
NSS, Common Layer, General File System
Severity:
Informational status error
Explanation:
An attempt was made to read past the end of a file.
This is a normal error when reading a file that indicates the application has reached the end of the file and should stop reading the file.
Possible Cause:
This error is expected to be returned to the program when the application is reading a file and it has reached the end of the file and should stop reading it.
Action:
If this error occurs in a program you are running and it persists, contact a Novell Support Provider.
If programming an application, make sure the application stops reading the file.
20101 zERR HARD READ ERROR
Source:
NSS, Common Layer, General File System
Explanation:
A read error occurred when an attempt was made to read from media.
Possible Cause:
Disk controller failure.
Action:
Reset the hardware and try again.
Possible Cause:
A disk media failure occurred when NSS was trying to read a sector that has gone bad on the disk.
Action:
Find out what file is affected and try to work around it. Or, restore the data from a backup.
20102 zERR HARD WRITE ERROR
Source:
NSS, Common Layer, General File System
Explanation:
A write error occurred when an attempt was made to read from media.
Possible Cause:
A failure occurred on one of the following:
-
Hardware
-
Disk controller
-
Media
Action:
Stop any further operations on the affected hardware and repair it.
Source:
NSS, Common Layer, General File System
Explanation:
No disk space is available.
Possible Cause:
The disk is full of active or deleted files.
Action:
If salvage is enabled, purge deleted files from the salvage area. Delete the files that are no longer needed.
20104 zERR FILE TOO LARGE
Source:
NSS, Common Layer, General File System
Explanation:
The file is too large for the given pool.
Possible Cause:
This error applies only to the nss_admin volume and should not happen.
Action:
Unload and reload NSS. Reboot the server.
20200 zERR VOLUME ALREADY INITIALIZED
Source:
NSS, Common Layer, General Storage System
Explanation:
An attempt was made to initialize a volume that is already set up.
Possible Cause:
This error is not currently used by NSS.
20201 zERR QUEUE READ FAILURE
Source:
NSS, Common Layer, General Storage System
Explanation:
NSS was unable to queue a read request.
Possible Cause:
The disk driver is no longer accepting read requests.
Action:
Reduce the load on the server. Reboot the server.
20202 zERR QUEUE WRITE FAILURE
Source:
NSS, Common Layer, General Storage System
Explanation:
NSS was unable to queue a write request.
Possible Cause:
The disk driver is no longer accepting write requests.
Action:
Reduce load on the server, or reboot the server.
Source:
NSS, Common Layer, General Storage System
Explanation:
An attempt to read a low-level asynchronous block failed.
Possible Cause:
A media failure occurred, such as one or more sectors on the disk cannot be read.
Action:
Retry the operation. If the error persists, reboot the server. Replace or reformat the disk, and then restore the affected areas from backup.
Source:
NSS, Common Layer, General Storage System
Explanation:
An attempt to write to a low-level asynchronous block failed.
Possible Cause:
A failure occurred in the disk controller or other hardware component. If Read After Write Verify is turned on, the media might have a bad sector.
Action:
Try the write again.
If the error persists, do the following:
-
Reboot the server.
-
Try to back up the disk so you have the most current snapshot of the data.
-
Reformat the disk.
-
Restore the data from backup.
20300 zERR INVALID BEAST ID
Source:
NSS, Common Layer, Beast Specific
Explanation:
An invalid beast (file or directory) ID was specified.
Possible Cause:
An application tried to open a file with a directory entry ID that is not valid. The beast (file or directory) could have been deleted between the time the ID was obtained and when it was used.
Possible Cause:
When programming, an uninitialized value was used.
Action:
If the error occurs in a program you are using, contact a Novell Support Provider.
When programming, make sure the application uses a valid ID.
20301 zERR BEAST CLASS ALREADY DEFINED
Source:
NSS, Common Layer, Beast Specific
Explanation:
The given beast class ID is already in use.
Possible Cause:
An internal error programming error occurred. This error should not occur until future releases of NSS start identifying new beast types.
Action:
Unload and reload NSS.
20302 zERR BEAST CLASS NOT DEFINED
Source:
NSS, Common Layer, Beast Specific
Explanation:
The given beast class ID is not defined.
Possible Cause:
An internal program error occurred. This error should not occur in the NetWare 5 release of NSS.
Action:
Unload and reload NSS. Check any recently installed NLM programs.
20303 zERR BEAST CLASS ROUTINE NOT DEF
Source:
NSS, Common Layer, Beast Specific
Explanation:
A required beast class routine is missing.
Possible Cause:
An internal programming error occurred in how a beast class was implemented.
Action:
Contact a Novell support provider.
20304 zERR BEAST CLASS ROUTINE MULT DEF
Source:
NSS, Common Layer, Beast Specific
Explanation:
A beast class routine is defined multiple times.
Possible Cause:
Server memory is corrupted.
Action:
Do the following:
-
Unload NSS and reload.
-
Reboot the server.
Possible Cause:
An internal programming error occurred.
20305 zERR COMN OP NOT SUPPORTED
Source:
NSS, Common Layer, Beast Specific
Explanation:
The specified COMN operation (beast or volume) is not supported. COMN refers to the "common" layer in NSS.
All Semantic Agents (SAs) and Loadable Storage Subsystems (LSSs) connect to the common layer. Each volume (beast) must supply a set of common operations; however, some beasts might not supply the complete set.
Possible Cause:
An attempt was made to access a volume (beast type) in a manner that was not intended. Normally, this should not be possible. The error might be caused by trying to run some applications on the nss_admin volume.
Action:
The nss_admin volume is not intended for general application use, so do not use it for running applications.
Possible Cause:
A conflict with the operating system occurred.
Action:
Unload and reload NSS.
20306 zERR INHERITANCE DEPTH EXCEEDED
Source:
NSS, Common Layer, Beast Specific
Explanation:
The maximum inheritance depth has been exceeded.
Possible Cause:
An internal programming error occurred in NSS.
20307 zERR BEAST SIZE CHANGED
Source:
NSS, Common Layer, Beast Specific
Explanation:
The size of a beast object changed when it should not have changed.
Possible Cause:
The versions of NSS modules and the disk might not be synchronized.
Action:
Unload and reload NSS.
Possible Cause:
An internal programming error occurred.
20308 zERR BAD LENGTH UNPACKING BEAST
Source:
NSS, Common Layer, Beast Specific
Explanation:
NSS detected an inconsistent length while unpacking a beast object.
Possible Cause:
An internal programming error occurred.
Action:
Unload and reload NSS.
20309 zERR UNSUPPORTED OBJECT LAYOUT
Source:
NSS, Common Layer, Beast Specific
Explanation:
The layout of an object on the disk is in an unsupported format.
Possible Cause:
A version of NSS is being used that does match the format of the data on the disk.
Action:
If the volume on the disk was created with a older version of NSS, do the following:
-
Load the older version of NSS that was previously used.
-
Back up the files.
-
Destroy the volume.
-
Load the current release of NSS.
-
Create a new NSS volume.
-
Restore the files.
20310 zERR BEAST CORRUPTED
Source:
NSS, Common Layer, Beast Specific
Explanation:
The beast object is corrupted.
Action:
The LSS rebuild should repair the beast object if possible; however, if the rebuild cannot repair the beast object then it can delete the beast object.
20400 zERR INVALID HANDLE PATH
Source:
NSS, Common Layer, Naming
Explanation:
The path handle type is not valid.
Possible Cause:
The path handle passed in by a NCP packet or a NLM program is invalid. The handle might be released or was never initialized.
Action:
Acquire the path handle again, and make sure the directory is valid.
20401 zERR BAD FILE HANDLE
Source:
NSS, Common Layer, Naming
Explanation:
The file handle is out of range, is a invalid instance, or does not exist.
Possible Cause:
The file handle has been closed and is no longer valid, or the file handle was not initialized.
Action:
Get a new file handle by opening the file again.
20402 zERR BAD CONTEXT HANDLE
Source:
NSS, Common Layer, Naming
Explanation:
The context for a context handle is invalid.
Possible Cause:
A directory in the path name has been deleted.
Action:
Restore the directory or change the path name.
Source:
NSS, Common Layer, Naming
Explanation:
The path name is invalid because the incorrect syntax was used.
Possible Cause:
An internal programming error occurred. The name space must match the syntax of the name being used.
20404 zERR INVALID CHAR IN NAME
Source:
NSS, Common Layer, Naming
Explanation:
The path name has an invalid character.
Possible Cause:
For the selected name space, at least one character in the path name is invalid.
Action:
Change the character or the name space.
Source:
NSS, Common Layer, Naming
Explanation:
The path is syntactically incorrect.
Possible Cause:
One of the following problems is in the path name:
-
An invalid name space or name type
-
A wildcard character in the volume name
-
A volume in the path name when one was not expected
-
A path name that requires a volume name
Action:
Fix the path name.
Source:
NSS, Common Layer, Naming
Explanation:
A request was made using a filename that is reserved and cannot be used by any other requests.
Possible Cause:
A filename was used that is reserved for DOS use only.
Action:
Use a different filename.
20407 zERR NAME NOT FOUND IN DIRECTORY
Source:
NSS, Common Layer, Naming
Explanation:
The name does not exist in the directory being searched.
Possible Cause:
A file or directory has been deleted, or moved, or the name has been mistyped.
Action:
Make sure the specified file exists and that the name has been typed correctly.
20408 zERR NOT DIRECTORY FILE
Source:
NSS, Common Layer, Naming
Explanation:
The name was found; however, it referred to an object that was not a directory.
Possible Cause:
A name in the path was a file instead of a directory.
Action:
Correct the name in the path.
20409 zERR NO NAMES IN PATH
Source:
NSS, Common Layer, Naming
Explanation:
A null filename was given.
Possible Cause:
The request required a path name but one was not supplied.
Action:
Supply a path name, or change the request to one that does not require a path name.
20410 zERR NO MORE NAMES IN PATH
Source:
NSS, Common Layer, Naming
Explanation:
While doing a search for a wildcard pattern, NSS ran out of names to search.
Possible Cause:
This is a normal status error indicating that all names matching the wildcard pattern have been returned.
Action:
Terminate the search.
20411 zERR PATH MUST BE FULLY QUALIFIED
Source:
NSS, Common Layer, Naming
Explanation:
The path name must be fully qualified in this context.
Possible Cause:
The path name must include volume name in this context.
Action:
Change the path name or change the context.
20412 zERR FILE ALREADY EXISTS
Source:
NSS, Common Layer, Naming
Explanation:
The given file already exists.
Possible Cause:
An attempt was made to create a file in a directory where a file by that name already exists.
Action:
Change the name of the file being created or delete the file that is already there.
20413 zERR NAME NO LONGER VALID
Source:
NSS, Common Layer, Naming
Explanation:
This is an informational error indicating the directory or filename is no longer valid.
Possible Cause:
The file or directory was deleted in the middle of an operation.
20414 zERR BAD SEARCHMAP ID
Source:
NSS, Common Layer, Naming
Explanation:
The searchMapID is invalid.
Possible Cause:
When scanning, the search maps keep the current location in a directory. The request passed in an old or uninitialized search map ID.
Action:
Get a new search map ID, and restart the directory scan.
20415 zERR INVALID TYPE FILE
Source:
NSS, Common Layer, Naming
Explanation:
The file type is wrong for the requested operation.
Possible Cause:
An attempt was made to open a directory for normal file read/write operations or to do a directory scan on a file.
Action:
Retry the operation using the correct file or directory names.
20416 zERR INVALID FILE TYPE
Source:
NSS, Common Layer, Naming
Explanation:
An invalid file type was specified.
Possible Cause:
Corrupted data exists in the name database.
Action:
Unload and reload NSS or reboot the server. If problem persists, rebuild NSS using the REBUILD tool in the Utilities menu.
Possible Cause:
A programming error occurred.
20417 zERR DIRECTORY NOT EMPTY
Source:
NSS, Common Layer, Naming
Explanation:
The directory still has files in it.
Possible Cause:
An attempt was made to delete a directory that still contains files or directories.
Action:
Delete any remaining contents of the directory, and then try to delete it again.
20418 zERR BAD SEARCH OPTIONS
Source:
NSS, Common Layer, Naming
Explanation:
An invalid search option was specified.
Possible Cause:
A NLM program or client supplied a bad option in a search request.
Action:
Contact the developer of the NLM program or client.
20419 zERR INVALID SEARCH SEQ NUM
Source:
NSS, Common Layer, Naming
Explanation:
An invalid search sequence number was given.
Possible Cause:
A NLM program or application used a stale (old) sequence number in a search request.
Action:
Restart the NLM program or application.
20420 zERR INTERNAL DIRECTORY ERROR
Source:
NSS, Common Layer, Naming
Explanation:
An internal error has occurred accessing a directory.
Possible Cause:
This error is not currently used by NSS.
20421 zERR INVALID MODIFY PARAMETER
Source:
NSS, Common Layer, Naming
Explanation:
An invalid parameter to modify information exists.
Possible Cause:
The ID could not be found in eDirectory or NDS.
Action:
Verify that the ID being used is in eDirectory or NDS.
20422 zERR INVALID USER ID
Source:
NSS, Common Layer, Naming
Explanation:
The user ID is not valid.
Possible Cause:
An attempt was made to use a user ID that is not valid, or the ID is not propagated to the replica that NSS is using.
Action:
Make sure the ID is valid and propagated.
20423 zERR NOTHING CHANGED
Source:
NSS, Common Layer, Naming
Explanation:
An attempt was made to modify an object, and nothing changed.
Possible Cause:
An attempt was made to rename a file to the name it already had.
Action:
Sometimes this is the desired result and this error is just informational. If this is not desired, check the source and destination names.
20424 zERR NO FILES FOUND
Source:
NSS, Common Layer, Naming
Severity:
Informational status error
Explanation:
No files matched the wildcard pattern that was specified.
Possible Cause:
The directory is empty, or the wildcard pattern does not match any filename in the directory.
Action:
Make sure the wildcard pattern is valid.
Possible Cause:
This is a normal error that is returned when the scanning of a directory is finished and the application should stop scanning the directory.
Action:
If this error occurs in a program you are running and it persists, contact a Novell Support Provider.
If programming, make sure the application stops scanning the directory.
20425 zERR UNABLE TO RETURN INFO
Source:
NSS, Common Layer, Naming
Explanation:
The build information routines could not complete.
Possible Cause:
An invalid request was made for information about a file.
Action:
Make sure the request code is correct.
20426 zERR FILE DID NOT MATCH ATTR
Source:
NSS, Common Layer, Naming
Explanation:
The file did not match the matchFileAttrSet/Clear criteria.
Possible Cause:
The file found did not match the attributes that were included in the search criterion.
Action:
Change attributes for the search.
20427 zERR FILE DID NOT MATCH TYPE
Source:
NSS, Common Layer, Naming
Explanation:
The file did not match the matchFileType criteria.
Possible Cause:
This error is not currently used by NSS.
20428 zERR FILE DID NOT MATCH TYPEATTR
Source:
NSS, Common Layer, Naming
Explanation:
The file did not match the matchTypeAttrSet/Clear criteria.
Possible Cause:
This error is not currently used by NSS.
20429 zERR NEXT VOLUME FOUND
Source:
NSS, Common Layer, Naming
Explanation:
The source path parsing was suspended because a volume change occurred.
Possible Cause:
This error is not currently used by NSS.
20430 zERR NEXT VOLUME FOUND DEST PATH
Source:
NSS, Common Layer, Naming
Explanation:
The destination path parsing was suspended because a volume change occurred.
Possible Cause:
This error is not currently used by NSS.
20431 zERR UNABLE TO OPEN BEAST
Source:
NSS, Common Layer, Naming
Explanation:
NSS is unable to open a beast (any NSS file-like object).
Possible Cause:
When NSS tried to look up a particular Z-ID, it could not find the object referenced by that Z-ID.
Action:
NSS should clean up the reference to that Z-ID.
20432 zERR NSPACE NAME ALREADY DEFINED
Source:
NSS, Common Layer, Naming
Explanation:
A name for the name space specified is already defined.
Possible Cause:
An internal programming error occurred. NSS is trying to load two name spaces that claimed the same name space, such as LONG and MAC.
20433 zERR NAME NOT FOUND IN BEAST
Source:
NSS, Common Layer, Naming
Explanation:
The name requested was not found in the beast object.
Possible Cause:
This error is not currently used by NSS.
20434 zERR PARENT NOT FOUND IN BEAST
Source:
NSS, Common Layer, Naming
Explanation:
The parent (directory) requested was not found in the specified beast (file or directory).
Possible Cause:
The beast (file or directory) tried to access its parent, but the parent directory could not be found.
Action:
Rebuild the volume using rebuild in the Utilities menu.
20435 zERR DIR CANNOT BE OPENED
Source:
NSS, Common Layer, Naming
Explanation:
The directory specified in the request cannot be opened.
Possible Cause:
While resolving a path name, one of the directories in the path could not be opened.
Action:
Figure out why the directory could not be opened and try the operation again.
20436 zERR INVALID CONTEXT HANDLE TYPE
Source:
NSS, Common Layer, Naming
Explanation:
The type of context handle specified is invalid.
Possible Cause:
The type of context handle specified is used to protect the "Z" interfaces for NSS that have not been released yet.
20437 zERR CONTAINER NOT FILE BEAST
Source:
NSS, Common Layer, Naming
Explanation:
The container for a beast object must be a File_s beast. Only file beasts, which includes many types of beast objects including file and directory beasts, can be used as parents for other beasts.
Possible Cause:
An internal programming error occurred.
20438 zERR NO OPEN PRIVILEGE
Source:
NSS, Common Layer, Naming
Explanation:
An attempt was made to open a file without the access privileges being assigned to the requestor.
Possible Cause:
Rights have not be granted for the user trying to access the beast (file or directory).
Action:
Change the rights on the beast (file or directory), or give the user the rights to access the beast object.
20439 zERR NO MORE CONTEXT HANDLE IDS
Source:
NSS, Common Layer, Naming
Explanation:
No more context handle IDs are available.
Possible Cause:
Each connection is limited to 126 context handles. This number has been exceeded. The connection might be failing to clean up context handles.
Action:
Reset the connection.
20440 zERR PREV DIR AFTER DATASTREAM
Source:
NSS, Common Layer, Naming
Explanation:
The PrevDir operation is not allowed after a data stream is processed.
Possible Cause:
A ".." exists after a data stream separator ("::", ":").
Action:
Remove the ".." from the path name.
20441 zERR INVALID PATH FORMAT
Source:
NSS, Common Layer, Naming
Explanation:
The pathFormat is invalid or unsupported.
Possible Cause:
The format of a path name for the given name space was incorrect.
Action:
Make sure that only legal characters for that name space are being used and that only one volume name is in the path name.
20442 zERR CANT WILDOPEN A DATASTREAM
Source:
NSS, Common Layer, Naming
Explanation:
Performing a zWildOpen call on a data stream is illegal.
Possible Cause:
An attempt was made to access a normal file as if it were a directory.
Action:
Try the operation on a directory.
20443 zERR NAMING INCONSISTENCY
Source:
NSS, Common Layer, Naming
Explanation:
An internal naming inconsistency has occurred. The volume needs recovery.
Possible Cause:
Media corruption occurred.
Possible Cause:
A hardware failure occurred.
Action:
Make sure the hardware is functioning properly and that the media is not corrupted, and then rebuild the volume.
Possible Cause:
An internal programming error occurred.
Source:
NSS, Common Layer, Naming
Explanation:
The Z-ID is not found in the directory specified.
Possible Cause:
An internal consistency error occurred in the NSS databases.
Action:
Verify the physical integrity of the specified pool, using nss /poolverify=poolname. Rebuild only if necessary, using nss /poolrebuild=poolname. Before you rebuild, make sure you have a backup tape of the problem pool and have installed the latest OS and NSS patches for your version of NetWare. A rebuild can take several hours, depending on the size of the pool.
20499 zERR INVALID NAME TYPE
Source:
NSS, Common Layer, Name Type
Explanation:
An invalid name type was specified.
Possible Cause:
An internal programming error occurred. The name types are set only by the semantic agent, so this indicates an error in the code or some other corruption.
20500 zERR ALL FILES IN USE
Source:
NSS, Common Layer, Rename
Explanation:
An attempt was made to rename one or more files when all of them are currently in use.
Possible Cause:
Another user or application has the files open.
Action:
When doing the rename, make sure none of the files are in use.
20501 zERR SOME FILES IN USE
Source:
NSS, Common Layer, Rename
Explanation:
An attempt was made to rename some files while some of them were still in use.
Possible Cause:
Another user or application has the files open.
Action:
When doing the rename, make sure none of the files are in use.
20502 zERR ALL FILES READ ONLY
Source:
NSS, Common Layer, Rename
Explanation:
An attempt was made to rename all files, and the files are labeled with a read-only attribute.
Possible Cause:
Read-only files cannot be renamed.
Action:
If appropriate, do the following to the files that need to be renamed:
-
Remove the read-only attribute from the files to be renamed.
-
Rename the files.
-
Restore the read-only attribute.
20503 zERR SOME FILES READ ONLY
Source:
NSS, Common Layer, Rename
Explanation:
An attempt was made to rename some files, and some of the files are labeled with the read-only attribute.
Possible Cause:
Read-only files cannot be renamed.
Action:
If appropriate, do the following to the files that need to be renamed:
-
Remove the read-only attribute from the files to be renamed.
-
Rename the files.
-
Restore the read-only attribute.
20504 zERR ALL NAMES EXIST
Source:
NSS, Common Layer, Rename
Explanation:
An attempt was made to change the names of all files to filenames that are already being used.
Action:
Remove the files that already exist, or change the name to which the files are being renamed.
20505 zERR SOME NAMES EXIST
Source:
NSS, Common Layer, Rename
Explanation:
An attempt was made to change the names of some files to filenames that are already being used.
Action:
Remove the files that already exist, or change the name to which the files are being renamed.
20506 zERR NO RENAME PRIVILEGE
Source:
NSS, Common Layer, Rename
Explanation:
An attempt was made to rename the file without the appropriate access privileges.
Possible Cause:
The user does not have the necessary security equivalence to rename the file.
Action:
Give the user the necessary security equivalence, or add a trustee which is security equivalent to the user.
20507 zERR RENAME DIR INVALID
Source:
NSS, Common Layer, Rename
Explanation:
The selected directory cannot be renamed.
Possible Cause:
The directory is a root directory, and a root directory cannot be renamed. Or, an attempt was made to rename a directory to its parent. For example, rename \abc\def \abc
Action:
Make sure the directory is not a root directory. Make sure the new directory name has the complete path including the parent.
20508 zERR RENAME TO OTHER VOLUME
Source:
NSS, Common Layer, Rename
Explanation:
The rename or move operation cannot move the file or directory (beast) to a different volume.
Possible Cause:
Rename does not work across volumes.
Action:
Make sure the volumes for the source and destination are the same.
20509 zERR CANT RENAME DATA STREAMS
Source:
NSS, Common Layer, Rename
Explanation:
An attempt was made to rename a data stream. NSS is not allowed to rename a data stream, because data streams do not have names.
Possible Cause:
An internal programming error occurred.
20510 zERR FILE RENAME IN PROGRESS
Source:
NSS, Common Layer, Rename
Explanation:
The file is already being renamed by a different process.
Possible Cause:
An attempt was made to rename a file at the same time as another rename operation was being done.
Action:
Wait for the other rename to finish.
20511 zERR CANT RENAME TO DELETED
Source:
NSS, Common Layer, Rename
Explanation:
Only deleted files can be renamed to a deleted state.
Possible Cause:
An internal programming error occurred. The name type was set incorrectly.
20550 zERR INVALID DATA STREAM
Source:
NSS, Common Layer, Data Stream
Explanation:
The data stream is invalid.
Possible Cause:
A data stream, such as a Macintosh* resource fork, was never created for this file.
Action:
Make sure the file has the types of data streams the application is expecting.
20551 zERR CANT MOD DATA STREAM METADATA
Source:
NSS, Common Layer, Data Stream
Explanation:
The meta-data for the data stream cannot be modified.
Possible Cause:
NSS contains many types of beast objects such as files, directories, volumes, resources forks, or extended attributes.
Some of these beast objects, such as extended attributes, do not allow their stream meta-data to be directly modified.
Action:
Perform the modification on a type that is allowed.
20601 zERR INVALID SA HANDLE
Source:
NSS, Common Layer, Semantic Agent Handle
Explanation:
The handle for the semantic agent (SA) is invalid.
Possible Cause:
A NLM program is incorrectly registered as a semantic agent.
Action:
Contact the provider of the NLM program.
20602 zERR SA HANDLE TOO SMALL
Source:
NSS, Common Layer, Semantic Agent Handle
Explanation:
An attempt was made to allocate a handle for a SA that was too small.
Possible Cause:
As part of the request, a buffer big enough to hold a semantic agent data structure must be passed to it.
Action:
Change the request to pass in a bigger buffer.
20650 zERR FILE NOT IN DFS MODE
Source:
NSS, Common Layer, Direct File System (DFS)
Explanation:
The file was not switched to DFS mode or Direct I/O.
Possible Cause:
A programming error occurred. Before a file can be accessed using Direct I/O, it must be changed into that mode.
Action:
If the error occurs in the program you are using, contact a Novell Support Provider.
If you are debugging a program, call the "SwitchToDirectFileSystemMode" function before trying Direct I/O.
20651 zERR HOLE IN DFS FILE
Source:
NSS, Common Layer, DFS
Explanation:
The DFS files or Direct I/O cannot have holes.
Possible Cause:
An attempt was made to convert a file to Direct I/O access that is a sparce file. A sparce file is a file that does not have disk blocks assigned to every offset in the file.
Action:
If the error occurs in the program you are using, contact a Novell Support Provider.
If you are debugging a program, fill in the holes of the file.
Source:
NSS, Common Layer, DFS
Explanation:
The DFS files or Direct I/O cannot be read beyond the end of the file (EOF).
Possible Cause:
An attempt was made to use Direct I/O to access an offset beyond the end-of-file.
Action:
You might need to make the file larger.
20700 zERR INVALID NAMESPACE ID
Source:
NSS, Common Layer, Name Space
Explanation:
A Network Support Protocol (NSP) or a NLM program request passed in a name space ID that was out of the legal range.
Possible Cause:
A programming error occurred.
20701 zERR UNABLE TO FIND NAMESPACE
Source:
NSS, Common Layer, Name Space
Explanation:
The code for the given name space could not be located.
Possible Cause:
A request was made for a name space that is not loaded.
Action:
Make sure the NCP or a NLM program is using the correct name space.
20702 zERR INVALID NAMESPACE VERSION
Source:
NSS, Common Layer, Name Space
Explanation:
The version number for the name space is invalid.
Possible Cause:
An internal programming error occurred.
20703 zERR NAMESPACE ID IN USE
Source:
NSS, Common Layer, Name Space
Explanation:
The name space ID specified is already in use.
Possible Cause:
An internal programming error occurred.
20704 zERR INVALID PATH SEPARATOR
Source:
NSS, Common Layer, Name Space
Severity:
Informational status error
Explanation:
The name space does not support the requested type of path separator.
Possible Cause:
This error is expected to be returned to the program when a query is made to a name space to see if it supports a particular path separator type.
20705 zERR VOLUME SEPARATOR NOT SUPPORTED
Source:
NSS, Common Layer, Name Space
Severity:
Informational status error
Explanation:
The name space does not support volume separators.
Possible Cause:
This error is expected to be returned to the program when a query is made to a name space to see if it supports a particular volume separator type.
20750 zERR BAD ASYNCIO HANDLE
Source:
NSS, Common Layer, Async-I/O
Explanation:
The AsyncIOHandle ID is invalid.
Possible Cause:
This error is not currently used by NSS.
20751 zERR ASYNCIO CANCELED
Source:
NSS, Common Layer, Async-I/O
Explanation:
The asynchronous I/O is canceled.
Possible Cause:
This error is not currently used by NSS.
Source:
NSS, Common Layer, Encrypted Volume
Explanation:
Encrypted volume support libraries returned an error.
Possible Cause:
One or both of the following problems could cause this error.
Action:
Check strings that are being used as a password for an encrypted NSS volume.
20799 zERR_INVALID_VOLUME_PASSWORD
Source:
NSS, Common Layer, Encrypted Volume
Explanation:
Password supplied for encrypted volume use is invalid.
Possible Cause:
On the first activation after a system reboot, you must enter a valid password for an encrypted volume. If the password is invalid, you cannot activate the volume. Passwords are case sensitive.
Action:
Repeat the activation command for the volume and enter a valid password when prompted.
20800 zERR BAD VOLUME NAME
Source:
NSS, Common Layer, Volume
Explanation:
The volume name specified is syntactically incorrect.
Possible Cause:
This error is not currently used by NSS.
20801 zERR VOLUME NOT FOUND
Source:
NSS, Common Layer, Volume
Explanation:
The volume name specified could not be found.
Possible Cause:
No volume on the specified server has a volume name that matches the name specified.
Action:
Make sure the volume name matches a name of a volume on the server.
20802 zERR DEACTIVATING ADMINVOL
Source:
NSS, Common Layer, Volume
Explanation:
NSS cannot deactivate the nss_admin volume.
Possible Cause:
An internal NSS error occurred.
Action:
Unload and reload NSS.
20803 zERR VOLUME STATE CHANGE ABORTED
Source:
NSS, Common Layer, Volume
Explanation:
NSS had to abort the change of the volume state.
Possible Cause:
NSS could not change the state of a volume, so it aborted the change. In some cases, the administrator is prompted to answer whether they want to continue the change in volume state. If the administrator responds negatively, then this error is returned to the operating system.
Action:
If the administrator wants to change the state of the volume but cannot, unload NSS and load it again.
20804 zERR DATA MIGRATION NOT ENABLED
Source:
NSS, Common Layer, Volume
Explanation:
NSS does not support data migration.
Possible Cause:
The user tried to invoke data migration on an NSS volume. The NetWare 5 release of NSS does not support data migration.
20805 zERR VOLUME STATE CHANGE A TO M
Source:
NSS, Common Layer, Volume
Explanation:
The volume state was changed from Active to Maintenance.
Possible Cause:
A problem was detected in the volume, and NSS changed the volume from the Active state to the Maintenance state.
Action:
Try dismounting and remounting the volume. If the error persists, try rebuilding or restoring the volume.
20806 zERR VOLUME NOT INT MAINT MODE
Source:
NSS, Common Layer, Volume
Explanation:
The volume specified is not in the Maintenance mode.
Possible Cause:
The user tried to verify or repair a volume that was not in the Maintenance state.
Action:
Do the following:
-
Make sure nothing is accessing the volume, and then try the request again.
-
Dismount and remount the volume.
-
Unload NSS, and load it again.
20807 zERR VOLUME STATE NOT SUPPORTED
Source:
NSS, Common Layer, Volume
Explanation:
The volume does not support the state change requested.
Possible Cause:
Some volumes, such as CD-ROM only support one state, so they do not handle any state changes.
Action:
Check the volume name and type, and make sure you can change its state.
Possible Cause:
An internal NSS error occurred.
Action:
Unload NSS, and load it again.
20808 zERR DUPLICATE VOLUME NAME
Source:
NSS, Common Layer, Volume
Explanation:
The volume name already exists.
Possible Cause:
The user tried to create or rename a volume using a name that is already being used by another volume.
Action:
Pick a different name for the volume.
WARNING:Not all volume name conflicts are caught immediately.
20809 zERR VOLUME SCHEDULED FOR MAINT
Source:
NSS, Common Layer, Volume
Explanation:
The volume is already scheduled for Maintenance.
Possible Cause:
The user tried to change a volume to the Maintenance mode when it is already in the Maintenance mode.
Action:
Make sure one operation on a volume is completed before beginning another.
20850 zERR NO SET PRIVILEGE
Source:
NSS, Common Layer, Authorization
Explanation:
An attempt was made to modify meta-data without the appropriate access rights.
Possible Cause:
The user does not have sufficient rights to make the change.
Action:
Change the access rights on the object being changed, or give the user more access rights.
Possible Cause:
An attempt was made to add space restrictions to a directory in NSS. Adding space restrictions to an NSS directory is not allowed.
Action:
Do not add space restrictions.
20851 zERR NO CREATE PRIVILEGE
Source:
NSS, Common Layer, Authorization
Explanation:
An attempt was made to create an object without the appropriate access rights.
Possible Cause:
The user does not have the create rights in the requested directory.
Action:
Give the user more rights or change the trustees of the directory.
Possible Cause:
The user tried to create a file or directory on a read-only volume. Creating files or directories on a CD-ROM or any read-only volume is not allowed.
Action:
Create the file or directory on a volume that can be written to.
20852 zERR INVALID AUTHORIZE SPACE
Source:
NSS, Common Layer, Authorization
Explanation:
The authorization space is invalid.
NSS uses the concept of authorization models and spaces. In future releases of NSS, it will be able to load different authorization models and spaces, such as a UNIX* authorization model. In NetWare 5, the authorization models and spaces are hard-coded into NSS.
Possible Cause:
This error is not currently used by NSS.
20853 zERR INVALID AUTHORIZE MODEL
Source:
NSS, Common Layer, Authorization
Explanation:
The authorization model is invalid.
NSS uses the concept of authorization models and spaces. In future releases of NSS, it will be able to load different authorization models and spaces, such as a UNIX authorization model. In NetWare 5, the authorization models and spaces are hard coded into NSS.
Possible Cause:
An internal programming error occurred.
Action:
Unload NSS, and load it again.
20854 zERR INVALID AUTHORIZE OPERATION
Source:
NSS, Common Layer, Authorization
Explanation:
An invalid operation was sent to an operation or function. When NSS has loadable authorization models, they will need to supply a set of well-defined functions or operations. If the model does not sent a valid operation, a default operation will be supplied and this error will be returned.
Possible Cause:
This error is not currently used by NSS.
20855 zERR AUTHORIZE LOAD FAILED
Source:
NSS, Common Layer, Authorization
Explanation:
NSS failed to load part of the authorization system.
Possible Cause:
This error is not currently used by NSS.
20856 zERR TRUSTEE NOT FOUND
Source:
NSS, Common Layer, Authorization
Severity:
Informational status error
Explanation:
NSS is unable to find the specified trustee ID.
Possible Cause:
This error is expected to be returned to the program when a trustee is not found.
NSS tried to find a trustee in the trustee list for this beast object (a trustee ID), but it was not found.
Action:
If this error occurs in the program you are using, contact a Novell Support Provider.
If programming, you could assign trustees to the beast object, but it is only necessary if different access rights are needed.
20857 zERR NO TRUSTEES FOUND
Source:
NSS, Common Layer, Authorization
Severity:
Informational status error
Explanation:
NSS is unable to find any trustees.
Possible Cause:
This error is expected to be returned to the program when a file or directory does not have any trustees, which is the case for most files and directories.
20858 zERR NO TRUSTEE CHANGE PRIVILEGE
Source:
NSS, Common Layer, Authorization
Explanation:
An attempt was made to change trustees without the appropriate access rights.
Possible Cause:
The user does not have the rights to change the trustees on the beast object (file, directory, or volume).
Action:
If appropriate, assign the user the rights needed.
Source:
NSS, Common Layer, Authorization
Explanation:
The user, represented by a NCP or a NLM program request, was denied access to a particular beast (file).
Possible Cause:
The user tried to open a file in a mode without sufficient rights. For example, if a user tried to open a file for writing that only allowed the user read access, this error would be returned.
Action:
If appropriate, assign the user the rights necessary to access the file.
20860 zERR NO WRITE PRIVILEGE
Source:
NSS, Common Layer, Authorization
Explanation:
A file or directory was opened in a mode that does not allow writing.
Possible Cause:
An attempt was made to write to a file or directory that had only been opened for read access.
Possible Cause:
An attempt was made to modify the meta-data of a file that the user only had read access to.
Action:
To modify a file, open the file for write access.
20861 zERR NO READ PRIVILEGE
Source:
NSS, Common Layer, Authorization
Explanation:
A file or directory was opened in a mode that does not allow reading.
Possible Cause:
An attempt was made to read a file or directory that was opened for write access only.
Action:
Open the file or directory for read/write access.
20862 zERR NO DELETE PRIVILEGE
Source:
NSS, Common Layer, Authorization
Explanation:
An attempt was made to delete data from media without the appropriate access rights.
Possible Cause:
The user does not have the necessary rights to delete the file.
Action:
If appropriate, assign the user the rights necessary to delete the file.
20863 zERR SOME NO DELETE PRIVILEGE
Source:
NSS, Common Layer, Authorization
Explanation:
If a user tries to delete multiple files using one request with a wildcard command in it, and the user does not have rights to delete some of the files, this error is returned.
Possible Cause:
This error is not currently used by NSS.
20864 zERR INVALID AUTH MODEL VERSION
Source:
NSS, Common Layer, Authorization
Explanation:
The version being registered is not correct.
Possible Cause:
An internal programming error occurred that was caused by an invalid authorization model version.
20865 zERR EXCEEDED MAX AUTH SPACES
Source:
NSS, Common Layer, Authorization
Explanation:
The maximum number of registered authorization spaces was exceeded.
Possible Cause:
An internal programming error occurred that exceeded the maximum number of authorization spaces.
20866 zERR EXCEEDED MAX AUTH MODELS
Source:
NSS, Common Layer, Authorization
Explanation:
The maximum number of registered authorization models was exceeded.
Possible Cause:
An internal programming error occurred that exceeded the maximum number of authorization models.
20867 zERR NO SUCH OBJECT
Source:
NSS, Common Layer, Authorization
Explanation:
The object specified does not exist in naming services.
Possible Cause:
eDirectory or NDS could not find the specified object.
Action:
Make sure that the object exists in eDirectory or NDS and that all replicas have been synchronized.
20868 zERR CANT DELETE OPEN FILE
Source:
NSS, Common Layer, Authorization
Explanation:
An attempt was made to delete an open file without the appropriate access rights.
Possible Cause:
A user tried to delete a file that is open, which is not allowed in the DOS semantics for files.
Action:
Close the file that needs to be deleted.
20869 zERR NO CREATE DELETE PRIVILEGE
Source:
NSS, Common Layer, Authorization
Explanation:
When creating a file that already exists, the user does not have rights to delete the existing file before recreating.
Possible Cause:
The user does not have sufficient rights to create a file that already exists.
Action:
If appropriate, change the rights on the file or give the user the appropriate rights.
20870 zERR NO SALVAGE PRIVILEGE
Source:
NSS, Common Layer, Authorization
Explanation:
An attempt was made to salvage a file without the appropriate rights.
Possible Cause:
The user does not have sufficient rights to salvage a file (recover a deleted file from deleted pool).
Action:
If appropriate, assign the user the applicable rights to salvage a file.
Source:
NSS, Common Layer, Locking-Related
Explanation:
An attempt was made to do a read/write to a locked range of a file.
Possible Cause:
Multiple users are accessing this file, and one of the users tried to read or write a portion of the file that was locked by another user.
Action:
Wait for the lock to be released.
Source:
NSS, Common Layer, Locking-Related
Explanation:
A general lock error occurred.
Possible Cause:
This error is not currently used by NSS.
20902 zERR LOCK COLLISION
Source:
NSS, Common Layer, Locking-Related
Explanation:
An attempt was made to lock a range that was already locked.
Possible Cause:
Multiple users are accessing this file, and one of the users tried to lock a portion of the file that was locked by another user.
Action:
Wait for the locks to be released.
Source:
NSS, Common Layer, Locking-Related
Explanation:
While waiting for a lock, the length of time to wait expired.
Possible Cause:
A user was waiting to acquire a lock but time ran out before the lock was granted.
Action:
Retry the lock, or find out who is holding the lock and not releasing it.
20904 zERR NONEXISTENT LOCK
Source:
NSS, Common Layer, Locking-Related
Explanation:
An attempt was made to release a lock that does not exist.
Possible Cause:
An attempt was made to unlock a byte range lock, and one of the following occurred:
-
An incorrect start and length for the lock was specified.
-
The lock had already been unlocked.
-
The lock had never been set.
-
The timer had expired on the lock before it was granted.
Action:
Make sure the code is releasing the correct lock.
20905 zERR FILE READ LOCKED
Source:
NSS, Common Layer, Locking-Related
Explanation:
An attempt to grant read access to the file failed.
Possible Cause:
A user requested read access, but at least one other user has requested exclusive access to the file.
Action:
You can use the console to search all the connections and find out which connections have the file open. Otherwise, wait until the other user closes the file.
20906 zERR FILE WRITE LOCKED
Source:
NSS, Common Layer, Locking-Related
Explanation:
An attempt to grant write access to the file failed.
Possible Cause:
Another user has exclusive access or read access to this file.
Action:
Wait until the other user closes the file.
20907 zERR CANT DENY READ LOCK
Source:
NSS, Common Layer, Locking-Related
Explanation:
An attempt to deny read access to the file failed.
Possible Cause:
Someone else is already accessing this file.
Action:
Wait until the other user closes the file.
20908 zERR CANT DENY WRITE LOCK
Source:
NSS, Common Layer, Locking-Related
Explanation:
An attempt to deny write access to the file failed.
Possible Cause:
Someone else is already accessing this file.
Action:
Wait until the other user closes the file.
20950 zERR UNICODE INVALID CONVERSION TYPE
Source:
NSS, Common Layer, Unicode
Explanation:
An attempt was made to convert a string to Unicode or Unicode to ASCII, but the type of the conversion was invalid,
Examples of invalid conversion types include converting case sensitive to case insensitive or changing path naming rules.
Possible Cause:
An NSS internal programming error occurred.
20951 zERR UNICODE CONVERSION ERROR
Source:
NSS, Common Layer, Unicode
Explanation:
A Unicode conversion error occurred.
Possible Cause:
One or more of the following problems could cause this error.
-
An unknown Unicode conversion error occurred.
-
The wrong code pages could be loaded on the machine.
-
The Unicode libraries are having a problem.
-
A bad string was passed to the Unicode libraries.
Action:
Check any strings that are being used as file or path names.
Source:
NSS, Common Layer, Unicode
Explanation:
An error occurred when an attempt was made to initialize the Unicode subsystem.
Possible Cause:
A resource limit was reached.
Action:
Reboot the server.
Possible Cause:
The wrong Unicode modules were loaded
Action:
Reload the Unicode NLM program.
20953 zERR UNICODE NON MAPPABLE CHAR
Source:
NSS, Common Layer, Unicode
Explanation:
A character that could not be mapped was encountered when converting the Unicode*.
Possible Cause:
The wrong code pages are on the server.
Action:
Make sure that all code pages needed are provided.
20954 zERR EXCEEDED MAX CONVERSION TYPES
Source:
NSS, Common Layer, Unicode
Explanation:
The number of registered conversion types exceeded the maximum number of loadable conversion types.
Possible Cause:
An attempt was made to register more Unicode conversion types than the built-in table had room for, due to an internal programming error in NSS.
21000 zERR INVALID LINK TYPE
Source:
NSS, Common Layer, Link
Explanation:
The specified link type is not supported.
Possible Cause:
A request was made for a link that is not supported by NSS. The current APIs cannot expose these features.
Action:
If this error occurs in the program you are running, contact a Novell Support Provider.
If you are programming an application, make sure the application requests a supported link type.
21001 zERR CANT HARD LINK DATA STREAMS
Source:
NSS, Common Layer, Link
Severity:
Informational status error
Explanation:
NSS is not allowed to create hard links to or from a dataStream.
Possible Cause:
This error is expected to be returned to the program when an attempt is made to link to a data stream. A data stream could be the resource link for the Macintosh name space.
21002 zERR CANT HARD LINK TO DIRECTORY
Source:
NSS, Common Layer, Link
Explanation:
NSS is not allowed to create hard links to a directory or container.
Possible Cause:
An attempt was made to create a hard link to a directory. If this were allowed, it could create cycles in the directory tree.
Action:
If this error occurs in a program you are running, contact a Novell Support Provider.
If you are programming, do not attempt to hard link to a directory. Soft links would work but are not supported in the NetWare 5 release of NSS.
21003 zERR MUST HARD LINK FROM DIRECTORY
Source:
NSS, Common Layer, Link
Explanation:
NSS is not allowed to create hard links from a non-directory or container.
Possible Cause:
Because a hard link creates a new name for the object, the destination must be a directory.
Action:
If this error occurs in a program you are running, contact a Novell Support Provider.
If you are programming, change the destination for the link to a directory.
21004 zERR CANT HARD LINK TO NON FILE
Source:
NSS, Common Layer, Link
Explanation:
NSS is not allowed to create hard links to beast object types (such as a data stream) not derived from a file.
Possible Cause:
In NSS released in NetWare 5, this is probably caused by an internal programming error.
Possible Cause:
An attempt was made to link to something, such as a data stream.
Action:
If you are programming, only link files into directories.
21005 zERR LINK DEST FILE ALREADY EXISTS
Source:
NSS, Common Layer, Link
Explanation:
The new name for the link already exists.
Possible Cause:
If a beast (file) with the requested name already exists in the destination directory, the link request cannot override the existing name.
Action:
If this error occurs in a program you are running, contact a Novell Support Provider.
If you are programming, delete the unwanted name in the destination directory and try the link again.
21050 zERR MODULE NAME ALREADY USED
Source:
NSS, Common Layer, NLM Registration
Explanation:
The specified NSS module name is already in use.
Possible Cause:
A module name conflicts with a module name NSS uses.
Action:
Unload the module that conflicts with NSS.
21051 zERR MODULE NAME NOT FOUND
Source:
NSS, Common Layer, NLM Registration
Explanation:
The specified NSS module name could not be found.
Possible Cause:
An attempt was made to load one of the modules that is part of NSS, but the module could not be found.
Action:
Make sure that all the NSS modules are in a directory that can be found from the search path.
21052 zERR INVALID MODULE VERSION
Source:
NSS, Common Layer, NLM Registration
Explanation:
The specified module has an invalid version number.
Possible Cause:
Modules from different versions of NSS are loaded on the server.
Action:
Make sure all the NSS modules are from the same release of NSS.
21053 zERR INCOMPATIBLE API VERSION
Source:
NSS, Common Layer, NLM Registration
Explanation:
The specified module has an incompatible API version number.
Possible Cause:
This error is not currently used by NSS.
21054 zERR INCOMPATIBLE DEBUG STATE
Source:
NSS, Common Layer, NLM Registration
Explanation:
The specified module has an incompatible debug version state.
Possible Cause:
Some of the NSS modules are debug versions and some are non-debug versions. Because of the state kept by the debug version of some routines, debug and non-debug NSS modules cannot be intermixed.
Action:
Get a released version of NSS that has been tested and released as product.
21055 zERR UNKNOWN MODULE TYPE
Source:
NSS, Common Layer, NLM Registration
Explanation:
The specified module has an unknown module type.
Possible Cause:
The type of the module is unknown to the current version of NSS.
Action:
Get a consistent set of NSS modules.
21056 zERR INVALID REGISTRATION TYPE
Source:
NSS, Common Layer, NLM Registration
Explanation:
The specified type is invalid for the item being registered.
Possible Cause:
An internal programming error occurred. In the beast structure, there is an area that is a variable length. Different subsystems can register for this area and supply the size for their variable section.
21057 zERR TYPE ALREADY REGISTERED
Source:
NSS, Common Layer, NLM Registration
Explanation:
The specified type is already registered.
Possible Cause:
An internal programming error occurred. A particular section of the variable beast data has already been claimed.
21215 zERR_ENABLE_ENCRYPTED_VOLUME_NOT_ENABLED
Source:
NSS, Common Layer, Encrypted Volume Support
Explanation:
An attempt was made to enable the Encrypted attribute for an existing nonencrypted volume.
Possible Cause:
One of the following problems could cause this error:
-
You can enable the Encryption attribute only at volume creation time.
-
The sys: volume cannot be encrypted, even at volume creation time.
Action:
To encrypt an existing volume, you must create a new encrypted volume, then migrate existing data from the nonencrypted volume to the encrypted volume.
22000 zERR INVALID OPENCREATE MODE
Source:
NSS, NW Semantic Agent Specific, Legacy
Explanation:
An invalid mode was sent to NCP 87 (create/open).
Possible Cause:
This error is not currently used by NSS.
22508 zERR ISO ASSOCIATED FILE
Source:
NSS, CD Specific
Explanation:
The error is returned as part of the unpack process. If the file ends up being a ISO associated type, this error is returned because this is a file type that should not be exposed to the user.
Possible Cause:
An internal error occurred.
Action:
If this error occurs in the program you are running, contact a Novell Support Provider.
If you are debugging the program, examine the LSS and correct the code.
22512 zERR ISO CANT CREATE BEAST
Source:
NSS, CD Specific
Explanation:
The BST_new failed in GetBeastFromVolume.
Possible Cause:
If an underlying error is returned, such as no memory, this error will probably not be sent. However, if no other error is returned in the errStatus field, this error is what would be returned.
22513 zERR ISO ZID NOT FOUND IN HASH
Source:
NSS, CD Specific
Explanation:
The ISO Z-ID was not found in the hash.
Possible Cause:
An unexpected and internal error to the LSS occurred.
Source:
NSS, ZFS Storage System Specific, B-tree
Explanation:
No node exists at the requested block location.
Possible Cause:
If corrupted data blocks that exist on the disk are found while NSS is attempting to verify or rebuild the file system, this error is returned.
Action:
If the file system did not get completely restored by the rebuild, restore the data from a backup.
24801 zERR BAD LOG RECORD
Source:
NSS, ZFS Storage System Specific, B-tree
Explanation:
A bad log record was found.
Possible Cause:
This error is not currently used by NSS.
Source:
NSS, ZFS Storage System Specific, B-tree
Explanation:
The beast (file system object) is too big to fit in the balanced tree (B-tree).
Possible Cause:
The size of the beast (file system object) is too big because it has too much variable data associated with it or there are too many names associated with this object. The particular object cannot be saved persistently, which will result in data corruption.
24803 zERR TREE LEAF CORRUPT
Source:
NSS, ZFS Storage System Specific, B-tree
Explanation:
A leaf object in an NSS B-tree is corrupted.
Possible Cause:
An internal programming error occurred.
Action:
Rebuild the affected NSS volume using the rebuild tool in the Utilities menu.
24820 zERR ZLOG BAD CHECKSUM
Source:
NSS, ZFS Storage System Specific, ZLOG
Explanation:
A zlog log record checksum error occurred.
Possible Cause:
Data corruption is on the disk. A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the file system.
24821 zERR ZLOG FILE TOO SMALL
Source:
NSS, ZFS Storage System Specific, ZLOG
Explanation:
The zlog file is too small.
Possible Cause:
The size of the NSS volume is too small, so there was not enough space to create a log for journaling the file system.
Action:
Create a larger NSS volume.
24822 zERR ZLOG BAD BLOCK SIGNATURE
Source:
NSS, ZFS Storage System Specific, ZLOG
Explanation:
The log block signature is invalid in the zlog file.
Possible Cause:
Data corruption is on the disk. A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the file system.
24823 zERR ZLOG BAD RECORD COUNT
Source:
NSS, ZFS Storage System Specific, ZLOG
Explanation:
The log record count for the log block is invalid in the zlog file.
Possible Cause:
Data corruption is on the disk. A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the file system.
24824 zERR ZLOG BAD RECORD SIZE
Source:
NSS, ZFS Storage System Specific, ZLOG
Explanation:
The record size for the zlog file is invalid.
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the file system.
Source:
NSS, ZFS Storage System Specific, ZLOG
Explanation:
The log record LSN is invalid in the zlog file.
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the file system.
24826 zERR ZLOG FILE INIT FAILED
Source:
NSS, ZFS Storage System Specific, ZLOG
Explanation:
ZLOG could not create the zlog file during a pool initialize command.
Possible Cause:
This error is not currently used by NSS.
24827 zERR ZLOG BAD BEAST SIGNATURE
Source:
NSS, ZFS Storage System Specific, ZLOG
Explanation:
The signature for the beast is invalid in the zlog file.
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the file system.
24828 zERR ZLOG UNSUPPORTED BEAST VERSION
Source:
NSS, ZFS Storage System Specific, ZLOG
Explanation:
The ZLOG code does not support the ZLOG beast version in persistent storage.
The ZLOG code and the ZLOG beast objects refer to the log file. NSS is a journaied file system. This means that NSS logs the changes to the meta-data of the system in a journal or log file. The zlog beast is this log file. The ZLOG code does a lot of checking to ensure the validity of the log file.
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the file system.
24829 zERR ZLOG UNSUPPORTED FILE VERSION
Source:
NSS, ZFS Storage System Specific, ZLOG
Explanation:
The ZLOG code does not support the zlog file version in persistent storage.
Action:
Do a clean shutdown with previous version of the nss.nlm, and then this error should go away. Otherwise, reset the volume.
WARNING:When resetting a volume, all the data on the volume will be lost and will need to be restored from a backup copy.
24830 zERR ZLOG FILE FULL
Source:
NSS, ZFS Storage System Specific, ZLOG
Explanation:
The ZLOG file is full. The file is too small for the transaction rate.
Possible Cause:
This error is not currently used by NSS.
24831 zERR ZLOG NO MORE RECORDS
Source:
NSS, ZFS Storage System Specific, ZLOG
Severity:
Informational status error
Explanation:
No more ZLOG recovery information exists. This is not a user error.
Possible Cause:
This error is expected to be returned to the program. It informs the recovery code to stop reading the log.
24840 zERR ZFSVOL BAD CHECKSUM
Source:
NSS, ZFS Storage System Specific, ZFSVOL Volume Data
Explanation:
A data checksum error for a ZFS volume occurred.
Possible Cause:
A hardware failure or media failure occurred.
Action:
Run verify on the volume, and if necessary run rebuild.
24850 zERR CHECKPOINT BAD CHECKSUM
Source:
NSS, ZFS Storage System Specific, Checkpoint
Explanation:
A Checkpoint checksum error occurred.
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the volume from a backup.
24851 zERR CHECKPOINT BAD BLOCK SIGNATURE
Source:
NSS, ZFS Storage System Specific, Checkpoint
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the volume from a backup.
24852 zERR CHECKPOINT BAD BLOCK SIZE
Source:
NSS, ZFS Storage System Specific, Checkpoint
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the volume from a backup.
24853 zERR CHECKPOINT UNSUPPORTED VERSION
Source:
NSS, ZFS Storage System Specific, Checkpoint
Explanation:
The Checkpoint code does not support the version in the checkpoint.
Possible Cause:
A newer version of NSS that is not backward compatible has been put on the server. The log file was created with an older version.
Action:
If the error persists, restore the file system from a backup.
24860 zERR SUPERBLOCK BAD CHECKSUM
Source:
NSS, ZFS Storage System Specific, Superblock
Explanation:
A superblock checksum error occurred.
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the volume from a backup.
24861 zERR SUPERBLOCK BAD BLOCK SIGNATURE
Source:
NSS, ZFS Storage System Specific, Superblock
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the volume from a backup.
24862 zERR SUPERBLOCK BAD BLOCK SIZE
Source:
NSS, ZFS Storage System Specific, Superblock
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the volume from a backup.
24863 zERR SUPERBLOCK UNSUPPORTED VERSION
Source:
NSS, ZFS Storage System Specific, Superblock
Explanation:
The superblock code does not support the version in the superblock header.
Possible Cause:
A newer version of NSS that is not backward compatible has been put on the server.
Action:
Restore all the data on NSS volumes from backup copies.
24864 zERR SUPERBLOCK UNSUPPORTED MEDIA
Source:
NSS, ZFS Storage System Specific, Superblock
Explanation:
The version of the media specified is not supported.
Possible Cause:
A newer version of NSS that is not backward compatible has been put on the server. The layout of the disk format has changed in the newer version.
Action:
Restore all the data on NSS volumes from backup copies.
24865 zERR SUPERBLOCK MISMATCH
Source:
NSS, ZFS Storage System Specific, Superblock
Explanation:
Two or more valid superblock headers do not match each other.
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the volume from a backup.
24866 zERR SUPERBLOCK UNDESIRED LOCATION
Source:
NSS, ZFS Storage System Specific, Superblock
Explanation:
A superblock is not in desired mathematical location.
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the volume from a backup.
24867 zERR SUPERBLOCK NOT ENOUGH
Source:
NSS, ZFS Storage System Specific, Superblock
Explanation:
Not enough valid superblock headers exist.
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the volume from a backup.
24868 zERR SUPERBLOCK CORRUPTED
Source:
NSS, ZFS Storage System Specific, Superblock
Explanation:
A valid superblock header has invalid information in it.
Possible Cause:
A hardware or media failure occurred.
Action:
Try rebuilding the volume. If the error persists, restore the volume from a backup.
24880 zERR RECOVERY TOO MANY UNCOMMITS
Source:
NSS, ZFS Storage System Specific, Recovery
Explanation:
The recovery could not uncommit all transactions that it needed to before it reached the last Checkpoint.
Possible Cause:
The file system was in an unstable state.
Action:
If the error persists, restore the file system from a backup.
24999 zERR GENERIC NSS ERROR
Source:
NSS, ZFS Storage System Specific, Generic Error for FSHooks