Error Messages Guide

From SEPsesam
Jump to: navigation, search

Copyright © SEP AG 1999-2017. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Draft.png WORK IN PROGRESS
This page is a draft. Treat the information on this page with caution as it may be incomplete.

Introduction

This guide is intended to help you quickly identify and resolve problems and errors during setup, installation and normal operation of your SEP sesam system. SEP sesam often serves as an indicator that there has been a change or event that impacts overall system performance. Changes in SEP sesam backup performance are often caused by system changes or failures.

SEP sesam provides two guides to help you resolve any problems you may encounter:

  • The Error Messages Guide lists error messages alphabetically, provides explanations of the errors wherever possible and suggestions for correcting the problems. Such messages contain an error number that can be used to access this information.
  • The Troubleshooting Guide describes problems as they may arise during the operation of your SEP sesam system, lists possible causes wherever possible and provides solutions to the problems.

First steps

To solve problems quickly and efficiently, make yourself familiar with the general troubleshooting information. Attempt to identify and resolve the problem by yourself. If you cannot find a solution to your problem, report it to SEP sesam support. The support team will then provide you with further instructions.

Identifying the problem

It is important to identify a problem as accurately as possible so that the best solution to the problem can be applied. Answer the following questions to identify the problem you are experiencing:

  1. What was the message or error?
  2. When did the error first appear?
  3. Does the error always occur after a specific action?
  4. What steps are necessary to duplicate the error?
  5. Did you make any changes to your SEP sesam environment before the error occurred?

Common problems you can solve by yourself

Below is a list of the most common problems you can solve by yourself. Most of the errors you are likely to encounter can be solved by following these instructions.

  • Check with sm_main status to see if all processes are running. If necessary, start the missing process again with sm_main reload.
  • View the day log and search for errors.
  • Check specific protocols for backups, restores.

Before contacting support

Before contacting SEP sesam support, make sure that you have exhausted any options that might enable you to solve the problem by yourself. Perform these general checks:

  1. Check whether your problem is described in the Error Messages Guide or Troubleshooting Guide.
  2. Browse through the FAQ / FAQ (DE) and check the forum (EN) / forum (DE).
  3. Go through the Common problems you can solve by yourself checklist above.
  4. Collect all relevant data about the problem and send it to SEP sesam support: error output, message ID, SEP sesam version, operating system environment.

Error messages

When an error occurs, the error message is written in the SEP sesam day log in the following format:

{date} {time} {message code} [{process pid}]: {message}

where process pid is the name of the process that issued the error.

BACKUP

Backup problems

Error message Cause Solution
E001-BACKUP Error during working on PRE interface of backup {val}:{val} 1. There is a bug in the PRE-script, or
2. Authorisation is not configured correctly, or
3. There may be a problem with network connectivity.
1. Check the user-programmed PRE-script and correct the code, or
2. Check the permissions to start the service.
E002-BACKUP Cannot submit SMS_WATCH process to queue {val} Queue manager (qm) is not running. Restart SEP sesam services. Run sm_shutdown, then sm_startup.
E003-BACKUP Could not read gv_bck_msg_{val}_{val} } Queue manager (qm) is not running. Restart SEP sesam services. Run sm_shutdown, then sm_startup.
E004-BACKUP {val} {val} A general SEP sesam error. Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E005-BACKUP Error during working on POST interface of backup {val}: {val} 1. There is a bug in the POST-script, or
2. Authorisation is not configured correctly, or
3. There may be a problem with network connectivity.
1. Check the user-programmed POST-script and correct the code, or
2. Check the permissions to start the service.
E006-BACKUP {val} error – please view backup protocol An error occurred during data transfer. Send your day log to SEP sesam customer support for review.
E007-BACKUP Invalid option {val} (line {val}) Incorrect arguments were used to call the command sm_backup. Check usage using the command sm_backup -h and retry calling sm_backup with the correct arguments. For details on using CLI, see SEP Sesam CLI.
E008-BACKUP SBC version at client side does not support encryption: {val} The SEP sesam Client (SBC) version is out of date. 1. Install the correct version of the SEP sesam Client (SBC). You can use the sm_update_client to automatically update all clients, RDS, and GUI (including a client). The sm_update_client command uses SEP sesam download center to check for new installation packages available for the configured clients.
2. If you keep experiencing the problem, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.


BASICS

Basics problems

Error message Cause Solution
E001-BASICS STR_CHAIN string overflow Represents an error that occurs when a string value is being set into a variable which is shorter than the string value. Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E002-BASICS {val} > error opening file {val} mode:{val} This error occurs if there is insufficient disk space to perform the operation. Make sure that you have an adequate amount of free disk space. Consider the following:

– extend the directory size
– create the missing directory

E003-BASICS {val} > {val} not yet existing – please restart SESAM Modified settings or other changes in SEP sesam will not take effect until the SEP sesam Server is restarted. Restart SEP sesam by using sm_shutdown, followed by sm_startup.
E004-BASICS GET_LOCAL_TCPIP_ADRESS could not find a usable WinSock DLL Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E005-BASICS HAL_REDIR string overflow: {val} {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E006-BASICS CHECK_SMS autom. SMS restart failed – SMS not running If the data store exceeds the specified limits of the file system, it must be reconfigured and the file system with sufficient size must be used. For details on data store size, see how do I calculate the data store capacity.
2. If you keep experiencing the problem, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E010-BASICS FILE copy {val} -> {val} could not open source for read Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E011-BASICS FILE copy {val} -> {val} could not open target to write Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E012-BASICS FILE copy {val} -> {val} copy invalid status {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E013-BASICS Failure in input from – to: {val} – {val} The program sm_sho was called for the SEP sesam protocol or status file using the wrong from_date or to_date argument Check the usage by running sm_sho -h. Retry calling sm_sho using the correct arguments. For example:
sm_sho test.jvr ee "stream SESAMPRL TODAY"
E014-BASICS Could not submit job {val} into queue {val} Queue manager (qm) is not running. Restart SEP sesam services. Run sm_shutdown, then sm_startup.
E015-BASICS Missing parameters – more information with {val} The program sm_arch was called with the wrong argument Check usage with the option -h and retry running the program using the correct argument.
E016-BASICS Sesam daily startup event must not be deleted The period of validity for the NEWDAY event schedule has been set incorrectly. Check the period of validity for the NEWDAY event schedule in the SEP sesam GUI and uncheck the checkbox End. This option must be disabled so that the NEWDAY event will be repeated in perpetuity. For details on scheduling, see creating a schedule.


BREAK

Break problems

Error message Cause Solution
E001-BREAK Couldn't block queue {val} Queue manager (qm) is not running. Restart SEP sesam services. Run sm_shutdown, then sm_startup.
If you keep experiencing the problem, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E002-BREAK Couldn't start queue {val} Queue manager (qm) is not running. Restart SEP sesam services. Run sm_shutdown, then sm_startup.
If you keep experiencing the problem, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E003-BREAK Aborting by {val} at {val} failed ({val}) Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E004-BREAK Missing parameters – try sm_break -h Retry running the command using the correct sm_break parameters.
E005-BREAK Wrong input value: {val} Retry running the command using the correct sm_break -h parameters.
E006-BREAK Interrupt signal SIGINT could not be sent to process {val} Process may already have been completed. Check whether the process is still running or has been completed.


CONFDRI

Configuration drive problems

Error message Cause Solution
E001-CONFDRI Submit {val} into queue {val} failed Queue manager (qm) is not running. Restart SEP sesam services. Run sm_shutdown, then sm_startup.
If you keep experiencing the problem, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E002-CONFDRI Error during activating the SesamMultiplexStream dataserver The Sesam Multiplex Stream (SMS) Server is not running. Reload the SMS Server by running the sm_main reload command.
E003-CONFDRI Automatic hardware setup and configuration finished with failure. Please take a look into daily protocol errors 1. Use the GUI to configure the loaders and drives.
2. If you keep experiencing the problem, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.


CONFLOA

Configuration loader problems

Error message Cause Solution
E001-CONFLOA Could not find out the status of filling of loader Problem associated with a newly installed loader. 1. Check the cable connection to the loader, or
2. Use the SEP sesam loader utility (slu) for managing loaders and tapes: run a slu scan command from CLI.
E002-CONFLOA Could not find out the drives of loader {val}: {val} Problem associated with a newly installed loader. 1. Check the cable connection to the loader, or
2. Use the SEP sesam loader utility (slu) for managing loaders and tapes: run a slu scan command from CLI.
E003-CONFLOA Could not find out the initial contents of loader: {val} Problem associated with a newly installed loader. 1. Check the cable connection to the loader, or
2. Use the SEP sesam loader utility (slu) for managing loaders and tapes: run a slu scan command from CLI.


DATABAS

Database problems

Error message Cause Solution
E001-DATABAS Failure during access to database: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E002-DATABAS DB_SEL_FIRST {val}: cannot allocate memory Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E003-DATABAS DB_SEL_ALLOC {val}: the recordlist is empty, cannot allocate a new element Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E004-DATABAS DB SEL_ALLOC fvalg: cannot allocate memory The file system may be full. Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E005-DATABAS {val} could not find column {val} within record Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E006-DATABAS {val}: empty recordlist, cannot catch requested data Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E007-DATABAS Unexpected NULL value Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E008-DATABAS CONVERT_DATE_TIME: wrong parameter {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E009-DATABAS OA MAKE DB_REC_LIS {val}: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E010-DATABAS OA MAKE DB REC LIS {val}: too many columns ( max {val} ) Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E011-DATABAS {val} {val}: cannot allocate memory ( {val} Bytes) Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E012-DATABAS {val} SQL pipe doesn't return the expected characters Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E013-DATABAS {val} {val}: error during opening a pipe Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E014-DATABAS OA_DO_SQL {val}: error from SQLcommand: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E015-DATABAS OA_DO_SQL {val]: error from DAMISQL: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E016-DATABAS {val} PSQL doesn't create output Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E017-DATABAS {val} {val}: too many columns Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E018-DATABAS {val} with unexpected result: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E019-DATABAS Invalid date in table results: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.


DRIVES

Problems with drives

Error message Cause Solution
E001-DRIVES Wrong media {val} during attempt to mount on drive {val} 1. Change the media manually or with a loader, or
2. Check the media labels (archive adjustment) or run a sm_drive command.
E002-DRIVES Could not read label from media in drive {val} 1. The Sesam Multiplex Stream (SMS) Server is not running, or
2. The media are defective.
1. Restart SEP sesam services. Run sm_shutdown, then sm_startup, or
2. Replace the defective media.
E003-DRIVES Drive {val} currently not online( {val} ) 1. Change the media manually or with a loader, or
2. Check the media labels (archive adjustment) or run a sm_drive command.
E004-DRIVES gv_ro_sms not yet defined (please check INI and restart) Restart SEP sesam services. Run sm_shutdown, then sm_startup.
E005-DRIVES SMS could not find label on media 1. Change the media manually or with a loader, or
2. Check the media labels (archive adjustment) or run a sm_drive command.
E006-DRIVES SMS in not allowed state Restart SEP sesam services. Run sm_shutdown, then sm_startup.
E007-DRIVES The pipes of SMS aren't running – please restart SMS Restart the Sesam Multiplex Stream (SMS) Server. Run sm_main reload sms.
E008-DRIVES Error from login to SMS Restart the Sesam Multiplex Stream (SMS) Server. Run sm_main reload sms.
E009-DRIVES message: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E010-DRIVES Error from initialising the media in drive {val}: {val}.{val} 1. Change the media manually or with a loader, or
2. Check the media labels (archive adjustment) or run a sm_drive command.


HOSTS

Problems with the host computer

Error message Cause Solution
E001-HOSTS Configuration of {val} backup client {val} completed with errors Verify the connectivity to the client and check for further error messages about this problem.
E002-HOSTS There is no access to computer {val} – please configure it now for {val} Check whether the SEP sesam Client is installed on the host and if the SEP sesam daemon is running. For details, see How can I verify that the SEP sesam server has full access to a specific client.
E003-HOSTS Error message:{val} Check for further error messages about this problem.
E004-HOSTS Error during access to database ({val}) Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E005-HOSTS cannot open local file {val} to insert SESAM server computer Check the local file system and the paths in the config file <SESAM_VAR>/var/ini/sm.ini.
E006-HOSTS Missing parameters for configuration of a client The sm_config_client appears to have been called with the wrong arguments. Run sm_config_client -h to check usage.
E007-HOSTS There is still no SESAM client software installed on computer {val} – please do it now 1. Install the SEP sesam Client on the computer, or
2. Verify that the SEP sesam daemon is running on the client computer, or
3. Check the connectivity to the client, or
4. Check the firewall settings.
E008-HOSTS SESAM computer is still not configured – please do it now first Check the database entry for the SEP sesam host: sql "select * from clients where client_id=0".
E009-HOSTS Couldn't find computer \"{val}\" within net ( perhaps name typing error? test with \'ping\') 1. Check your name resolution for the given host name, or
2. Check the connectivity.
E010-HOSTS SESAM client on {val} not yet started – for what to do see Day Protocol 1. Install the SEP sesam Client on the computer, or
2. Verify that the SEP sesam daemon is running on the client computer, or
3. Check the connectivity to the client, or
4. Check the firewall settings.
E011-HOSTS Missing permit – please insert [{val}] into {val}:../var/ini/sm_ctrld.auth Check that the SEP sesam Server has full access to a specific client. Run the command sm_setup set_client {Sesam_Server}.
E012-HOSTS Backup from {val} not possible. Check for further error messages about this problem.
E013-HOSTS Backup from {val} cannot return to {val} – please check ( ping, DNS, local STPD ) 1. Check the connectivity to the client, or
2. Check the firewall settings, especially for the STPD port.
E013-HOSTS Could not find computer {val} in database: {val} The given hostname cannot be found in the SEP sesam database. This error message should only arise if the wrong hostname was given in the CLI. Check your name resolution for the given host name (DNS or etc/hosts file).
E014-HOSTS RemoteCmd {val} > error: {val} 1. Check whether the SEP sesam Client is installed on the host, or
2. Verify that the SEP sesam daemon is running on the client computer, or
3. Check the connectivity to the client, or
4. Check the firewall settings,or
5. Check that the SEP sesam Server has full access to a specific client. Run the command sm_setup set_client {Sesam_Server}.
E015-HOSTS RemoteCopy error reading from {val} ( num.{val}): {val} 1. Check whether the SEP sesam Client is installed on the host, or
2. Verify that the SEP sesam daemon is running on the client computer, or
3. Check the connectivity to the client, or
4. Check the firewall settings,or
5. Check that the SEP sesam Server has full access to a specific client. Run the command sm_setup set_client {Sesam_Server}.
E016-HOSTS RemoteCopy {val} {val} {val} -> {val}: error at {val} 1. Check whether the SEP sesam Client is installed on the host, or
2. Verify that the SEP sesam daemon is running on the client computer, or
3. Check the connectivity to the client, or
4. Check the firewall settings,or
5. Check that the SEP sesam Server has full access to a specific client. Run the command sm_setup set_client {Sesam_Server}.
E017-HOSTS RemoteCopy {val} {val} {val} -> {val}: {val} 1. Check whether the SEP sesam Client is installed on the host, or
2. Verify that the SEP sesam daemon is running on the client computer, or
3. Check the connectivity to the client, or
4. Check the firewall settings,or
5. Check that the SEP sesam Server has full access to a specific client. Run the command sm_setup set_client {Sesam_Server}.
E018-HOSTS RemoteCopy {val}: invalid mode: {val} This error message should generally not appear. Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E019-HOSTS RemoteCmd {val} > invalid accessmode - {val} This error message should generally not appear. Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E020-HOSTS Computer {val} is currently not reachable 1. Check whether the SEP sesam Client is installed on the host, or
2. Verify that the SEP sesam daemon is running on the client computer, or
3. Check the connectivity to the client, or
4. Check the firewall settings,or
5. Check that the SEP sesam Server has full access to a specific client. Run the command sm_setup set_client {Sesam_Server}.


LOADERS

Problems with loaders

Error message Cause Solution
E001-LOADERS Action {val} of loader {val} failed There is a problem at the loader. 1. Check the cable connection, or
2. Run a slu scan to check SCSI access.
The loader could be switched off for a short time.
E002-LOADERS Action {val} of loader {val} failed: {val} 1. Check the loader's slot and drive movements, or
2. Check whether the loader auto-unloads the drives. If it does, set the value in the loader properties, or
3. Check the cable connection, or
4. Run a slu scan to check SCSI access.
The loader could be switched off for a short time.
E003-LOADERS The specified destination slot {val} of loader {val} is occupied Attempting to unload to an occupied slot. 1. If necessary, check and fix the slot info in the archive, or
2. Run an media labels (archive adjustment) if making manual changes in the loader.
E004-LOADERS Attention: Loader {val} is auto unloading! Auto unload will now be activated! The configuration will be updated automatically. No further action is required.
This error should not appear multiple times. If it does, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E005-LOADERS Attention: Internal drive number of drive {val} ({val}) not found in loader {val}! Please check your drive configuration If necessary, check and fix the loader configuration: set the loader number (loader_num) and correct the internal drive number (loader_drive) for the selected drive (table hw_drives).
E006-LOADERS Attention: {val} {val} not found in loader {val}! Please check your configuration 1. If the argument was called in the CLI, check your arguments, or
2. Check the cable connection, or
3. Run a slu scan to check SCSI access.
The loader could be switched off for a short time.
E007-LOADERS Invalid Control Software {val} – only DIR_SLU permitted This error should not appear. Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E008-LOADERS Error when creating the SHOW LIST (sm_slu) 1. Check the cable connection, or
2. Run a slu scan to check SCSI access.
The loader could be switched off for a short time.
E009-LOADERS Invalid loader function {val} – only E,I,L,U,S available This error should only appear if the argument was called in the CLI. Check the first argument function (check usage: sm_loader -h).
E010-LOADERS Invalid slot number {val} – there are max. {val} This error should only appear if the argument was called in the CLI. Use the sm_loader -s {slot_number} (check usage: sm_loader -h).


MEDIA

Problems with media

Error message Cause Solution
E001-MEDIA {val} error: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E002-MEDIA Error from submitting {val} into queue {val} Queue manager (qm) is not running. Restart SEP sesam services. Run sm_shutdown, then sm_startup.
E003-MEDIA Error when loading media from slot {val} Error from EXXX-LOADERS
E004-MEDIA Label including wildcards [{val}] could not be converted to a valid Sesam label 1. Check the label with wildcards, for example, %u and set the correct wildcards.
See the Unix man page man strftime(3).
E005-MEDIA Archive action {val} completed with error: {val} Check for further error messages about this problem.
E006-MEDIA Archive action {val} completed with error – unknown EXIT code: {val} 1. Check for further error messages about this problem.
2. If you keep experiencing the problem, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E007-MEDIA No media of pool {val} available 1. If a loader is present, check whether the media in the loader are EOL-restricted. Add EOL-free media to the loader and run an archive adjustment, or
2. If no loader is present, check whether the media in the loader are EOL-restricted, or
3. Reduce the EOL restriction of some of the media, add media to media pool and, if applicable, reduce the EOL of the media pool as well.
E008-MEDIA All media of pool {val} with EOL restriction 1. If a loader is present, check whether the media in the loader are EOL-restricted. Add EOL-free media to the loader and run an archive adjustment, or
2. If no loader is present, check whether the media in the loader are EOL-restricted, or
3. Reduce the EOL restriction of some of the media, add media to media pool and, if applicable, reduce the EOL of the media pool as well.
E009-MEDIA All EOL free media of pool {val} are loaded in other drives 1. If a loader is present, check whether the media in the loader are EOL-restricted. Add EOL-free media to the loader and run an archive adjustment, or
2. If no loader is present, check whether the media in the loader are EOL-restricted, or
3. Reduce the EOL restriction of some of the media, add media to media pool and, if applicable, reduce the EOL of the media pool as well, or
4. Unload any other drives, if applicable.
E010-MEDIA Loaded media {val} is not identical to requested media {val} Check for further error messages about this problem.
E011-MEDIA Media action 'closetape' failed: {val} Check for further error messages about this problem.


RECOVER

Disaster recovery problems

Error message Cause Solution
E001-RECOVER Couldn't start {val} : {val} 1. If recovery was called in the CLI, check your arguments by using sm_recover -h, or
2. Check for further error messages about this problem.
E002-RECOVER Loading of media {val} failed ({val}) – signal restore to break Check for further error messages about this problem.
E003-RECOVER Error during copying files from save set {val} on media {val} to {val} (see {val}) Check for further error messages about this problem.
E004-RECOVER Error during creating listing of files in save set {val} on media {val} Check for further error messages about this problem.
E005-RECOVER Error during inserting media with label {val} into archive 1. Check the SQL insert statement
2. Check for further error messages about this problem.
E006-RECOVER Error during inserting media-pool {val} into database 1. Check the SQL insert statement
2. Check for further error messages about this problem.
E007-RECOVER Missing label in EOM-signal ({val}) The label information is missing from the tape trailer. Try to restore a full SESAM_BACKUP from backup media to get a SEP sesam database with complete media label information.


RESTORE

Restore problems

Error message Cause Solution
E001-RESTORE LIS_DB > {val} 1. If restore was called in the CLI, check your arguments by using sm_restore -h, or
2. Check for further error messages about this problem.
If you keep experiencing the problem, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E002-RESTORE Restore task {val} not yet defined – please do it now 1. If restore was called in the CLI, check your arguments by using sm_restore -h, or
2. If you keep experiencing the problem, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E003-RESTORE Restore {val} completed with errors: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E005-RESTORE Selective generations restore cannot allocate memory ( {val} ) Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E006-RESTORE SEARCH_LIS {val} is an invalid name of task 1. If restore was called in the CLI, check your arguments by using sm_restore -h, or
2. If you keep experiencing the problem, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E007-RESTORE Error in {val}-activities: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.


SBC_COM

SEP sesam communication with external backups

Error message Cause Solution
E000-SBC_COM Wrong parameter Use the correct sm sbc com -h
E001-SBC_COM Wrong number of parameters Use the correct sm sbc com -h
E002-SBC_COM Missing or wrong mandatory task The name of the task has not been specified. Specify the task name.
E003-SBC_COM Failure selecting from database table Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E004-SBC_COM Missing mandatory label, media pool or drive number Correct the mandatory input.
E005-SBC_COM FIND_DRIVES_OF_POOL no drives for pool {val} configured Complete the media pool configuration in the GUI.
E006-SBC_COM A session {val} was not connected before Open an external session first.
E007-SBC_COM Missing mandatory save set identifier Correct the mandatory input.
E008-SBC_COM GET_SEGM_AND_OFFSETS could not find selected file {val} in save set {val} Correct the filename.
E009-SBC_COM GET_SEGM_AND_OFFSETS wrong format in line [{val}] Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E010-SBC_COM The entered tapeserver {val} is invalid for drive {val} (see drive properties) Check the configuration on the RDS Server and drives.
E011-SBC_COM Wrong parameter -s {val}: we need savesetname@starting-time as returned from Open Restore Use the savesetname@starting-time as returned from open restore.
E012-SBC_COM Couldn't get node of drive {val} – please check drive's properties Check the selected drive. Change the external setting to another drive or omit the drive number setting.
E013-SBC_COM Restore not possible, bcs. backup {val} was not successful Restore from another save set of the same backup task that finished successfully.
E014-SBC_COM INQUIRE_INFO wrong type Use the correct sm sbc com -h-
E015-SBC_COM INQUIRE_INFO save set {val} doesn't exist Use another save set of the same task.
E016-SBC_COM INQUIRE_INFO cannot open listing file {val} of save set {val} to read Check syntax for errors.
E017-SBC_COM Submit sm_sbc_com_ext failed, Saveset Check for further error messages about this problem.
E018-SBC_COM Failure updating database table Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E019-SBC_COM CONNECT_BACKUP loading media {val} into drive {val} failed Check error from EXXX-LOADERS.
E020-SBC_COM LOTUS_SAVESET there's no save set containing file {val} Use another save set of the same task.
E021-SBC_COM Task {val} has Backup Type {val} but requested Type is {val} Use a different task identifier with the corresponding external task backup type.
E022-SBC_COM Medium {val} is currently not available If the medium is being used elsewhere:
1. Wait until the medium is free, or
2. Terminate the other action.
3. Unload the other drive.

If the medium is not present in loader:
Fill the loader and run an archive adjustment.

E023-SBC_COM Task {val} not yet configured 1. Check whether the external backup task is using the correct task identifier, or
2. Add the missing task.
E024-SBC_COM Pool {val} does not exist Check whether the correct external backup pool is being used. Change the external backup pool or add media pool and some media.
E030-SBC_COM Failure in file copy {val} {val} Check for further error messages about this problem.


SEPULER

Messages of the SEP sesam Scheduler

Error message Cause Solution
E001-SEPULER Error from initialisation of queue {val} (type {val}) Queue manager (qm) is not running. Restart SEP sesam services. Run sm_shutdown, then sm_startup.
E002-SEPULER Error from submitting {val} into queue {val} (type {val}) 1. Check the result of the sm_config_drives and restart the sm_config_drives, or
2. Restart SEP sesam services. Run sm_shutdown, then sm_startup.
E003-SEPULER Duplication of primary key in DB:results Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E005-SEPULER invalid command: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E006-SEPULER Restoretask {val} not yet defined – please do it now Configure the restore task in the restore wizard.
E007-SEPULER READ_INI sent error {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E007-SEPULER There is no drive group attached to media pool {val} Set the correct drive group for the media pool using drives in GUI or sm_cmd in CLI.
E008-SEPULER There are no drives attached to drive group {val} 1. Select a different group or drive, or
2. Change your hardware configuration.
E009-SEPULER String overflow: {val} --> {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E010-SEPULER Wrong type of schedule cycle: {val} Select a different schedule cycle.
E011-SEPULER Error happened during calculation of user defined list for schedule {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E012-SEPULER Calculating next execution for schedule {val} returns always the same time Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.


Other error messages

Error message Cause Solution
E006-COPY Copy of save set {val} failed! Check for further error messages about this problem.
E008-COPY Copy of save sets {val} failed: {val} Check for further error messages about this problem.
E001-GETVOL Request for media {val} completed with error: {val} 1. Change the media manually or with a loader, or
2. Check the media label (archive adjustment) or execute media event with another label to try a different media, or
3. Check for further error messages. If you keep experiencing the problem, contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.
E001-START Drive is not available ({val}) Correct the drive configuration.
E002-START Drive {val} does not exist ({val}) Correct the drive configuration.
E001-STARTAL Date unknown, please restart NEWDAY Restart SEP sesam services. Run sm_shutdown, then sm_startup.
E001-STARTUP Directory {val} not found! A problem occurred after installation. Create the required directory manually.
E001-WATCH Received performance data with invalid format: {val} 1. If the message appears only temporarily, check the network connection between the SEP sesam Server and the RDS, or
2. If the RDS is not running, restart it by running sm_startup or sm_main reload sms.
E002-WATCH EOM completed with error: {val} Contact SEP sesam support. Follow the procedure described in the section Before contacting support and attach the log file(s) to your email message.

See also

Troubleshooting Guide

FAQ