|
Product: StorageExpress™ Backup Server
E4001, E4002, E4003, E4004, E4005, E4007, E4021, E4101, E4102, E4103,
E4104, E4106, E4109, E4112, E4113, E4114, E4115, E4201, E4203, E4204,
E4205, E4206, E4207,
E4001 - Message Index out of bound [index number] (max=[maximum index
number]), m, programMesgIndex
Problem
The message index number is out of range. This indicates either
that the version of the message file (*.MSG) does not match that of
the NLM it is interacting with or that the message file has become
corrupted.
Resolution
An incorrect version of a message file is an indication of an
improper or incomplete ARCserve installation or upgrade. If this
is the case, it is recommended that ARCserve be reinstalled (or the
most recently applied upgrade be reapplied). It is not necessary
to overwrite the Job Queue or the ARCserve databases during this
process. If a single message file has become corrupted, it can
also be replaced with a new copy of the file from the ARCserve
install disks (using the Microsoft* EXPAND utility).
E4002 - Failed to read message file [file name],path
E4004 - Failed to read message file, request=[size requested]
actual=[actual size] bufSize, ret
E4007 - Unable to access ARCserve home directory [path name]
Problem
ARCserve could not access the specified file or directory due to
one or more of the following reasons:
1. The rights of the user account created the ARCserve installation
process have been altered.
2. The specified file has been damaged or deleted.
Resolution
For each of the causes, check the following:
1. All user accounts created and NetWare properties set by the
ARCserve installation process should not be manually altered. The
ARCserve user is called CHEY_ARCHSVR for NetWare* 3.1x and
AQ_<servername> for NetWare 4.x. If the accounts cannot be
returned to their original state, the ARCserve user and queue
should be recreated or ARCserve reinstalled. See Recreating the
ARCserve Job Queue.
2. Check to ensure that the specified file exists on the path
specified. If it does not, it may be copied from the ARCserve
install disk (using the Microsoft EXPAND utility) or ARCserve may
be reinstalled.
E4003 - Failed to allocate message buffer
E4115 - Failed to allocate \[object name]\ ([Number] bytes)
E4204 - Failed to allocate memory for [object name]
Problem
There was insufficient memory on the ARCserve server to perform a
required operation.
Resolution
See Checking the File Server's Memory Status.
E4005 Too many [number] messages, MAX MESSAGE.
Resolution:
Contact your reseller or Cheyenne Technical Support.
E4021 Failed to Parse Entity, 9.
Solution:
This could be caused by an unprintable character on the ZONE name,
or some workstation doesn't have machine name. Check with user for
zonelist and do a lookup test.
E4101 - Failed to update[database] record id=[record id],
status=[Btrieve error code]
E4102 - Failed to insert [database] record, status =[Btrieve error code]
E4203 - Failed to initialize [database name] database
Problem
The ARCserve databases have been corrupted.
Resolution
Check the Btrieve error code specified and look in the ARCserve
Activity Log for other error messages that mention Btrieve or the
ARCserve database files (AS*.DB).
E4103 - [CLIENTS] Failed to Create Activity Log File
E4201 - Failed to create activity log file:[file name]
Problem
This error is due to one of the following:
1. There was insufficient disk space on the ARCserve host volume
to create the log file.
2. The rights of the ARCserve user account have been altered.
Resolution
For each of the causes check the following:
1. Free up disk space on the ARCserve host volume. See TECHNOTE:
ARCserve and File Server Disk Space.
2. All user accounts created and NetWare properties set by the
ARCserve installation process should not be manually altered. The
ARCserve user is called CHEY_ARCHSVR for NetWare 3.1x and
AQ_<servername> for NetWare 4.x. If the accounts cannot be
returned to their original state, the ARCserve user and queue
should be recreated or ARCserve reinstalled. See Recreating the
ARCserve Job Queue.
E4104 - Failed to establish connection with [network address]-[node
address], [error code], connSave: [NetWare error codes]
E4106 - Failed to query local IPX address, [NetWare error code]
Problem
The ARCserve server could not make contact with the specified
workstation.
Resolution
Make sure that the workstation is powered on, that the proper agent
and network drivers are loaded for the environment, and that access
to the workstation is not blocked by a network broadcast message.
See also Network Communications Troubleshooting Checklist.
E4109: Failed to receive IPX packet, [error code]
Error codes:
FA = No known route to destination
FC = The request canceled
FD = Packet overflow
FE = Timeout failure/Bad packet
FF = Socket closed/Hardware failure
Problem
In ARCserve versions 5.0 and 5.0a, if a file server has more than 4
LAN cards or channels active, CLIENTS.NLM will generate the above
error and unload itself.
Resolution
Upgrade ARCserve to version 5.01 or later. The CLIENTS.NLM
included with this release can handle up to 8 LAN cards or
channels. If the problem persists, see Network Communications
Troubleshooting Checklist.
E4112 - Failed to query router address for [workstation address],
[NetWare error code]
Problem
There is a network communications problem.
Resolution
See Network Communications Troubleshooting Checklist.
E4113 - Failed to load NLM [NLM name], [NetWare error code]
Problem
Either the specified NLM does not exist on the path given, or there
is not enough memory available on the ARCserve server to load the
NLM.
Solution
Make sure that the specified NLM exists on the path given. See
Checking the File Server's Memory Status.
E4114 Failed to make file server list.
Description:
This is an internal error.
Resolution:
ARCserve is trying to make a list of all the file servers on the
network. If it fails to make this list, check the LAN card. If
you are still unsure, contact your reseller or Cheyenne's Technical
Support.
E4202 Failed to find ([tape name], [seq. number],[id]) tape record.
Description:
The tape isn't in the database.
Solution:
Eject the tape and re-insert into the drive. ARCserve will make an
entry into its database for this tape.
E4205: Failed on Integrity Check (filename.db) (error #)
Problem
The database file has become corrupt. This error is normally
received after an ASTART is issued at the server console. When
ASDB.NLM attempts to open the ARCserve Database, it may detect
corruption.
Resolution
Follow the steps to Repair a Corrupt Database. The recovery
procedure should be performed for all database files. The error
may only be citing one *.DB file, but since a Btrieve Database is
indexed and all database files share information, the possibility
that another database file contains corruption is high.
See also Btrieve Status Codes and Messages.
E4206 - Disk is full
Problem
There is insufficient disk space available on the ARCserve host
volume.
Solution
Free up disk space on the ARCserve host volume. See also TECHNOTE:
ARCserve and File Server Disk Space.
E4207 - Failed to create FTS Daemon [Btrieve error]. No FTS history
will be saved.
Problem
A required ARCserve database function could not be initiated for
one of the following reasons:
1. The database file ASTPSDAT.DB has been corrupted.
2. There is not enough memory available on the ARCserve server.
Solution
1. See Repairing the ARCserve Databases.
2. See Checking the File Server's Memory Status.
This applies to:
|
