61.0 SBCON Messages

These messages are generated by the SBackup Console (SBCON) module.

SBCON-X-7: Screen allocation error

Source: SBCON.NLM
Possible Cause: There is not enough memory on the server.
Action: Unload SBCON.NLM and QMAN.NLM Reduce the transfer buffer size in the configuration file, SYS:\ETC\SMS\SBACKUP.CFG, then reload QMAN.NLM and SBCON.NLM again. If the problem persists, upgrade the server memory and try again.

SBCON-X-21: Error connecting to TSA

Source: SBCON.NLM
Possible Cause: The TSA is not loaded or there may be another problem with the TSA.
Action: If the TSA is not loaded, load the TSA. If the TSA is loaded, unload and reload the TSA and SMDR.

SBCON-X-22: Error listing the Target Service

Source: SBCON.NLM
Possible Cause: The workstation TSAs have not been registered to the TSAProxy.
Action: 1. Make sure the workstation TSA is running. 2. Set the preferred server through the TSA interface and submit the registration. 3. Retry the operation. If the problem persists, contact your Novell support provider.

SBCON-X-23: No services are available.

Source: SBCON.NLM
Possible Cause: The workstation TSAs have not been registered to the TSAProxy.
Action: 1. Make sure the workstation TSA is running. 2. Set the preferred server through the TSA interface and submit the registration. 3. Retry the operation. If the problem persists, contact your Novell support provider.

SBCON-X-27: The specified user does not exist.

Source: SBCON.NLM
Possible Cause: The user name entered is not valid.
Action: Type the appropriate user name and context. If full context must be used, precede the name with a period (.), for example, .admin.novell. Try again.

SBCON-X-28: Error connecting to Target Service

Source: SBCON.NLM
Possible Cause: With DOS TSA, only one connection is allowed. This error may occur if several users are trying to connect to the DOS TSA at the same time.
Action: Disconnect the first connection and retry the operation.

SBCON-X-30: Error opening the file filename

Source: SBCON.NLM
Possible Cause: Either the directory does not exist for this file, or this file is Read Only.
Action: If the directory does not exist, create the directory. If the file is Read Only, remove the Read Only attributes.

SBCON-X-32: The specified key function is not implemented.

Source: SBCON.NLM
Possible Cause: This function is not yet implemented.
Action: Contact your Novell support provider for the new modules when they become available.

SBCON-X-36: Error listing the resource

Source: SBCON.NLM
Possible Cause: For workstation TSAs, none of the drives have been exported.
Action: Export some of the drives using the TSA interface. Retry the operation. If the problem persists, contact your Novell support provider.

SBCON-X-41: Error creating the portal

Source: SBCON.NLM
Possible Cause: The maximum number of windows has been created.
Action: Close some of the windows and try again. If the problem persists, unload and reload SBCON.NLM. Contact your Novell support provider.

SBCON-X-42: Error listing Advanced Options

Source: SBCON.NLM
Possible Cause: You are not yet connected to the TSA.
Action: First connect to the TSA, then try to list the Advanced Options. If the problem persists, contact your Novell support provider.

SBCON-X-43: Error listing selection hot spot

Source: SBCON.NLM
Possible Cause: You are not yet connected to the TSA.
Action: First connect to the TSA, then try to list the Advanced Options. If the problem persists, contact your Novell support provider.

SBCON-X-44: Error listing scanning hot spot

Source: SBCON.NLM
Possible Cause: You are not yet connected to the TSA.
Action: First connect to the TSA, then try to list the Advanced Options. If the problem persists, contact your Novell support provider.

SBCON-X-58: Error inserting into list.

Source: SBCON.NLM
Possible Cause: There was an error scanning the data set.
Action: Try connecting to the TSA again, then select the data set.

SBCON-X-60: No TSAs are available on the selected server.

Source: SBCON.NLM
Possible Cause: No TSAs have been loaded.
Action: Load the appropriate TSA (TSA600.NLM, TSANDS.NLM, TSADOSP.NLM, or GWTSA.NLM). Retry the operation. If the problem persists, contact your Novell support provider.

SBCON-X-61: You should select a data set to back up first.

Source: SBCON.NLM
Possible Cause: No data sets have been selected when you tried to submit a job.
Action: Before you submit a job, select at least one data set to back up, then submit the job.

SBCON-X-74: Are you sure you want to delete all marked sessions?

Source: SBCON.NLM
Possible Cause: You are trying to delete all the sessions marked using <F5>.
Action: Select Yes if you want to delete all the selected session files; otherwise, select No.

SBCON-X-75: Are you sure you want to delete this session?

Source: SBCON.NLM
Possible Cause: You are trying to delete a session file.
Action: Select Yes to delete the file; select No if you do not want to delete the file.

SBCON-X-79: An undefined error has occurred: error_number.

Source: SBCON.NLM
Possible Cause: An internal error has occurred.
Action: Note the error number and the conditions for simulating the error. Contact your Novell support provider.

SBCON-X-84: An invalid message number is generated.

Source: SBCON.NLM
Possible Cause: The nutlib.msg file is the wrong version.
Action: Obtain the latest nutlib.msg from Novell for the appropriate local language and install it in the Sys:\system\nls\language\ directory.

SBCON-X-100: Error error_number occurred during the engine’s attempt to open directory name.

Source: SBCON.NLM
Possible Cause: The permissions were not sufficient to browse the directory.
Action: Log in as a user who has sufficient rights and try again.

SBCON-X-101: Error error_number occurred in Get Server Information.

Source: SBCON.NLM
Possible Cause: An internal error has occurred.
Action: Note the error number and contact your Novell support provider.

SBCON-X-114: The engine cannot parse path pathname.

Source: SBCON.NLM
Possible Cause: The configuration file pathname is corrupted.
Action: Delete the configuration file and load QMAN.NLM Accept the default settings, or change the settings for QMAN.NLM to regenerate the configuration file. Load SBCON.NLM again.

SBCON-X-156: Out of memory!

Source: SBCON.NLM
Possible Cause: The server is out of memory.
Action: Unload SBCON.NLM and QMAN.NLM Reduce the transfer buffer size in the configuration file, SYS:\ETC\SMS\SBACKUP.CFG, then reload QMAN.NLM and SBCON.NLM again. If the problem persists, upgrade the server memory and try again.

SBCON-X-175: Scheduling not enabled

Source: SBCON.NLM
Possible Cause: The scheduling information for the job is corrupted or it is wrong. Perhaps other applications have tried to submit a job to the job queue.
Action: Make sure the job queue is being used by Enhanced SBACKUP only.
Action: If the job file is corrupted, enter the scheduling information again, but unexpected results might occur.
Action: Delete the job and try again.

SBCON-X-178: The job is no longer in the queue.

Source: SBCON.NLM
Possible Cause: While the job was being executed, the job was deleted using NetWare Administrator.
Action: Do not use NetWare Administrator to access SMS job queues.

SBCON-X-183: Status report error: error_number

Source: SBCON.NLM
Possible Cause: An internal error has occurred.
Action: Report the error message and number to your Novell support provider.

SBCON-X-193: Do you want to abort this session?

Source: SBCON.NLM
Possible Cause: You pressed Delete while displaying the active job’s runtime status in the Job Administration menu.
Action: Select Yes if you want to stop the job; otherwise, select No and the job will continue to run.

SBCON-X-196: Alert Handler can’t allocate the resource_tag_name resource tag.

Source: SBCON.NLM
Possible Cause: The server is out of memory.
Action: Unload SBCON.NLM and QMAN.NLM Reduce the transfer buffer size in the configuration file, SYS:\ETC\SMS\SBACKUP.CFG, then reload QMAN.NLM and SBCON.NLM again. If the problem persists, upgrade the server memory and try again.

SBCON-X-197: No connection is available to SMSDI.

Source: SBCON.NLM
Possible Cause: The SMSDI.NLM module is not loaded.
Action: Load SMSDI.NLM at the console prompt.

SBCON-X-198: No device and media are found with the given name.

Source: SBCON.NLM
Possible Cause: The device driver for the tape device/host adapter is not loaded.
Action: Load the correct device driver.
Possible Cause: No media is present in the tape drive.
Action: Check that the media is present in the tap drive.
Possible Cause: The media is in use by another job.
Action: Make sure no other job is running on the media.
Possible Cause: The media label does not match the media label provided during the job submission.
Action: Make sure the label provided during job submission is the same as the media label present during backup/restore. If you are not sure, accept the default setting for the Device/Media name during job submission.

SBCON-X-199: No device is found in the SMSDI list.

Source: SBCON.NLM
Possible Cause: The device driver was loaded after loading SMSDI.
Action: Unload and reload SMSDI.NLM. If the problem persists, try using the command list devices at the server console.

SBCON-X-200: The device is not found in the Media Manager database.

Source: SBCON.NLM
Possible Cause: The correct device driver has not been loaded, or an outdated device driver was loaded.
Action: Load the correct device driver. Contact the device vendor or a Novell support provider for the correct driver version.

SBCON-X-201: No device is reserved.

Source: SBCON.NLM
Possible Cause: None of the devices is available for use.
Action: Free a device and retry the operation. If the problem persists, contact a Novell support provider.

SBCON-X-202: The device cannot be reserved.

Source: SBCON.NLM
Possible Cause: The device is in use by another application.
Action: Check if you have opened the device on the client interface or if another job is running. Retry the operation. If the problem persists, contact a Novell support provider.

SBCON-X-203: The list device is not finished.

Source: SBCON.NLM
Possible Cause: You tried to access the device when the list device command was used at the server console.
Action: Wait for the list device command to complete, then retry the operation.

SBCON-X-204: The device name format is invalid.

Source: SBCON.NLM
Possible Cause: The device name is not in the format, device.media.
Action: Make sure the name of the device is in the correct format (device name.media name).

SBCON-X-205: The input parameters are wrong.

Source: SBCON.NLM
Possible Cause: You were restoring files that could not be backed up because they were open.
Action: None required.

SBCON-X-206: Destination slot is not empty.

Source: SBCON.NLM
Possible Cause: You tried to move media into a slot that was not empty.
Action: Move the media into a slot that is empty. See the media list to determine which slots are empty.

SBCON-X-207: The media in the device is being used.

Source: SBCON.NLM
Possible Cause: Another job is running on the same media you are trying to access.
Action: Wait for the job to complete before running another job. Retry the operation.

SBCON-X-208: The list media is not finished.

Source: SBCON.NLM
Possible Cause: You tried to access the media when the list media command was used at the server console.
Action: Wait for the list media command to complete, then retry the operation.
Possible Cause: The Media Manager does not have the media database.
Action: If you just inserted a new tape into the tape drive, wait a few minutes, then try to list the media. If the problem persists, close Enhanced SBACKUP and unload it. Reload Enhanced SBACKUP.

SBCON-X-209: The media is not found.

Source: SBCON.NLM
Possible Cause: No media is present in the device.
Action: Load the media in the device and retry the operation.

SBCON-X-210: No media is reserved.

Source: SBCON.NLM
Possible Cause: All the media are busy or no medium is present.
Action: Wait for the medium to be released by the application or insert a new media in a device.

SBCON-X-211: The media cannot be reserved.

Source: SBCON.NLM
Possible Cause: All the media are busy or no medium is present. The media is being used by another job.
Action: Wait for the medium to be released by the application or insert a new medium in a device. Close the other application and try again.

SBCON-X-212: The media sequence is null.

Source: SBCON.NLM
Possible Cause: The server is out of memory.
Action: Unload SBCON.NLM and QMAN.NLM Reduce the transfer buffer size in the configuration file, SYS:\ETC\SMS\SBACKUP.CFG, then reload QMAN.NLM and SBCON.NLM again. If the problem persists, upgrade the server memory and try again.

SBCON-X-213: Mount failed

Source: SBCON.NLM
Possible Cause: The media is corrupted or has not been reserved properly.
Action: Eject the media and try again or change the media.

SBCON-X-214: The server is out of memory.

Source: SBCON.NLM
Possible Cause: The server is out of memory.
Action: Unload SBCON.NLM and QMAN.NLM Reduce the transfer buffer size in the configuration file, SYS:\ETC\SMS\SBACKUP.CFG, then reload QMAN.NLM and SBCON.NLM again. If the problem persists, upgrade the server memory and try again.

SBCON-X-219: Spanning set creation error

Source: SBCON.NLM
Possible Cause: The media list in the SMSDI database is incorrect.
Action: Unload SBCON and type the command list device at the server console. Retry the operation.

SBCON-X-221: The media name is invalid.

Source: SBCON.NLM
Possible Cause: The media name in the job file is not the same as the media loaded when the job began.
Action: Locate the correct media and insert it into the device. Retry the operation.

SBCON-X-224: The source slot is not reserved.

Source: SBCON.NLM
Possible Cause: The backup or restore source is missing. No medium exists in the location where the medium needs to be moved.
Action: Make sure the medium exists in the source slot. Retry the operation.

SBCON-X-266: Cannot delete an active job. If you want to terminate it, press Insert and then Delete.

Source: SBCON.NLM
Possible Cause: You cannot delete a job that is being processed or that is running.
Action: To terminate the job, press Insert in the job list menu, then press Delete in the job activity screen.

SBCON-X-295: Could not run

Source: SBCON.NLM
Possible Cause: The submitted job could not be executed.
Action: Check that the correct TSA is loaded.
Action: For workstation TSAs, check that the TSA has registered to the correct TSAProxy.
Action: Check that the device is on, contains media, and the device drivers are loaded.
Action: Load SMSDI.NLM after loading the device drivers.

SBCON-X-303: No Target Service Agents were found on this server.

Source: SBCON.NLM
Possible Cause: No TSAs have been loaded.
Action: Load the appropriate TSA (TSA600.NLM, TSANDS.NLM, TSADOSP.NLM, or GWTSA.NLM). Retry the operation. If the problem persists, contact your Novell support provider.

SBCON-X-306: An error occurred while connecting to the TSA.

Source: SBCON.NLM
Possible Cause: The TSA is not loaded or there may be another problem with the TSA.
Possible Cause: Enhanced SBACKUP could not connect to the TSA.
Action: Load the TSA. If the TSA is loaded, unload and reload the TSA and SMDR. Retry the operation.

SBCON-X-307: No Backup/Restore Target Services were found on this server.

Source: SBCON.NLM
Possible Cause: The workstation TSAs have not been registered to the TSAProxy.
Action: Make sure the workstation TSA is running.
Action: Set the preferred server through the TSA interface and submit the registration.
Action: Retry the operation. If the problem persists, contact your Novell support provider.

SBCON-X-309: Could not connect to the Target Service

Source: SBCON.NLM
Possible Cause: Enhanced SBACKUP could not connect to the TSA.
Action: Verify that the correct user name and password were entered. Make sure to use the fully distinguished name (FQN) for the user.

SBCON-X-311: Warning! You are not connected to any Target Service.

Source: SBCON.NLM
Possible Cause: You did not select a target service during job submission or the authentication failed.
Action: Select a target service from the list, and provide the username and password before submitting the job.

SBCON-X-317: QManager: Job name failed. Error number.

Source: SBCON.NLM
Possible Cause: The job failed to run.
Action: See the activity log, Sys:system\tsa\log\activity.log, for the cause of the failure.

SBCON-X-318: QManager: Error executing job name: error_number

Source: SBCON.NLM
Possible Cause: An error occurred while executing the job.
Action: See the activity log, Sys:system\tsa\log\activity.log, for the cause of the failure.

SBCON-X-319: QManager: Job name was found to be deleted unexpectedly!

Source: SBCON.NLM
Possible Cause: You deleted a job while it was active.
Action: Enhanced SBACKUP does not allow you to delete an active job.

SBCON-X-342: No session or error file was found.

Source: SBCON.NLM
Possible Cause: The session files were deleted.
Action: Create the session files for the media by submitting a create session file job.

SBCON-X-416: You have not selected any resource to back up.

Source: SBCON.NLM
Possible Cause: You didn’t select a resource for your backup when you submitted the job.
Action: Select a resource to back up. Retry the operation.

SBCON-X-417: You are not connected to any TSA.

Source: SBCON.NLM
Possible Cause: When submitting a job, you selected the Target Service list without selecting a target.
Action: Select a target, or quit Enhanced SBACKUP without submitting a job.

SBCON-X-428: The medium does not exist.

Source: SBCON.NLM
Possible Cause: No media is present with the name given.
Action: Find the correct medium and insert it in the device.

SBCON-X-429: No media is present.

Source: SBCON.NLM
Possible Cause: No media is present in the device.
Action: Insert the medium and retry the operation.

SBCON-X-453: CRCs do not match

Source: SBCON.NLM
Possible Cause: The medium may be corrupted.
Action: Replace the media and retry the operation. If the problem persists, contact a Novell support provider.

SBCON-X-454: Could not get the CRC FID

Source: SBCON.NLM
Possible Cause: The medium may be corrupted.
Action: Replace the media and retry the operation. If the problem persists, contact a Novell support provider.

SBCON-X-455: The backup session does not contain CRC information.

Source: SBCON.NLM
Possible Cause: During backup, the verification option was not selected.
Action: The session cannot be verified. Create the session files for the media.

SBCON-X-456: Cannot read the first buffer header

Source: SBCON.NLM
Possible Cause: The media my be corrupted.
Action: Replace the media and retry the operation. If the problem persists, contact a Novell support provider.

SBCON-X-464: Unable to open activity log name for writing.

Source: SBCON.NLM
Possible Cause: The activity log file Sys:system\tsa\log\activity.log is in use by another application, or the TSA directory has been unexpectedly deleted.
Action: Create the directory if it has been deleted. If the file is open, close the application that is using the file. Make sure the activity file is not marked as Read Only. Retry the operation.

SBCON-X-468: No error files exist in this directory.

Source: SBCON.NLM
Possible Cause: The session and error file were deleted.
Action: Create the session and error files.

SBCON-X-469: No log files exist in this directory.

Source: SBCON.NLM
Possible Cause: The session and error file were deleted.
Action: Create the session and error files.

SBCON-X-470: Error accessing queue queue_name: code.

Source: SBCON.NLM
Possible Cause: There are insufficient rights to access the queue, or the queue does not exist.
Action: Make sure the queue exists. If it is not present, reload QMAN.NLM with the option new. This option re-creates the queue and sets the correct rights. This should be done by the server with a tape device.

SBCON-X-482: An invalid path was used.

Source: SBCON.NLM
Possible Cause: The path is not correct.
Action: Use the correct pathname for the correct name space.

SBCON-X-488: QManager is not running. Cannot display the runtime status.

Source: SBCON.NLM
Possible Cause: The SBCON.NLM module was loaded without QMAN.NLM
Action: Unload SBCON.NLM, load QMAN.NLM and reload SBCON.NLM.

SBCON-X-494: Verification failed

Source: SBCON.NLM
Possible Cause: The medium is corrupted.
Action: Replace the media and retry the operation.

SBCON-X-495: Verification error

Source: SBCON.NLM
Possible Cause: The medium is corrupted.
Action: Replace the media and retry the operation.

SBCON-X-509: Errors occurred in This Session:

Source: SBCON.NLM
Possible Cause: The error log file reported the errors that occurred in this session.
Action: Check the error log file for the list of errors.

SBCON-X-519: Could not connect to the service

Source: SBCON.NLM
Possible Cause: You entered an incorrect password.
Action: Try entering the password again.
Possible Cause: The backup engine could not connect to the target service while executing a job.
Action: Note the error code number and error message. It will indicate what happened. If the problem persists, contact your Novell support provider.

SBCON-X-520: Could not connect to the TSA

Source: SBCON.NLM
Possible Cause: You entered an incorrect password.
Possible Cause: The backup engine could not connect to the target service while executing a job.
Action: Note the error code number and error message. It will indicate what happened. If the problem persists, contact your Novell support provider.

SBCON-X-522: An error occurred in the restore job.

Source: SBCON.NLM
Possible Cause: The restore job could not be completed.
Action: Check the activity log file in Sys:system\tsa\log\activity.log for the error.

SBCON-X-525: No media is present.

Source: SBCON.NLM
Possible Cause: Some of the slots are empty in the Autoloader.
Action: This message is for information only.

SBCON-X-528: Could not execute the job: job_name

Source: SBCON.NLM
Possible Cause: The submitted job could not be executed.
Action: Check that the correct TSA is loaded.
Action: For workstation TSAs, check that the TSA has registered to the correct TSAProxy.
Action: Check that the device is on, contains a media, and the device drivers are loaded.
Action: Load SMSDI.NLM after loading the device drivers.

SBCON-X-533: Could not load the engine: engine_name

Source: SBCON.NLM
Possible Cause: The SME.NLM module must be present in the system path.
Action: Make sure the SME.NLM is present in the SYS:SYSTEM directory.

SBCON-X-539: An error occurred during session file creation.

Source: SBCON.NLM
Possible Cause: The submitted job could not be executed.
Action: Check that the correct TSA is loaded.
Action: For workstation TSAs, check that the TSA has registered to the correct TSAProxy.
Action: Check that the device is on, contains a media, and the device drivers are loaded.
Action: Load SMSDI.NLM after loading the device drivers.

SBCON-X-540: Could not create session file: filename. Error code

Source: SBCON.NLM
Possible Cause: The session file was already open.
Action: None required.
Possible Cause: The user does not have rights to the directory.
Action: Make sure the directory rights are correct.
Possible Cause: There may be no space left in the volume.
Action: Make sure that there is enough space on the volume. If no space exists on the volume, delete any unwanted files or increase the disk capacity.

SBCON-X-541: Could not create error file: filename. Error code

Source: SBCON.NLM
Possible Cause: The session file was already open.
Action: None required.
Possible Cause: The user does not have rights to the directory.
Action: Make sure that the directory rights are correct.
Possible Cause: There may be no space left in the volume.
Action: Make sure there is enough space on the volume. If no space exists on the volume, delete any unwanted files or increase the disk capacity.