Novell Doc: NW 6.5 SP8: System Messages

SMSDI-X-256: An attempt was made to read or write when that access was not granted.

Source: SMSDI.NLM

Possible Cause: Access has been denied because another application has reserved the requested device or medium.

Action: Before proceeding with the read or write operation, select a medium or device to which the user has access and make sure that access was granted.

SMSDI-X-257: Upon checking the buffer header on a read operation, the SMSDI determined that it is not what it was expecting.

Source: SMSDI.NLM

Possible Cause: The medium was not written to correctly.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-258: BufferSize requested is not sufficient for application’s and SMSDI’s blockHeaderSize.

Source: SMSDI.NLM

Possible Cause: An internal error occurred between Enhanced SBACKUP and SMSDI.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-259: A media error was encountered, but was corrected by the driver.

Source: SMSDI.NLM

Possible Cause: The read or write operation was successful, but the device had to use its error correction feature to recover the data.

Action: Replace the device or medium as soon as possible.

SMSDI-X-260: The deviceHandle passed is invalid.

Source: SMSDI.NLM

Possible Cause: The selected device is no longer valid or has changed.

Action: Try selecting the device again. If the problem persists, contact a Novell support provider.

SMSDI-X-261: While getting the list of devices available, a change in the list of available devices has occurred. Restart the NWSMSDListDevices.

Source: SMSDI.NLM

Possible Cause: A device was added or deleted while Enhanced SBACKUP was getting the list of devices.

Action: Select the Storage Device Administration menu again to rescan the devices.

SMSDI-X-262: Device exists but is not available (for example, already subjugated by another application in a nonsharing mode).

Source: SMSDI.NLM

Explanation: The requested device has been reserved by another application.

Action: Select another device, or find the application that has reserved the device and free it from that application.

SMSDI-X-263: Device does not exist.

Source: SMSDI.NLM

Possible Cause: TA device error probably caused the device to become deactivated, or the device driver was unloaded.

Action: Rescan the device list by reselecting the Storage Device Administration menu again.

SMSDI-X-264: Early warning was detected on the media.

Source: SMSDI.NLM

Explanation: The medium has reached the early warning. This is dealt with by the engine. This message is for information only.

SMSDI-X-265: The end of media was detected.

Source: SMSDI.NLM

Possible Cause: The requested session was not found.

Action: Request another session or insert another medium.

SMSDI-X-266: The medium has been unexpectedly changed since it was last identified.

Source: SMSDI.NLM

Possible Cause: SMSDI keeps track of what medium it expects to find in the device. It verifies the medium before executing reads or writes. In this instance, the wrong medium was in the device.

Action: Put the correct medium into the device, or reselect the current medium from the Storage Device Administration menu item.

SMSDI-X-267: An unexpected internal SMSDI error has occurred.

Source: SMSDI.NLM

Possible Cause: An internal error occurred.

Action: Write down the sequence of events that led to this error, along with any other system messages. If the problem persists, contact a Novell support provider.

SMSDI-X-268: An invalid connection number was passed to SMSDI.

Source: SMSDI.NLM

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-269: An invalid message number was passed to SMSDI.

Source: SMSDI.NLM

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Write down the number of any Enhanced SBACKUP messages that are displayed with this message. Diagnose and correct the problem from the information in the Enhanced SBACKUP message if possible. Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-270: One or more of the parameters is NULL or invalid.

Source: SMSDI.NLM

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Write down the number of any Enhanced SBACKUP messages that are displayed with this message. Diagnose and correct the problem from the information in the Enhanced SBACKUP messages, if possible. Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-271: NWSMSDWriteSector or NWSMSDReadSector requested fractional sector size.

Source: SMSDI.NLM

Possible Cause: The media is not compatible with SMS.

Action: Use SMS compatible media.

Possible Cause: If the media is compatible with SMS, this is probably an internal program error.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-272: An invalid session data type was passed in a control block to NWSMSDWriteSessionData/NWSMSDReadSessionData.

Source: SMSDI.NLM

Explanation: The medium was not written to correctly.

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-273: An invalid destination location was specified.

Source: SMSDI.NLM

Explanation: The medium was not written to correctly.

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-274: Data from media is valid but error correction had to be used to read.

Source: SMSDI.NLM

Explanation: The read or write operation was successful, but the device had to use its error correction feature to recover the data.

Action: Replace the device or medium as soon as possible.

SMSDI-X-275: Media Manager reported a failure when attempting the requested read or write operation.

Source: SMSDI.NLM

Possible Cause: The device or the media reported a hardware failure.

Action: Replace the media or service the device.

SMSDI-X-276: The mediaHandle passed is invalid.

Source: SMSDI.NLM

Possible Cause: The selected media is no longer valid or has changed.

Action: Try selecting the media again by selecting the device under the Storage Device Administration menu. If the problem persists, contact a Novell support provider.

SMSDI-X-277: An attempt was made to label an already labeled media.

Source: SMSDI.NLM

Explanation: This alert is handled by Enhanced SBACKUP. The message informs the user that a valid label already exists. This message is for information only.

SMSDI-X-278: While getting the list of media available, a change in the available media has occurred. Start listing the media from the beginning.

Source: SMSDI.NLM

Possible Cause: A device was added or deleted while Enhanced SBACKUP was getting the list of devices.

Action: Select the Storage Device Administration menu again to rescan the devices.

SMSDI-X-279: A file mark was encountered while reading media. This is not fatal and data in buffer up to number of sectors read is valid.

Source: SMSDI.NLM

Explanation: The media was not correctly written.

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-280: A set mark was encountered while reading the medium. This is not fatal and data in buffer up to number of sectors read is valid.

Source: SMSDI.NLM

Explanation: The medium was not written to correctly.

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-281: An attempt was made to perform an action (for example, Move Media) on a mounted medium which is illegal.

Source: SMSDI.NLM

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-282: The medium exists but is not available (for example, already subjugated by another application in a non-sharing mode).

Source: SMSDI.NLM

Possible Cause: The requested medium has been reserved by another application.

Action: Select another medium, or find the application that has reserved the medium and free it from that application.

SMSDI-X-283: The medium does not exist.

Source: SMSDI.NLM

Explanation: The requested medium no longer exists.

Action: Select another device under the Storage Device Administration menu.

SMSDI-X-284: The medium does not have a valid SMS label.

Source: SMSDI.NLM

Explanation: The medium was not written to correctly.

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-285: The medium has not been mounted using the Mount Media function.

Source: SMSDI.NLM

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-286: The requested operation, if completed, would have resulted in creating media that would not have been SMS compliant.

Source: SMSDI.NLM

Possible Cause: The media is not SMS compliant.

Action: Select another device under the Storage Device Administration menu.

SMSDI-X-287: No more connections available for Alert Routines.

Source: SMSDI.NLM

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-288: No memory is available for any size block.

Source: SMSDI.NLM

Possible Cause: The server does not have enough available memory.

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

SMSDI-X-289: The application has requested an operation that requires READ access mode, but this has not been granted.

Source: SMSDI.NLM

Possible Cause: In NetWare 6, this message will appear only if an internal error has occurred.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-290: A call was made to ReadSessionData but the media is at the end of the session [including session and media index].

Source: SMSDI.NLM

Possible Cause: An internal error has occurred in the program.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-291: The application has requested an operation that requires WRITE access mode, but this has not been granted.

Source: SMSDI.NLM

Possible Cause: In NetWare 6, this message will appear only if an internal error has occurred in the program.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-292: The request for non-share subjugation failed because the device or medium is already subjugated in share mode by another SMS application or an attempt to perform an operation on a shared medium or device which requires non-share mode.

Source: SMSDI.NLM

Possible Cause: In NetWare 6, this message will appear only if an internal error has occurred in the program.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-293: SMSDI memory allocation failed.

Source: SMSDI.NLM

Possible Cause: The server does not have enough available memory.

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

SMSDI-X-294: The partition is not an SMS medium or partition.

Source: SMSDI.NLM

Possible Cause: The medium or the partition cannot support SMS media.

Action: For a read operation, select an SMS medium. For a write operation, overwrite the device or medium with caution. Just because SMS cannot identify the media does not mean that it contains no valuable data.

SMSDI-X-295: The position requested is not valid (for example, a relative mode was specified but either the expected sessionNumber or the expected blockNumber is NULL).

Source: SMSDI.NLM

Explanation: The medium was not written to correctly.

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-296: The position requested was not located on the media.

Source: SMSDI.NLM

Explanation: The medium was not written to correctly.

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-297: The requested session handle is not valid either because the session was not opened or the medium is no longer positioned within the requested session.

Source: SMSDI.NLM

Explanation: The medium was not written to correctly.

Possible Cause: An internal error occurred in the program that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-298: The specified session header was not found at the location specified, or if a location was not specified, there is not a session header that matches the specified description.

Source: SMSDI.NLM

Explanation: The medium was not written to correctly.

Possible Cause: The wrong medium is inserted.

Action: Insert the medium that contains the requested session or request a session that exists on this medium.

Possible Cause: An internal error occurred that Enhanced SBACKUP was unable to handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-299: The operation timedout.

Source: SMSDI.NLM

Explanation: The length of time allowed for the requested operation has been exceeded.

Possible Cause: A media error, a media failure, or a problem with the device occurred.

Action: Make sure the device is running and functioning properly. Use the correct media. Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-300: The transfer buffer passed was not large enough to hold the entire transfer buffer from the media. SMSDI returned as much of the transfer buffer as would fit.

Source: SMSDI.NLM

Possible Cause: An internal error has occurred in the program.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-301: One or more of the requested transfer requests was not able to be canceled. SMSDI will complete those requests normally.

Source: SMSDI.NLM

Explanation: Even though an error occurred, SMSDI was able to complete one or more requests. This message is for information only

SMSDI-X-302: A function was called which is not supported by this version of SMSDI.

Source: SMSDI.NLM

Possible Cause: A required device driver function is not supported by the current version of SMSDI.

Action: Make sure the device driver is a current version and supports SMS. Also, make sure that the server is running the most recent version of SMSDI. Upgrade the device driver, device, or SMSDI if necessary. Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-303: An SMSDI function was asked to perform a service that is not supported in this version of SMSDI.

Source: SMSDI.NLM

Possible Cause: An internal error has occurred in the program.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-304: The NetWare operating system returned an error.

Source: SMSDI.NLM

Possible Cause: An error occurred in the NetWare operating system.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-305: The device driver or device itself returned an error.

Source: SMSDI.NLM

Possible Cause: The device or the medium failed.

Action: Make sure the device is running and functioning properly. Check the medium. Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-306: An I/O function was successfully aborted.

Source: SMSDI.NLM

Possible Cause: An internal error occurred that Enhanced SBACKUP could not handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-307: An I/O function was aborted due to a previous error.

Source: SMSDI.NLM

Possible Cause: An internal error occurred that Enhanced SBACKUP could not handle.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-308: An attempt was made to use a function that is not supported by the device driver.

Source: SMSDI.NLM

Possible Cause: A required device driver function is not supported by the current device driver or device.

Action: Make sure the device driver is a current version and supports SMS. Upgrade the device driver or device if necessary. Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-309: Invalid data was encountered on the media.

Source: SMSDI.NLM

Explanation: The medium was not written to correctly.

Possible Cause: The medium is defective.

Action: Use a new device or medium.

SMSDI-X-310: The medium is write protected.

Source: SMSDI.NLM

Possible Cause: The write protect switch on the medium is set.

Action: Use another medium or remove the write-protection from the currently selected medium.

SMSDI-X-311: The device driver or device itself returned an unknown error.

Source: SMSDI.NLM

Possible Cause: An unknown error occurred in the device driver or the device itself.

Action: Make sure the device is functioning properly. Also make sure the server is running a current, uncorrupted copy of the driver. Then try again. If the problem persists, contact a Novell support provider.

SMSDI-X-312: The header is too large to fit in a physical sector.

Source: SMSDI.NLM

Possible Cause: The medium is not compatible with SMSDI.

Action: Make sure the medium is compatible with SMS. Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-313: The medium is not formatted.

Source: SMSDI.NLM

Possible Cause: This type of medium needs to be formatted before using it.

Action: Format the medium.

SMSDI-X-314: The medium is blank.

Source: SMSDI.NLM

Explanation: This message is associated with a prompt from Enhanced SBACKUP telling the user to label the medium. This message is for information only.

SMSDI-X-315: The beginning of media was detected.

Source: SMSDI.NLM

Possible Cause: An internal program error has occurred.

Action: Try again. If the problem persists, contact a Novell support provider.

SMSDI-X-316: The sector size is not valid.

Source: SMSDI.NLM

Possible Cause: SMS cannot support the sector size of the currently selected medium.

Action: Select a new medium.

SMSDI-X-317: The medium was written in old media format and is therefore not appendable.

Source: SMSDI.NLM

Possible Cause: The NetWare 6 version or later versions of Enhanced SBACKUP cannot append to NetWare 3.11 media.

Action: Back up to NetWare 6 or later media.

SMSDI-X-318: The medium is unavailable for use by an SMS application.

Source: SMSDI.NLM

Possible Cause: The requested device or medium has been reserved by another application.

Action: Select another device or medium, or find the application that has reserved the media and free it from that application.

SMSDI-X-319: Starting a Work to do failed. Usually out of memory.

Source: SMSDI.NLM

Possible Cause: SMSDI tried to start a new execution thread, but not enough memory was available to the server.

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

SMSDI-X-320: The mediaHandle passed is invalid.

Source: SMSDI.NLM

Possible Cause: The application passed a media handle to SMSDI that never existed or is no longer valid.

Action: This problem is normally handled by the application. However, if this error does appear, try selecting the device or medium again and restarting the operation.

SMSDI-X-321: The specific info change requested for the object is not changeable.

Source: SMSDI.NLM

Explanation: The application tried to change a parameter for a device or medium that the device or medium does not allow to be changed. This message is for information only.

SMSDI-X-323: The magazine does not exist.

Source: SMSDI.NLM

Possible Cause: The requested magazine no longer exists.

Action: Select another device under the Storage Device Administration menu.

SMSDI-X-324: Magazine exists but is not available (for example, already subjugated by another application in a non-sharing mode).

Source: SMSDI.NLM

Possible Cause: The requested magazine has been reserved by another application.

Action: Select another magazine, or search for the application that has reserved the magazine and free it from that application.

SMSDI-X-325: A requested abort is pending.

Source: SMSDI.NLM

Explanation: The application normally deals with this message internally. It means that the request to abort an operation has been accepted and the abort operation is pending. This message is for information only.

SMSDI-X-326: An undefined error occurred.

Source: SMSDI.NLM

Possible Cause: An error from the device driver that is not recognized by the NetWare operating system has been reported to SMSDI.

Action: Contact a Novell support provider.

SMSDI-X-327: Cannot append to media written with SBACKUP version 3.11.

Source: SMSDI.NLM

Possible Cause: While SMSDI will read Enhanced SBACKUP for NetWare 3.11 media, it will not write the NetWare 3.11 media format. Therefore, it will not append a NetWare 6.x or later session onto media that was written using NetWare 3.11 SBACKUP.

Action: Use another medium to write the requested session.

SMSDI-X-328: The device is either not active or is offline.

Source: SMSDI.NLM

Possible Cause: The device driver has been removed, or the device has been deactivated or is offline.

Action: Perform the requested operation on another device or reactivate the requested device.

SMSDI-X-329: The magazine is either not active or is offline.

Source: SMSDI.NLM

Possible Cause: The magazine has been removed or is otherwise not active.

Action: Choose another magazine or reactivate the magazine and reselect it.

SMSDI-X-330: The media is either not active or is offline.

Source: SMSDI.NLM

Possible Cause: The media has been removed or is otherwise not active.

Explanation: Choose another magazine or reactivate the medium and reselect it.

SMSDI-X-331: The media has been using a pre-release version of SMSDI. Don’t use this media for production media.

Source: SMSDI.NLM

Possible Cause: The medium has been written using pre-release software. The media format used on this medium is not be compatible with released software.

Action: Do not use this media for production data.

SMSDI-X-332: Attempted to open a session for writing or write data while not at end of media.

Source: SMSDI.NLM

Possible Cause: The engine (such as Enhanced SBACKUP) has not placed the media at the end. Media can only be appended to.

Action: Contact the third-party engine developer, or contact a Novell support provider.

SMSDI-X-333: The transfer buffers have been received out of order.

Source: SMSDI.NLM

Possible Cause: SMSDI has detected an incorrect sequence for the returned transfer buffers. This is usually caused by an error from the originating system of this media, because an error caused by the NetWare operating system would generate error message 334.

Action: Do not use data recovered from the media until the problem has been resolved. Contact the third-party engine developer, or contact a Novell support provider.

SMSDI-X-334: The transfer buffers have been received out of order from the OS.

Source: SMSDI.NLM

Possible Cause: The operating system returned the transfer buffers out of the expected sequence. This error is most likely caused by a device driver.

Action: Do not use data recovered from the media until the problem has been resolved. Contact a Novell support provider.

SMSDI-X-335: The transfer buffer does not belong to the opened session.

Source: SMSDI.NLM

Explanation: This is used when reading interleaved sessions to notify Enhanced SBACKUP that a transfer buffer is to be ignored. This error is only to be used internally by Enhanced SBACKUP and should not be displayed.

Action: Contact the third-party engine developer, or contact a Novell support provider.

SMSDI-X-336: NWSMSDSessionOpenForReading excludes all further session opens on the media handle.

Source: SMSDI.NLM

Possible Cause: An attempt to open a write session has been issued on media that already has a session open for writing. Open sessions for reading exclude all other open attempts.

Action: Wait until the currently open session finishes and retry the operation.

SMSDI-X-337: NWSMSDSessionOpenForWriting excludes all further session open with different transfer buffer sizes.

Source: SMSDI.NLM

Possible Cause: All interleaved write sessions must have the same transfer buffer size. An attempt to open a write session with a different transfer buffer size from the write session already opened was attempted.

Action: Wait until the currently open session finishes and retry the operation.

SMSDI-X-338: NWSMSDSessionOpenForReading was attempted while a session is open for writing on the media handle.

Source: SMSDI.NLM

Explanation: An attempt to open a read session while a write session is in progress was made.

Possible Cause: A read session is not open when a write session is in process.

Action: Wait until the currently open session finishes and retry the operation.

64.0 SMSDI Messages