|
Product: StorageExpress™ Backup Server
E1000 - Failed to initialize process, [error desc]
Problem
The APROCESS.NLM had a problem connecting to the host server, or
getting a job from the queue.
Resolution
Unload and reload ARCSERVE.NLM and try to submit a test job. If
the error persists, reinstall ARCserve.
E1002 - Failed to examine state semaphore, [error code]
Resolution
Check the NetWare error code.
1. If the server is loading CONLOG.NLM from the AUTOEXEC.NCF,
remove the LOAD CONLOG statement from the AUTOEXEC.NCF.
2. Unload and reload ARCserve by typing ASTOP and ASTART at the
server.
E1006 - Failed to contact tape server - no I/O buffer
Problem
There is not enough memory available in the server to completely
initialize ARCserve
Resolution
See Checking the File Server's Memory Status
E1006 Failed to Contact Tape Server - No I/O Buffers
Problem
An E1006 error is generated when TAPESVR.NLM attempts to start a
job. There appears to be plenty of memory at the server.
Resolution
If the user has installed a 32-bit or non-DMA SCSI adapter, add
USEABOVE16 to the board driver and TAPESVR load lines. If the user
has installed a 16-bit or DMA SCSI adapter, add Set Reserved
Buffers below 16 meg = X (where x=200 for NetWare 3.11 or 300 for
NetWare 3.12 or 4.x) to the STARTUP.NCF file and reboot the server.
E1007 - Failed to contact tape server - group [group name] is busy
E1008 - Failed to contact tape server - group [group name] not found
E1009 - Failed to contact tape server - communication error
Problem
This error is caused by one or more of the following:
1. The tape group doesn't exist (for E1008).
2. There is a problem connecting across the network.
3. There is not enough server memory for ARCserve to function
properly.
Resolution
For each of the causes check the following:
1. Make sure that the tape group exists. Do this in one of the
following ways:
a) At the Tape Manager Menu on the file server console, select
"Configuration" and then "Group." See if the group name(s) here
match(es) the one in the error message.
b) In the Device Management screen of the ARCserve Manager, see if
the group name associated with the tape drive's SCSI ID matches the
one in the error message. If the group names do not match, then it
is possible that someone has changed them since the job was
created. Either create a new job or change the group name back to
what it was when the job was created.
2.
a) Check for the existence of the remote file server (using the
SLIST command).
b) Check the communications path to the server at all layers. This
may include cabling, bridges, routers, etc.
c) Make sure that the LAN driver revisions being used are up to
date.
d) Check the LAN cards. If the problems are consistent, it might
be necessary to replace the LAN cards and drivers on both servers
with those from a different vendor.
3. See Checking the File Server's Memory Status
E1010 - Failed to initialize database to begin merging tape [tape name]
sequence [number] (random [error code]) session [number], [error code]
E1011 - Failed to close database session for merging tape [tape name]
session [number], [error code]
E1071 - Failed to get Auto Pilot Job's Tape set, [error code]
E1074 - Invalid target name returned from asdb
E1076 - Failed to get number of permanent tapes, [error code]
E1081 - Failed to query database for tape to be recycled, [error code]
Problem
There is a problem with the ARCserve databases.
Resolution
Look in the ARCserve Activity Log for an error message mentioning
Btrieve or any of the ARCserve database filenames (AS*.DB). See
the entry for that error message for resolutions.
See also Repairing the ARCserve Databases
See also Btrieve Status Codes and Messages
E1081 Failed To Query Database, 3
Problem
Error message E1081 Failed to Query Database, 3 is received when an
Auto Pilot Job in the queue goes active.
Resolution
Check the ARCserve databases for corruption. The Auto Pilot
operation logic relies heavily on the integrity of the ASTAPE.DB
and ASTPSES.DB databases. If the databases are corrupted, the user
should repair them rather than replacing them with empty database
templates. Once the databases are repaired, check the Tape List
Database and verify that the Auto Pilot Rotation is correct. If
the user is erasing tapes each night, have them delete the old
tapes from the Tape List Database until the rotation is properly in
synch. The number of tapes in the Auto Pilot Pool (Daily, Weekly &
Monthly) should have no effect on the integrity of the database,
but the possibility of corruption increases with a larger number of
tapes.
E1081 Failed to Scan File .OU=xxxx.O=xxxxx (size: 0), 2
Problem
An E1081 Failed to Scan File .OU=xxxx.O=xxxx error is generated in
the activity log right after backing up the ARCserve database. The
backup operation is successful.
Resolution
The problem is resolved as a result of issuing the SET UPGRADE LOW
PRIORITY THREADS = ON command.
E1001 - Cannot continue with tape driver's read/write process, [error
desc]
E1013 - Failed to get function list from tape driver, [error code]
E1014 - Failed to format tape [tape name], [error code]
E1015 - Failed to read tape header - [error message]
E1016 - Failed to position tape, [error code]
E1017 - Failed to repair incomplete session [session number], [error
code]
E1019 - Failed to space filemark (request=[# filemarks] actual=[#
filemarks]), [error desc]
E1020 - Failed to detect continuation block
E1021 - Failed to read continuation block
E1022 - Invalid continuation block, signature=[signature]
E1024 - Failed to contact tape server, [error code]
E1025 - Invalid VT signature: [signature]
E1026 - Failed to space to end of data, [error message]
E1028 - Failed to update volume table
E1033 - Failed to access tape
E1034 - Failed to access tape [tape name] sequence [number] id
[number]
E1036 - Failed to write data to tape, [error code]
E1037 - Failed to write filemark - [error message]
E1038 - Failed to write tape header (tape name) Seq=[number] - [error
message]
E1039 - Failed to flush tape buffer
E1040 - Failed to write continuation block
E1043 - Failed to place end of session on tape
E1047 - Failed to align [file path] [file name] to block boundary,
[error code]
E1054 - Failed to resume daemon process, [error code]
E1055 - Failed to read session header - [error code]
E1056 - Invalid file header signature=[XXX]
E1057 - Failed to read file header
E1059 - Failed to space end of data, [error desc]
E1060 - Failed to read volume table from tape, [error desc]
E1067 - Failed to reverse [number] file marks, [error desc]
E1069 - Failed to reverse [number] block, [error desc]
Problem
All of the above errors may occur due to one or more of the
following causes. Refer to the error code or description for more
information about the exact error that occurred.
1. There is no tape in the drive
2. Media error
3. Hardware error
Resolution
For each of the causes, check the following:
1. Check to see if there is a tape properly loaded in the drive.
2. Check to see if the tape is damaged.
3. See Tape Drive Troubleshooting Checklist.
4. See Tape Server Internal Error Codes.
E1024 Failed to contact tape server, [error code].
Problem
This is usually due to a memory problem or a connection problem.
Resolution
See E1007.
E1018 - Failed to locate tape [tape name], [error code]
Problem
An incorrect tape name has been specified in the job setup.
Resolution
Check that the tape in the drive has the same name as that
specified by the job.
E1023 - Failed to locate volume table, [error code]
Problem
This error occurs due to one of the following:
1. The power to the tape drive was interrupted during the job.
2. You are using a drive that has not been certified by Cheyenne
Software.
Resolution
For each of the causes, check the following:
1. The power may be (or may have been) turned off, and the session
may not be properly terminated. Check the power supply to the
drive and run the job again.
2. Check to see if the drive is Cheyenne-certified.
3. See Tape Drive Troubleshooting Checklist.
E1027 - Failed to read block number, [error message]
Problem
This error occurs due to one of the following:
1. The tape in the drive is damaged or defective.
2. ARCserve is being run withy a drive that has not been certified
by Cheyenne Software.
Resolution
For each of the causes, check the following:
1. Run the job with a different tape, preferably a new one.
2. Check to see if the tape drive is Cheyenne-certified.
E1029 - Failed to space chunk <offset> for QFA operation
Problem 1
The error can occur due to inaccurate offset numbers in the
database.
Resolution 1
Merge the tape into the database. This will overwrite the old
offset number information. If any other database errors occur with
this one, see Repairing the ARCserve Databases.
Problem 2
The error can also occur if the tapedrive has a problem executing
the SPACE command.
Resolution 2
A replacement TAPESVR.NLM that resolves this problem is available
from the Cheyenne online services in a file called ECN097.ZIP. See
also Tape Drive Troubleshooting Checklist.
E1031 - Failed to locate [tape name]'s session [number] req=[number]
actual=[number]
E1032 - Failed to locate [tape name]'s session [number] @ block
[number], [error message]
E1041 - Failed to locate session [number]
Symptom
The tape name, session number or sequence specified in the job
form is invalid.
Resolution
Check that the tape name, session number and sequence specified
while creating the job are valid for the tape that is in the drive.
If they are, then there is a problem reading the tape. See Tape
Drive Troubleshooting Checklist.
E1045 - Failed to spawn [tape name], [error code]
Problem
This error occurs due to one or more of the following:
1. The specified NLM is corrupted or does not exist.
2. The search path is not set properly at the file server.
3. There is not enough memory to load the specified NLM.
4. The Secure Console command has been entered at the file server.
5. In a NetWare 4.x or Full SMS environment, SMDR.NLM and/or the
appropriate TSAs have not been loaded.
Resolution
For each of the causes, check the following:
1. Make sure that the specified NLM exists in the appropriate
directory.
2. Check that a search path to the appropriate directory has been
specified at the server. (Type SEARCH at the file server console
prompt).
3. See Checking the File Server Memory Status.
4. See Running ARCserve under SECURE CONSOLE.
5. Load SMDR.NLM and the appropriate TSAs for the NetWare version
running on the server.
E1046 - Error reading [file path] [file name] - [error message],
[number] vs [number] fd=[error code] fsz=[number]
Problem
A read error on the source drive occurred during backup. At the
beginning of every backup job, ARCserve does an estimate pass of
the Source drives, reading their files to determine the total
number of files and kilobytes to be backed up. This error message
indicates that the specified file has changed significantly between
the first time that ARCserve read it (during the Estimate) and the
actual backup of the file.
Resolution
There are many server and workstation processes that automatically
create, modify and/or delete files on the drives. Very often, this
error occurs when a temporary file is detected during the Estimate
pass that has been modified or deleted by the time the actual
Backup occurs, in which case the error message can be ignored.
Particularly susceptible to this are Email and print queue files.
The possibility of this increases when there is activity on the
network while the ARCserve job is running. Check to see if the
specified file still exists in the specified directory. If the
file does still exist and is not a file that should change (such as
an EXE), it may have become corrupted.
TECHNOTE: Field Descriptions for E1046 - Error reading [file path]
[file name] - [error message], [number] vs [number] fd=[error code]
fsz=[number]
Error reading path: This indicates that APROCESS.NLM has failed to
read a file. [File path] [File name]: This is the path and file
name that APROCESS.NLM has failed to read. [error message]: This
is an attempt to translate the error code returned by the (2nd)
[number] field. (1st) [number]: This is the number of bytes that
APROCESS.NLM expects to read. (2nd) [number]: This is a return
code for a open file call. A code of -1 would indicate that the
file is in use. fd = x: The value fd returns is the file handle
number that NetWare assigns to the file open call that APROCESS.NLM
made. fsz = x: This is the current file size.
E1048 - Failed to initialize job record (owner name), [job type], [set
name] [error code]
E1049 - Failed to update job record (owner name), [job type], [set
name], [error code]
Problem
The ARCserve Database Manager has not been notified that ARCserve
is going to begin or end a job.
Resolution
This error indicates the existence of a database problem. Check
the ARCserve Activity Log for error messages mentioning Btrieve or
any of the ARCserve database filenames (AS*.DB). See the entry for
that error message for resolutions.
See also Repairing the ARCserve Databases
See also Btrieve Status Codes and Messages
E1050 - Failed to update daily log
Problem
ARCserve cannot update the Auto Pilot daily log due to one or more
of the following conditions:
1. The volume containing the Auto Pilot daily log is out of disk
space.
2. The user has insufficient rights to update the file.
3. The path to the log file is incorrect.
Resolution
For each of the causes, check the following:
1. Check the amount of free disk space.
2. Use SYSCON to make sure that the proper rights have been
assigned to the ARCserve home directory
3. Check the path to the daily log
E1052 Failed to access tape [tape name] sequence [number].
Problem
This error occurs due to one of the following:
1. The correct tape is not in the drive.
2. You have specified the wrong tape or sequence number.
Resolution
For each of the causes check the following:
1. Make sure the correct tape is in the drive.
2. Check the tape name and/or sequence number.
E1058 - Failed to read from tape, [controller failure]
Problem
The above error occurs randomly when performing tape operations.
Resolution
1. Verify that the Tape Server memory configuration is correct for
the SCSI adapter card. Make sure that SET RESERVED BUFFERS BELOW
16 MEG = 200 or USEABOVE16 is properly specified, where
appropriate. See also Tape Server Memory Utilization.
2. Verify user is selecting a valid session number for a restore
operation.
3. Check for a hardware and/or media problem. See Tape Drive
Troubleshooting Checklist.
4. Check the code cited after the error description for more
infomation. See Tape Server Internal Error Codes.
NOTE: If a user has the Compaq Turbodat with the 5Gb drive, see
E1058 under Compaq tapedrives.
E1058 Failed to Read From Tape - File mark Detected
Problem
User gets E1058 Failed to read from tape - File mark detected. As
per the debug log, the DAT tape drive was being treated as a Volume
Table tape drive. Therefore, the tape format used for the tape
drive was incorrect. A file mark is detected because the drive is
told to go to an incorrect position for the beginning of the
session. This will occur if the tape drive is not recognized as a
known tape drive during the initialization, since ARCserve will
default to the Volume Table format. The data on tape is still able
to be restored even though it was written to tape in a method that
is not native to the DAT tape drive.
Resolution
There is patched APROCESS.NLM available in ECN088.ZIP that has
support for a NO_VT parameter which is applied to the ARCSERVE.NLM
load line. This will position the drive differently to adjust for
the different tape formats. The patched APROCESS is written in
5.01f architechure and can be used with 5.01g, although it is not
recommended to run the patch during normal operations, only when a
restore is needed. A debug log should be obtained by tech support
to ensure that the E1058 is due to this problem before issuing the
patch.
NOTE: The ECN088.ZIP patch will allow restores to be performed from
tapes made with ARCserve versions prior to 5.01d. However, new
backup jobs should not be appended to these tapes, as there has
been a format change which could lead to session incompatibilities.
When reusing them, be sure to overwrite or erase them first.
E1061 - Failed to locate node [node name] for compare. Perform
verification.
Problem
The node could not be located for comparison, so a verification is
being performed instead.
Resolution
Make sure that the node cited is still properly configured for
communication with the ARCserve server. Check that the workstation
is turned on, that an agent is properly loaded, and that access to
the workstation is not blocked by a network broadcast message.
E1062 - Invalid session signature, [error code]
Problem
During a restore, compare or verify job, ARCserve failed to find
the next available file header from the tape
Resolution
If the tape drive being used is a QIC (Quarter Inch Tape),
retension the tape. If retensioning does not correct the problem,
eject the tape and then re-insert it. Otherwise, see Tape Drive
Troubleshooting Checklist.
E1063 - Invalid session password !!
Problem
During a restore or merge job, the session password that was
entered does not match the password on the tape.
Resolution
1. If there is a session password specified on the tape, make sure
that it has been correctly entered in the job form.
2. If there is no password specified on the tape, then check the
version of the ARCserve Manager being run. There was an issue with
versions of the ARCserve Manager prior to 5.01d in which the user
was prompted for a password when none existed. The problem was in
the ASCTP.DLL file in the 5.01 front end and it was corrected in
5.01d. Upgrading ARCserve to the latest version will resolve the
problem.
E1065 - Failed to start enumerating tape, [error desc]
Problem
ARCserve failed to get the tape list from the tape driver.
Resolution
This error indicates the existence of a database problem. Check
the ARCserve Activity Log for error messages mentioning Btrieve or
any of the ARCserve database filenames (AS*.DB). See the entry for
that error message for resolutions.
See also Repairing the ARCserve Databases
See also Btrieve Status Codes and Messages
E1066 - Failed to submit detailed record for [file name], [error desc]
Problem
ARCserve failed to submit detailed file/directory to database.
Resolution
This error indicates the existence of a database problem. Check
the ARCserve Activity Log for error messages mentioning Btrieve or
any of the ARCserve database filenames (AS*.DB). See the entry for
that error message for resolutions.
See also Repairing the ARCserve Databases
See also Btrieve Status Codes and Messages
E1068 Failed to get Scan Daemon Status
Problem
The above error was generated when the user went to run a backup
job. In addition, he also received E1036 Failed to write data to
tape and E3120 Failed to backup errors, thereby causing the backup
to fail. The scan daemon is what we send to the drive in order to
sense the mode of the tape drive to let us know what it is doing.
Resolution
The server was running an EISA SCSI adapter and had 64 megs of
memory in the server. After adding the USEABOVE16 parameter to the
ASPI50 load line in ASTART.NCF, it worked without error. (The
speculation here is that the card itself was running out of work
buffers, thereby holding up the SCSI bus and not allowing any type
of communication between the TAPESVR and ARCSERVE NLMs).
E1072 - Failed to update tape
Problem
APROCESS.NLM calls the function ClientWriteVolumeHeader from
TAPESVR.NLM. After the tape header is written, the tape server
always performs a read after write compare of the header. If the
header is not written correctly or if the data does not compare
correctly, then this error will be generated.
Resolution
The header may have failed to be written properly due to hardware
or media error. Check the Tape Server Log for any messages
indicating the problem. See also Tape Drive Troubleshooting
Checklist.
E1073 - Failed to get missed target list, [error desc]
Problem
ARCserve failed to query the database so that it can process the
targets which are missed from the regular Auto Pilot job.
Resolution
This error indicates the existence of a database problem. Check
the ARCserve Activity Log for error messages mentioning Btrieve or
any of the ARCserve database filenames (AS*.DB). See the entry for
that error message for resolutions.
See also Repairing the ARCserve Databases.
See also Btrieve Status Codes and Messages.
E1077 - Failed to get remaining space on tape, [NetWare error code]
Problem
APROCESS.NLM has called the function ClientGetTapeRemaining from
TAPESVR.NLM and the function did not complete properly, resulting
in the above error.
Resolution
The function may have failed due to a communications (IPX/SPX)
problem between the the Tape Server and ARCSERVE.NLM. Check the
Tape Server log for any SCSI error or Timeout problems. See also
Tape Drive Troubleshooting Checklist for possible hardware
problems.
E1078 - Failed to enumerate next tape, [error code]
Problem
ARCserve failed to find the tape list from the tape driver.
Resolution
Check the Tape Server Log for any SCSI errors or Timeout problems.
See also Tape Drive Troubleshooting Checklist for possible hardware
problems.
E1079 - Failed to create screen [NLM name]
Problem
There is not enough server memory available to create a screen.
Resolution
See Checking the File Server's Memory Status.
This applies to:
|
