72.0 TSA600 Messages

The TSA6OO messages include messages from the NetWare 3.12, 3.2, 4.0, 4.1, 4.11, and 5.0 releases that are still being used.

TSA6OO-X-1: The bindery cannot be opened. Error code: code.

Source: TSA6OO.NLM
Explanation: After backup or restore, the bindery must be opened; however, it cannot be opened.
Action: Make sure the user has Supervisor or equivalent user access rights. Make sure the correct volume is in use. Make sure volume Sys is mounted. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-2: The bindery cannot be closed. Error code: code.

Source: TSA6OO.NLM
Explanation: Before backup or restore, the bindery must be closed; however, it cannot be closed.
Action: Make sure the user has Supervisor or equivalent user access rights. Make sure the correct volume is in use. Make sure volume Sys is mounted. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-3: The bindery cannot be closed because you are not a Supervisor.

Source: TSA6OO.NLM
Explanation: Before backup or restore, the bindery must be closed; however, it cannot be closed.
Action: Make sure the user has Supervisor or equivalent user access rights.

TSA6OO-X-10: The data stream format for name is incorrect. Error code: code.

Source: TSA6OO.NLM
Explanation: The media cannot be read.
Possible Cause: The backup device has a problem.
Action: Make sure the backup device is functioning properly. If it is, make sure that your media is SMS-compatible. Try again. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-41: An internal error has occurred. The program cannot push directory name.

Source: TSA6OO.NLM
Explanation: The program could not add the directory to a list.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. Verify the number of open files and directories. Make sure the user has appropriate user access rights.

TSA6OO-X-42: This program cannot get the name space entry name for data_set_name in the type name space.

Source: TSA6OO.NLM
Explanation: The program could not find the file or directory name in the requested name space.
Action: Make sure the indicated name space type is valid and that it is supported on the target volume. Make sure the data set name is valid for the specified name space. Make sure the name space support NLM programs are loaded.

TSA6OO-X-43: Error code getting name space specific information size for data_set_name in the name_space name space.

Source: TSA6OO.NLM
Explanation: The program could not read the name-space-specific information for the file or directory.
Action: Do the following:

  1. Make sure the indicated name space type is valid and supported on the target volume.

  2. Make sure the data set name is valid for the specified name space.

  3. Make sure the name space support NLM programs are loaded. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-45: Error code occurred during the program’s attempt to get the entry index for data_set.

Source: TSA6OO.NLM
Explanation: The program could not get the file system entry index for the requested file or directory.
Action: Make sure the indicated name space type is valid and supported on the target volume.
Action: Make sure the data set name is valid for the specified name space. Make sure the name space support NLM programs are loaded.
Action: Make sure the user has appropriate user access rights. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-46: Error code occurred when the program attempted to read extended attributes for data_set.

Source: TSA6OO.NLM
Explanation: The program could not read the extended attributes for the requested file or directory.
Action: Make sure the indicated name space type is valid and supported on the target volume.
Action: Make sure the data set name is valid for the specified name space. Make sure that name space support NLM programs are loaded.
Action: Make sure the user has appropriate user access rights. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-47: The original access date for file name cannot be reset. The access date will be changed to today’s date.

Source: TSA6OO.NLM
Explanation: This is a informational message indicating that the TSA6OO.NLM could not reset the access date for the file or directory. The file system will show the current time as the last access time. This error will affect future file system searches based on access date.

TSA6OO-X-48: Invalid data (an unexpected bindery trailer) was found.

Source: TSA6OO.NLM
Explanation: TSA6OO received an unexpected data object (a bindery trailer) from the SMS engine. This object was out of sequence or was redundant.
Possible Cause: The media or storage device is malfunctioning.
Action: Make sure the media and storage devices are operating properly.

TSA6OO-X-49: This program cannot create directory name. Error code: code.

Source: TSA6OO.NLM
Explanation: TSA6OO cannot create the requested directory.
Action: Make sure a valid path (including volume name) is specified.
Action: Make sure the user has appropriate user access rights.
Action: Make sure the volume has enough disk space. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-51: Invalid data (no data stream trailer) was found for data_stream_name.

Source: TSA6OO.NLM
Explanation: TSA6OO received an unexpected data sequence from the SMS engine (a missing data stream trailer). End of data stream is assumed.
Possible Cause: The media or storage device is malfunctioning.
Action: Make sure the media and storage devices are operating properly.

TSA6OO-X-52: Invalid data (an unexpected directory trailer) was found.

Source: TSA6OO.NLM
Explanation: TSA6OO received an unexpected data object (a bindery trailer) from the SMS engine. This object was out of sequence or was redundant.
Possible Cause: The media or storage device is malfunctioning.
Action: Make sure the media and storage devices are operating properly.

TSA6OO-X-53: This program cannot allocate a directory handle for directory_name.

Source: TSA6OO.NLM
Explanation: The program could not allocate a directory handle to the requested directory.
Action: Make sure the directory name is valid for the specified name space.
Action: Make sure a valid path (including volume name) is specified.
Action: Make sure the user has appropriate user access rights. Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

TSA6OO-X-54: File name was restored but could not be closed. Error code code was returned. The file may be corrupted.

Source: TSA6OO.NLM
Explanation: The open file could not be closed. (The error code might give more specific information.) Because the file could not be closed, it might not be complete on the disk.
Action: Verify the file contents.
Action: Make sure the user has appropriate user access rights.
Action: Make sure the file is not in exclusive use by another process. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-55: File name cannot be created. Error code: code.

Source: TSA6OO.NLM
Explanation: The requested file cannot be created.
Action: Make sure the filename is valid for the requested name space.
Action: Make sure the user has appropriate user access rights. Verify the number of currently open files.
Action: Make sure a valid path (including volume name) is specified.
Action: Make sure the volume has enough disk space. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-56: File name cannot be replaced.

Source: TSA6OO.NLM
Explanation: The specified file exists but could not be opened for overwrite.
Action: Make sure the user has appropriate user access rights.
Action: Make sure the file is not in exclusive use by another process.

TSA6OO-X-57: Invalid data (an unexpected file trailer) was found.

Source: TSA6OO.NLM
Explanation: The program received a file trailer record before the complete file had been received. The file could be truncated or corrupted.
Action: Verify the file’s contents. Check the backup log for an error on this file.
Action: Make sure the media and storage devices are operating properly.

TSA6OO-X-58: This program cannot write file name. Error code: code.

Source: TSA6OO.NLM
Explanation: An error occurred when the program attempted to write the file.
Action: Make sure the user has appropriate user access rights.
Action: Make sure the volume has not been dismounted. Make sure the file is not in exclusive use by another process. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-59: An internal error has occurred. This program cannot get the field for field_name. Error code: code.

Source: TSA6OO.NLM
Explanation: TSA6OO encountered an error while attempting to read the next data field to process.
Action: Contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-60: Trustee name cannot be added to file/directory_name. Error code: code.

Source: TSA6OO.NLM
Explanation: The requested Trustee cannot be added to the specified file or directory.
Action: If this is the case, do the following:

  1. Make sure the Trustee name is a valid eDirectory object.

  2. Make sure the file exists and the filename is valid for the specified name space type.

  3. Make sure the file or directory exists and is valid in the specified name space.

  4. Make sure the user has appropriate user access rights.

For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-61: File name may be corrupted. An invalid CRC was received.

Source: TSA6OO.NLM
Explanation: The cyclic redundancy check (CRC) calculated on the file data does not match the CRC value calculated at the time of backup and stored on the media.
Possible Cause: The file might be corrupted.
Action: Make sure the file contents are not corrupted.
Possible Cause: The media or storage device might be malfunctioning.
Action: Make sure the media and storage devices are operating properly.

TSA6OO-X-62: Corrupted data was found after data_set_name.

Source: TSA6OO.NLM
Explanation: The program still has data for the file or directory after a valid trailer record was processed because the file did not restore well.
Action: Try restoring the file again. If the error continues, the data set might be corrupted.
Action: Make sure the media and storage devices are operating properly.

TSA6OO-X-63: The data set type is invalid.

Source: TSA6OO.NLM
Explanation: TSA6OO received an unknown data set type identifier. This data set will not be processed.
Action: Make sure the media and storage devices are operating properly.

TSA6OO-X-64: An invalid data marker was found. File name may be corrupted.

Source: TSA6OO.NLM
Explanation: An invalid data stream was found following a valid data stream trailer record.
Action: Verify the contents of the file or directory.
Action: Make sure the media and storage devices are operating properly.

TSA6OO-X-65: The extended attributes format for data_set_name is invalid. Error code: code.

Source: TSA6OO.NLM
Explanation: The extended attribute format for the file or directory is in an invalid sequence. The extended attributes might not be correct.
Action: Verify the extended attributes for the data set. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-66: An invalid path data_set_path was specified. A full path is required.

Source: TSA6OO.NLM
Explanation: The data set path could not be located or was incomplete.
Action: Make sure the data set path is valid for the specified name space type. A full path requires a path from the server volume.

TSA6OO-X-67: An invalid path was specified. The volume does not exist: name.

Source: TSA6OO.NLM
Explanation: The specified path contains a nonexistent volume.
Action: Make sure the volume name is correct and that it includes a colon after the volume name.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-68: The program cannot set directory characteristics for directory_name.

Source: TSA6OO.NLM
Explanation: The program could not set the directory attributes for the directory.
Action: Make sure the user has appropriate user access rights.
Action: Make sure the directory attributes are valid.
Action: Make sure to use a valid directory name for a directory that exists.

TSA6OO-X-69: The program cannot set file characteristics for filename. Error code: code.

Source: TSA6OO.NLM
Explanation: The program cannot set the requested file attributes on the specified file.
Action: Make sure the file attributes requested are valid and the file exists.
Action: Make sure the user has appropriate user access rights.
Action: Make sure the filename is valid for the specified name space type. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-70: The Macintosh name space is not supported. This information will not be restored.

Source: TSA6OO.NLM
Explanation: The Macintosh name space is not supported on the target volume, so Macintosh-specific information will not be restored.
Action: If Macintosh information is desired, do one of the following:

  • Stop the restore, enable Macintosh support for the target volume, and load Macintosh name space support modules.

  • Restore to a volume in which Macintosh name space is supported.

TSA6OO-X-71: Beginning and ending FIDs for data_set_name do not match.

Source: TSA6OO.NLM
Explanation: The closing FID for the file or directory does not match the opening FID.
Possible Cause: The data set might be corrupted.
Action: Check your hardware devices and retry the data set. If the same errors occurs, the data is probably unrecognizable.

TSA6OO-X-72: Invalid data (an unexpected volume trailer) was found.

Source: TSA6OO.NLM
Explanation: TSA6OO read a volume trailer record before the end of the current data set.
Possible Cause: The data set might be corrupted.
Action: Check your hardware devices and retry the data set. If the same errors occurs, the data is probably unrecognizable.

TSA6OO-X-73: User name (ID number) cannot be added to volume name. Error code: code.

Source: TSA6OO.NLM
Explanation: The requested user cannot be added as a user because of space restrictions on the volume.
Action: Make sure the volume exists and the user has proper user access rights.
Action: Make sure the user is a valid eDirectory object. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-74: An internal error has occurred. Some trustees may not be restored for data_set_name.

Source: TSA6OO.NLM
Explanation: Trustee information expected next in the data stream was not found.
Action: Make sure the correct trustees were restored for the data set. If not, correct the trustee list as necessary.

TSA6OO-X-75: Trustee name was not restored for data_set_name, because the trustee IDs are different.

Source: TSA6OO.NLM
Possible Cause: This error might happen when the same username exists on two different servers or when the users have different directory IDs.
Action: At the end of the restore session, set the appropriate trustee information using ConsoleOne.

TSA6OO-X-76: The volume restrictions data set format for data_set_name is invalid. Error code: code.

Source: TSA6OO.NLM
Explanation: TSA6OO found the volume restrictions name and the ID to be out of sequence in the data stream. Processing will continue.
Action: At the end of the restore session, verify the volume restrictions are correct. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-77: The trustee data set format for object_name is invalid. Error code: code.

Source: TSA6OO.NLM
Explanation: TSA6OO found the trustee name and the ID to be out of sequence in the data stream. Processing will continue.
Action: At the end of the restore session, verify the trustee information is correct. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-78: An internal error has occurred. Volume restrictions cannot be found for data_set_name.

Source: TSA6OO.NLM
Explanation: TSA6OO expected Volume Restrictions to be next in the data stream, but did not find them. Processing will continue.
Action: At the end of the restore session, verify the volume restrictions are correct.
Action: Make sure that the user is using a valid volume name and has proper access rights.

TSA6OO-X-79: The extended attributes for file name were not restored. Error code: code.

Source: TSA6OO.NLM
Explanation: The extended attributes were not restored.
Action: For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-80: Invalid data stream name name was found for file name.

Source: TSA6OO.NLM
Explanation: An unknown or unsupported data stream (file or directory) header name was found. This data stream will not be restored.
Action: Make sure the file has been restored correctly and the correct number of data streams was restored.

TSA6OO-X-81: Data set data_set_name may be corrupted. An invalid CRC was received.

Source: TSA6OO.NLM
Explanation: The cyclic redundancy check (CRC) in the data stream is invalid.
Possible Cause: The data might not be valid.
Action: Try again. If the error continues, check the file or directory for internal errors.

TSA6OO-X-88: The NFS name space is not supported. This information will not be restored.

Source: TSA6OO.NLM
Explanation: This file or directory contains information specific to NFS that will not be restored.
Action: If NFS information is required, restore to a volume with NFS support or load NFS support on the selected volume. If the NFS information is not needed, continue the restore session.

TSA6OO-X-89: The full paths data set format is invalid. Error code: code.

Source: TSA6OO.NLM
Explanation: An invalid full path was detected by TSA6OO.
Action: Make sure the full path is specified; it must contain volume, directory, filename, and file separators for the specified name space. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-90: The type name space is not supported.

Source: TSA6OO.NLM
Explanation: The specified name space type is invalid, or not supported on this volume.
Action: Specify a valid name space type. If necessary, load name space support for the specified volume.

TSA6OO-X-91: Error code occurred while the program attempted to set the type name space name for data_set_name.

Source: TSA6OO.NLM
Explanation: TSA6OO could not set the name space name for the indicated name space type.
Action: Make sure the name space name and name space type are valid. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-92: Error code occurred while the program was scanning for extended attributes for data_set_name.

Source: TSA6OO.NLM
Explanation: An error occurred when the program attempted to read the extended attributes (EA) for the indicated file or directory. The extended attributes will not be backed up for this data set.
Action: Make sure the user is using a valid data set name.
Action: Make sure the user has appropriate user access rights.
Action: Make sure the extended attributes are not corrupted. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-93: A buffer underflow occurred during the program’s attempt to get the extended attribute value for data_set_name. Error code: code.

Source: TSA6OO.NLM
Explanation: TSA6OO received an end-of-data error before the correct number of bytes was read.
Action: Make sure the extended attributes and the data set’s data are not corrupted. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-94: Error code occurred while the program attempted to scan information that is specific to the name_space_name name space of data_set_name.

Source: TSA6OO.NLM
Explanation: The name-space-specific information for the indicated data set cannot be read.
Action: Make sure the specified name space support modules are loaded and volume support for the name space is enabled.
Action: Make sure the user is using a valid data set name.
Action: Make sure the user has appropriate user access rights. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-95: An NFS hard link collision occurred while restoring data_set_name. The hard links cannot be restored.

Source: TSA6OO.NLM
Explanation: NFS hard links for the file or directory conflict with existing hard links. The restore session cannot be completed.
Action: Exit and try the operation again.

TSA6OO-X-96: An error occurred while the program attempted to restore name-space-specific information for data_set_name in the data_set_name name space. Error code: code.

Source: TSA6OO.NLM
Explanation: Name space information for the file or directory cannot be restored.
Action: Make sure the specified name space type is supported on the target volume.
Action: Make sure the user has appropriate user access rights. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-108: Directory entry information for data_set_name cannot be scanned.

Source: TSA6OO.NLM
Explanation: The program could not scan the directory for the indicated data set.
Action: Make sure a valid path (including volume name) is specified.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-109: An internal error has occurred: buffer state problem number number.

Source: TSA6OO.NLM
Explanation: An internal error has occurred in the data buffer. Processing will continue; however, the data might be corrupted.
Action: Repeat the session to make sure the data is not corrupted.

TSA6OO-X-110: This program cannot delete existing extended attributes for data_set_name. Error code: code.

Source: TSA6OO.NLM
Explanation: The program cannot delete the extended attributes for the indicated data set.
Action: Make sure the user has appropriate user access rights.
Action: Make sure the file is not in exclusive use by another process. After the restore session, check the integrity of the extended attributes and correct or change them if necessary. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-111: The TSA and responder versions are incompatible.

Source: TSA6OO.NLM
Possible Cause: The SMS modules are from incompatible versions.
Action: Replace SMS modules as necessary to obtain compatible versions.

TSA6OO-X-135: Extended Attributes are not supported in this version of NetWare. Information will be lost!

Source: TSA6OO.NLM
Explanation: The program is unable to set or get extended attributes.
Action: Make sure that support for extended attributes is available for the file system in this version of NetWare. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-137: Open Data Stream failed for code on dataStream code error error number. This stream will not be restored.

Source: TSA6OO.NLM
Explanation: The data stream cannot be opened for restoring data.
Action: Make sure there is sufficient disk space.
Action: Make sure the data set is not currently being used by another application. If it is, close the other application.

TSA6OO-X-152: code is currently in use. Unloading now may result in an ABEND!

Source: TSA6OO.NLM
Possible Cause: An active connection exists between this program and another application. This program cannot be loaded now.
Action: Close all active applications and try unloading this program. For information about a specific error code, search the Error Codes online documentation.

TSA6OO-X-153: Delete existing trustees before restoring.

Source: TSA6OO.NLM
Explanation: The existing trustee information will be overwritten.
Action: This message is for information only.

TSA6OO-X-158: File filename has a compressed size of zero (0). This indicates an error with the file and it cannot be read.

Source: TSA6OO.NLM
Explanation: The size of the compressed file is 0. Either the file contains no data or the file is corrupted.
Action: Check the integrity of the file. Retry the operation.

TSA6OO-X-169: File open failed for filename in Server Specific Info object, error error no. It will not be backed up.

Source: TSA6OO.NLM
Explanation: The corresponding file containing server specific information cannot be backed up.
Action: Make sure there is sufficient disk space. Retry the operation.

TSA6OO-X-178: Trustee name was not restored for object, because the name doesn’t exist in NDS.

Source: TSA6OO.NLM
Explanation: This is an informational message that indicates that the trustee name no longer exists in eDirectory because it was either removed or deleted; it cannot be restored.

TSA6OO-X-179: Trustee name was not restored for object, because no NDS name is available for this ID.

Source: TSA6OO.NLM
Explanation: This is a informational message that indicates that the trustee name no longer exists in eDirectory because it was either removed or deleted; it cannot be restored.

TSA6OO-X-180: The file filename contains invalid characters. The file was skipped. The file name is a hexidecimal representation of the string.

Source: TSA6OO.NLM
Explanation: The file name contains characters that are not recognized. An equivalent hexadecimal representation of the file name will be backed up.
Action: Make sure the file naming conventions are consistent with NetWare.

TSA6OO-X-256: Access has been denied. An invalid username or authentication was used.

Source: TSA6OO.NLM
Explanation: An invalid authentication has occurred.
Action: Try again. Make sure the username and password are correct.

TSA6OO-X-257: This program cannot get the Directory object name.

Source: TSA6OO.NLM
Explanation: The name specified is not a valid or known name.
Action: Verify the name; then try again.

TSA6OO-X-258: This program has encountered a buffer underflow and cannot get the entire field.

Source: TSA6OO.NLM
Explanation: TSA6OO received an end-of-data error before the correct number of bytes were read.
Possible Cause: The data might be corrupted.
Action: Make sure the data is correct. Repeat the session if necessary.

TSA6OO-X-259: This program cannot allocate a directory handle.

Source: TSA6OO.NLM
Explanation: The program could not allocate a directory handle.
Action: Make sure the user has specified a valid directory path for the desired name space.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-260: The bindery cannot be closed.

Source: TSA6OO.NLM
Explanation: The bindery cannot be closed.
Action: Make sure the user has Supervisor rights to the server.
Action: Make sure the bindery is not being used.

TSA6OO-X-261: This program cannot create a directory entry.

Source: TSA6OO.NLM
Explanation: The program could not create the specified directory entry.
Action: Make sure the user has specified a valid directory path for the name space.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-262: This program cannot create a file.

Source: TSA6OO.NLM
Explanation: The program could not create the specified file.
Action: Make sure the user has specified a valid directory path for the name space.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-263: This data set name is already in use.

Source: TSA6OO.NLM
Explanation: TSA6OO cannot overwrite the existing data set because the data set is being used.
Action: Change the SBACKUP selection to Overwrite parent/child, or change the destination path.

TSA6OO-X-264: The data set was excluded by the selection list.

Source: TSA6OO.NLM
Explanation: The specified file or directory was excluded by the selection criteria.
Action: Change the selection criteria in SBACKUP.

TSA6OO-X-265: This file is flagged Execute Only and cannot be opened.

Source: TSA6OO.NLM
Explanation: The specified file cannot be opened for read or write because its attribute is set to Execute Only.
Action: Change the attributes to Normal to allow the specified file to be backed up or restored.

TSA6OO-X-266: This data set is in use and cannot be accessed at this time.

Source: TSA6OO.NLM
Explanation: The specified file is currently in use by another application and cannot be accessed.
Action: Make sure the file is not in use by any application. If it is, close the application.

TSA6OO-X-267: The target data set is newer than the one on the media. The data set will not be restored.

Source: TSA6OO.NLM
Explanation: The specified file on the target server is newer than the one that is available on the media. The file will not be overwritten.
Action: If the older file will replace the newer file, set the Overwrite Existing Parent & Child option to Yes.

TSA6OO-X-268: A data set is already open. You cannot open a data set or alter a scan when a data set is open.

Source: TSA6OO.NLM
Explanation: The specified file is already open and cannot be accessed now.
Action: Make sure the specified file is not in use by any application. If it is, close the application.

TSA6OO-X-270: This program cannot delete a data set.

Source: TSA6OO.NLM
Explanation: The specified data set could not be deleted.
Action: Make sure a valid data set name was specified.
Action: Make sure the user has appropriate user access rights.
Action: Make sure the file is not in exclusive use by another process.

TSA6OO-X-271: The program was processing a record or subrecord and did not find the Header field.

Source: TSA6OO.NLM
Explanation: The data has been corrupted. The header field is missing.
Action: Clean the tape heads and check the hardware. Retry the operation. If the problem persists, contact your Novell support provider.

TSA6OO-X-272: The program was processing a record or subrecord and did not find the Trailer field.

Source: TSA6OO.NLM
Explanation: The data has been corrupted. The trailer field of a record is missing.
Action: Clean the tape heads and check the hardware; then try again. If the problem persists, contact a Novell support provider.

TSA6OO-X-273: This program cannot get the Directory object name.

Source: TSA6OO.NLM
Explanation: The specified object was not found in the bindery.
Action: Make sure a valid bindery object was specified.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-274: This program cannot get the data stream name.

Source: TSA6OO.NLM
Explanation: The program could not read the requested data stream name.
Action: Make sure a valid data set name for the name space was specified.
Action: Make sure name space is supported on the volume.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-275: This program cannot get the entry index.

Source: TSA6OO.NLM
Explanation: The program could not get an entry index for the requested file or directory.
Action: Make sure a valid data set name for the name space was specified.
Action: Make sure name space is supported on the volume.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-276: This program cannot get the name space entry name.

Source: TSA6OO.NLM
Explanation: The program could not read the name space entry name for the requested file or directory.
Action: Make sure a valid data set name for the name space was specified.
Action: Make sure name space is supported on the volume.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-277: This program cannot get the name space size information.

Source: TSA6OO.NLM
Explanation: The program could not read the name space information size.
Action: Make a valid data set name for the name space was specified.
Action: Make sure name space is supported on the volume.

TSA6OO-X-278: This program cannot get the NetWare server information.

Source: TSA6OO.NLM
Explanation: TSA6OO could not read the server information.
Action: Make sure the server’s NetWare operating system version matches the TSA6OO version in use.

TSA6OO-X-279: This program cannot get the volume-supported name space information.

Source: TSA6OO.NLM
Explanation: The program could not read the list of supported name spaces for the requested volume.
Action: Make sure a valid volume name was specified.
Action: Make sure the volume is mounted. Make sure the user has appropriate user access rights.

TSA6OO-X-280: An invalid connection handle was passed.

Source: TSA6OO.NLM
Explanation: Your connection might no longer be valid.
Action: Make sure the workstation is connected to the network.

TSA6OO-X-281: Invalid data set data was found.

Source: TSA6OO.NLM
Explanation: The data set is corrupted.
Action: Check the integrity of the file. Retry the operation.

TSA6OO-X-282: The data set handle is invalid.

Source: TSA6OO.NLM
Explanation: The data set might not exist.
Action: Verify the data set exists.

TSA6OO-X-283: The data set name is invalid.

Source: TSA6OO.NLM
Explanation: An invalid file or directory name was specified.
Action: Specify a valid data set name for the specified name space.

TSA6OO-X-284: An invalid data stream was found for data_set_name, data set type type.

Source: TSA6OO.NLM
Explanation: The data stream specified is invalid for the indicated data set and type.
Action: Specify a valid data stream type.
Action: Make sure the requested name space is supported on this volume.

TSA6OO-X-285: The handle tag is invalid or the pointer is null.

Source: TSA6OO.NLM
Explanation: This handle is not valid. This message is for information only.

TSA6OO-X-286: Message number is invalid.

Source: TSA6OO.NLM
Explanation: An invalid message number was detected. This message is for information only.

TSA6OO-X-287: The name space type does not exist or is invalid.

Source: TSA6OO.NLM
Explanation: An invalid name space type was specified.
Action: Specify a valid name space type, and make sure support for the specified name space type is loaded on the specified volume.

TSA6OO-X-288: The object ID or name that was backed up does not match the current object ID or name.

Source: TSA6OO.NLM
Explanation: The object ID or name for the restore does not match the object ID or name for the backup. Restore is probably being performed on a different server from the server that was used for the backup. This results in an object on both servers with a different ID. This message is for information only.

TSA6OO-X-289: The Open mode option is out of range (less than 0 or greater than 23).

Source: TSA6OO.NLM
Explanation: An invalid open mode option was specified.
Action: Specify a range within allowable parameters.

TSA6OO-X-290: One or more of the parameters is null or invalid.

Source: TSA6OO.NLM
Explanation: Invalid parameters were specified.
Action: Replace any null or invalid parameters.

TSA6OO-X-291: An invalid path was used.

Source: TSA6OO.NLM
Explanation: The path is invalid for the specified name space.
Action: Make sure the path is valid for the specified name space.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-292: The scan type is out of range (less than 0 or greater than 31).

Source: TSA6OO.NLM
Explanation: An invalid scan type was specified.
Action: Correct the scan type and try again.

TSA6OO-X-293: An invalid select list entry was passed.

Source: TSA6OO.NLM
Explanation: The corresponding selection list entry is not supported by this TSA version.
Action: Check the documentation for a valid list of selection list entries.

TSA6OO-X-294: The selection type is out of range (less than 0 or greater than 31).

Source: TSA6OO.NLM
Explanation: An invalid selection type was specified.
Action: Correct the selection type and try again.

TSA6OO-X-295: The sequence number is invalid.

Source: TSA6OO.NLM
Explanation: An invalid sequence number was specified.
Action: Correct the sequence number and try again.

TSA6OO-X-296: This login attempt has been denied.

Source: TSA6OO.NLM
Explanation: The login attempt failed.
Action: Make sure a valid username and password for the selected server is specified; then try again.

TSA6OO-X-297: This logout attempt cannot be completed.

Source: TSA6OO.NLM
Explanation: The logout attempt failed.
Action: Make sure no work is in progress; then try again.

TSA6OO-X-298: The name space path has not been updated.

Source: TSA6OO.NLM
Explanation: A valid path was not found in the path list for the selected name space.
Action: Make sure a valid DOS path exists; then try again.

TSA6OO-X-300: The connection is invalid or does not exist.

Source: TSA6OO.NLM
Explanation: The old connection is invalid or no connection has been established.
Action: Re-establish the connection and proceed.

TSA6OO-X-302: There are no more data sets to be scanned.

Source: TSA6OO.NLM
Explanation: There are no more data sets available on the target server.
Action: Proceed with scanning a new data set.

TSA6OO-X-303: Either no more entries are in the list or the name space type does not exist.

Source: TSA6OO.NLM
Explanation: This message is for information only.

TSA6OO-X-304: You do not have the Search right on client service.

Source: TSA6OO.NLM
Explanation: TSA6OO could not scan the client file system because of a rights violation.
Action: Try one or more of the following:

  • Change to another server or volume where you have the Search right.

  • Log in as another user who does have the Search right.

  • Make sure the user has appropriate user access rights.

TSA6OO-X-305: No such property exists.

Source: TSA6OO.NLM
Explanation: An invalid property was specified.
Action: Make sure the property you want is valid; then try again.

TSA6OO-X-306: A data stream cannot be opened.

Source: TSA6OO.NLM
Explanation: The program cannot open the specified data stream.
Action: Make sure that you are using a valid data stream name and the data stream exists.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-307: A file cannot be opened.

Source: TSA6OO.NLM
Explanation: The program cannot open the specified file.
Action: Make sure that you are using a valid filename and the file exists.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-308: The Open option is not used.

Source: TSA6OO.NLM
Explanation: The Open option mode type string is not being used.
Explanation: This message is for information only.
Action: However, you might want to add the mode type string (for example, NO_DATA_STREAMS_STR).

TSA6OO-X-309: A file or directory cannot be restored. You are out of disk space.

Source: TSA6OO.NLM
Explanation: Restore cannot continue until the user adds more disk space.
Action: Do one or both of the following:

TSA6OO-X-310: Either the server is out of memory or memory allocation failed.

Source: TSA6OO.NLM
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

TSA6OO-X-311: A UINT64 value has overflowed.

Source: TSA6OO.NLM
Explanation: A number overflow has occurred. The number is too large for the UINT64 type variable.
Possible Cause: Invalid or corrupted data exists.
Action: Contact a Novell support provider.

TSA6OO-X-312: The extended attributes cannot be read.

Source: TSA6OO.NLM
Explanation: The extended attributes for a file cannot be read.
Action: Make sure a valid file is specified.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-313: A file cannot be read.

Source: TSA6OO.NLM
Explanation: The file might be corrupted.
Action: Try the operation again. If the problem persists, contact a Novell support provider.

TSA6OO-X-314: Either no resource name can be found or all resource names have been found.

Source: TSA6OO.NLM
Explanation: The Scan Target Service Resource function has found all resources, or no resources were found.
Action: If you are expecting a resource list, make sure the data set sequence is correct. Then try again.

TSA6OO-X-315: The program’s attempt to scan failed, probably because an invalid path was specified.

Source: TSA6OO.NLM
Explanation: An invalid path was specified.
Action: Specify a valid path for the requested name space. Make sure the user has appropriate user access rights.

TSA6OO-X-316: The program cannot scan file entry information.

Source: TSA6OO.NLM
Explanation: File scan failed.
Action: Specify a valid filename for the requested name space. Make sure the user has appropriate user access rights.

TSA6OO-X-317: You cannot alter the resource list while scans are in progress.

Source: TSA6OO.NLM
Explanation: The resource list will remain persistent until the scan is complete. It cannot be altered now.
Action: Complete the current scan and start a new scan after rebuilding the resource list.

TSA6OO-X-318: Information applicable to a specific name space cannot be scanned.

Source: TSA6OO.NLM
Action: Make sure that you have specified a valid name space and that name space support is loaded on the selected volume.

TSA6OO-X-319: The program cannot scan for trustees.

Source: TSA6OO.NLM
Explanation: TSA6OO could not scan for a trustee list.
Action: Make sure the user has appropriate user access rights.
Action: Make sure the entry index is valid; then try again.

TSA6OO-X-320: This scan type is not used.

Source: TSA6OO.NLM
Explanation: An invalid or unused scan type was specified.
Action: Specify a valid scan type and try again.

TSA6OO-X-321: This selection type is not used.

Source: TSA6OO.NLM
Explanation: An invalid or unused selection type was specified.
Action: Specify a valid scan type and try again.

TSA6OO-X-322: The program cannot set file information.

Source: TSA6OO.NLM
Explanation: The program cannot set file information.
Action: Make sure the user has appropriate user access rights.
Action: Make sure the information to be set is valid.

TSA6OO-X-323: The transport mechanism has failed.

Source: TSA6OO.NLM
Explanation: The intermodule communication layer has failed.
Action: Re-establish the LAN communication between machines.

TSA6OO-X-324: The read/write request exceeds 128 KB.

Source: TSA6OO.NLM
Explanation: An intermodule communication request exceeds the 128 KB limit.
Action: Restructure the read/write request into pieces of 128 KB or smaller.

TSA6OO-X-325: An invalid or inactive TSA was specified.

Source: TSA6OO.NLM
Explanation: A TSA (Target Service Agent) was specified that cannot be found.
Action: Make sure the TSA you want is valid and active. If it is not loaded, load it and try again.

TSA6OO-X-326: The requested function is not supported by this TSA.

Source: TSA6OO.NLM
Explanation: The requested function is not supported on the selected TSA (Target Service Agent).
Action: Request a valid function, or select another TSA that supports the requested function.

TSA6OO-X-328: The program cannot write extended attribute (value).

Source: TSA6OO.NLM
Explanation: The program could not write the extended attributes.
Action: Make sure the extended attributes are valid and the file or directory is valid.
Action: Make sure sufficient extended attribute space is on the volume.
Action: Make sure the user has appropriate user access rights.

TSA6OO-X-329: An error occurred while the program attempted to write to a file. The full request could not be written.

Source: TSA6OO.NLM
Explanation: You might not have enough disk space, or the file might be corrupted.
Action: Do one or more of the following:

TSA6OO-X-330: An error occurred while the program attempted to write to a file.

Source: TSA6OO.NLM
Possible Cause: The server might not have enough disk space.
Action: Increase the available disk space on the volume. See Resolving Server Disk Space Problems in the NW 6.5 SP8: Server Operating SystemAdministration Guide.
Possible Cause: The file might be corrupted.
Action: Check the contents of the file for corruption.

TSA6OO-X-332: All available connections to TSA are in use.

Source: TSA6OO.NLM
Explanation: The TSA has reached its maximum limit for servicing the connection.
Action: Wait for a connection to be released by another application. Retry the operation.

TSA6OO-X-333: An attempt was made to put compressed data on a non-compressed volume.

Source: TSA6OO.NLM
Explanation: The target server does not support compression on a volume. The compressed data cannot be restored that that volume.
Action: Do the following:

  1. Enable compression for the volume.

  2. Back up the compressed files as expanded files.

  3. Try the operation again.

TSA6OO-X-334: An internal TSA error occurred. See the error log for details.

Source: TSA6OO.NLM
Explanation: An internal error has occurred.
Action: Note the error log messages and contact a Novell support provider.