|
Product: StorageExpress™ Backup Server
E5000, E5001, E5002, E5003, E5004, E5005, E5006, E5007, E5008, E5011,
E5012, E5013, E5018, E5019, E5023, E5027, E5029, E5031, E5035, E5039,
E5040, E5041, E5042, E5043, E5044, E5048, E5049, E5050, E5051, E5052,
E5053, E5055, E5058,
E5000 - Failed to connect to workstation - Is Agent loaded?
Problem
The workstation Agent is not loaded, or the workstation is blocked
by a network broadcast message.
Resolution
Load the appropriate Agent. Use CASTOFF ALL to block broadcast
messages to the workstation. Or, at the server console, in
ARCserve's Configuration screen, turn on the Turn off all messages
to workstation option to prevent ARCserve from sending any
broadcast messages.
E5001 - Failed to establish connection with WS @ [network #], [node
address]
Problem
The workstation Agent is not loaded, or the workstation is blocked
by a network broadcast message.
Resolution
Load the appropriate Agent. Use CASTOFF ALL to block broadcast
messages to the workstation. Or, at the server console, in
ARCserve's Configuration screen, turn on the Turn off all messages
to workstation option to prevent ARCserve from sending any
broadcast messages.
E5002 - Failed to start database session, [error code]
E5003 - Failed to add record to ARCserve database,[error code]
E5004 - Failed to end database session, [error code]
Problem
There is no available disk space on the ARCserve volume.
Resolution
Use CHKVOL or VOLINFO to see if the ARCserve volume has run out of
disk space.
See also TECHNOTE: ARCserve and File Server Disk Space Problems.
Problem
The database may be corrupt or in an inconsistent state.
Resolution
Look in the ARCserve Activity Log for a Btrieve error.
See also Btrieve Status Codes and Messages
E5005 - Failed to locate directory [directory name] on workstation
Problem
A source directory of the workstation backup job no longer exists
on that workstation. The directory may have been deleted by a user
since the job was created, or it may have been a temporary
directory that was deleted by a normal workstation process.
Resolution
Verify that the directory no longer exists on the target drive. If
this is a repeating job, modify it and deselect the source
directory that no longer exists.
E5006 - Failed to allocate filter buffer [number] bytes
E5007 - Failed to allocate memory (number Bytes) for WS Backup
Problem
The host server does not have enough memory to process the job.
Resolution
See Checking File Server Memory Status.
E5008 - Failed to create file [file name] - [error message]
Problem
The Workstation Restore process fails to create the file on the
workstation due to one of the following causes:
1. There is already a file in the target directory with the same
file name.
2. The workstation disk may be full.
3. The file is opened by another application in a locked or
exclusive mode.
Resolution
For each of the causes check the following:
1. If the file or directory exists but cannot be overwritten, you
can restore the file with the Rename if
Exists option, thus restoring the file with a different extension.
2. Use CHKDSK to see if the workstation's disk is full.
3. Close the other application to release the file.
E5011 - Failed to get host server information, [NetWare error code]
Problem
The ARCserve-created user CHEY_ARCHSVR has been deleted, altered,
corrupted or has had its password changed.
Resolution
See Recreating the ARCserve Job Queue
E5012 - Failed to get workstation's drive list
E5013 - Failed to initiate SPX send to workstation 9cmd=[code number], #
of bytes)
Problem
The error occurs when trying to view a workstation's hard drive(s)
thorough the browser in the ARCserve Manager Backup or Restore
screens. It indicates that the SPX communication between the
server and the workstation is not proceeding properly.
Resolution
First, make sure that an agent is properly loaded on the
workstation to be viewed and that access to the workstation is not
blocked by a network broadcast message. If the agent is already
loaded, load the SPXCONFG.NLM module at the file server console and
increase the following parameters to their maximum values:
A. SPX Watchdog Abort Timeout
B. SPX Watchdog Verify Timeout
C. SPX Ack Wait Timeout
D. SPX Default Retry Count
E. Maximum Concurrent SPX Sessions
Note: C and D are the most important parameters that need to be
changed.
E5018 - Failed to allocate [number] bytes) for WS Backup
Problem
The host server does not have sufficient memory to spawn the NLMs
needed to perform the workstation backup.
Resolution
Increase the amount of File Cache Buffers available on the server.
See Checking File Server Memory Status.
E5019 - Failed to open file [file name] -[error message][error code]
Problem
ARCserve was unable to back up the specified file for any of the
following reasons:
1. The file no longer exists.
2. The file is in use by another application which has it open in
exclusive mode, and the file has not been flagged as shareable.
3. The account being used by ARCserve to access this file does not
have the proper rights to the volume, directory or file.
4. The path to the file is incorrect.
5. The connection with the remote server was broken.
Resolution
1. Make sure the file exists.
2. Check to see that the file isn't open and locked by someone
else. This can be done using the MONITOR utility at the file
server console.
3. Flag the file shareable, using the following syntax: FLAG
[filename] S.
4. In the Backup Options screen of the ARCserve Manager, set the
Open File Method to Deny None if Deny Write Fails and rerun the
job.
5. Use FILER to check the effective rights to the specified
directory or file and change them if necessary.
6. Make sure the path to the specified file has been entered
correctly.
7. Check that the specified server exists on the network.
Check the communications path to the server, such as routers,
bridges, cabling, etc.
Make sure that the latest versions of the LAN drivers are
being used on both servers.
Make sure that the LAN cards are functioning properly. Try
replacing the LAN cards and drivers with those from a different
vendor on both servers.
Note: If this sort of problem occurs frequently, it may be
advisable to run the backup job at a time when there is a lesser
chance of users accessing files or to activate the Clear User
Connections Before Job option in the Backup Options screen of the
ARCserve Manager.
E5023 - Failed to receive packet from WS, [address] Expecting
seq.#[number]
Problem
This message occurs due to one of the following:
1. ARCserve has waited for a long time and is unable to receive the
packet from the workstation.
2. The network connection may be broken.
3. The workstation may have been turned off during the backup or
the agent may have been unloaded from memory.
Resolution
For each of the causes, check the following:
1. Make sure that the workstation is switched on and that an Agent
is loaded.
2. Try running the agent using a 512 byte packet size in one of the
following ways:
- From the ARCserve Scheduler configuration screen (at the file
server console), select Yes for Use 512 byte packet to communicate
with workstation.
- Load the agent with an appropriate parameter that will force a
512 byte packet to be used, such as: DOSAGENT !
See also Agent Command Line Arguments
3. Verify the server and the workstation have the same Packet Size
Limits set. For example, if the maximum packet size is set to 4k
on the server and 1k on the workstation then the E5023 error will
occur.
Server Parameter: (must be set in STARTUP.NCF, may be viewed from
the server console by using the SET command and selecting
Communications)
SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE=4202
Default Packet Sizes
NetWare 3.11=1130
NetWare 3.12=
NetWare 4.x=4202
Workstation parameters:
In the workstation's NET.CFG file, use the following parameter:
Link Driver drivername
MAX FRAME SIZE 4202 (for 3.1x servers)
or
MAX FRAME SIZE 4216 (for 4.x servers)
If the workstation is still using the SHELL.CFG file, use the IPX
PACKET SIZE LIMIT parameter.
Note: If one of these parameters is not explicitly set, then a 4k
default value is used.
4. Check for a workstation memory conflict involving network
communications:
- Using the DOS EMM386.EXE memory manager without specifying the
UMB parameter in the DOS=HIGH command or can produce this error.
- Loading memory resident programs into upper memory without
excluding a memory address range required for a particular network
interface card may also cause this problem.
E5027 - Failed to send command [code number] to workstation (# of bytes)
- [NetWare error code]
Problem
The error occurs while trying to back up a workstation.
Resolution
Try configuring the agent to use a 512 byte packet size. Verify
that any NetWare broadcast messages have been cleared from the
workstation.
See also Agent Command Line Arguments
E5029 - Failed to set [file name]'s information, [error code]
Problem
1. The user does not have appropriate rights to perform this
function.
2. The file has been deleted.
Resolution
1. Use SYSCON to make sure that the correct rights have been
assigned to the file.
2. Check to see if the file has been deleted.
E5031 - Failed to terminate SPX connection
Problem
This problem is due to a patch file called SPXDDFIX.NLM having been
loaded in order to run older versions of McAfee's Netshield
anti-virus product. If this patch is not loaded, the server will
abend with Netshield and ARCserve loaded at the same time.
Resolution
To run properly with ARCserve, Netshield users should upgrade to
version 1.60 or greater. This version will not require the use of
the SPXDDFIX.NLM patch.
E5035 - Failed to end tape session, [NetWare error code]
Problem
The connection has been broken between the Tape Server and the
workstation.
Resolution
Check the following:
1. Make sure that no one has reset the tape drive.
2. Check the physical connections between workstation and file
server, and file server and tape drive(s).
E5039 - Failed to get free buffer's
Problem
The host servers does not have enough memory.
Resolution
See Checking File Server Memory Status.
E5040 - Error reading [file name] - [error code] [error message]
Problem
This error message can have several causes:
- Someone has deleted or changed the file size since the job
started.
- The connection with remote server was broken.
- An application may have part of the file locked (such as a
database application).
Resolution
For each of these possible causes, try the following:
- Check for the existence of the file, and if the file has been
changed.
- Check the existence of the remote server.
- Check the physical communications path to the server, such as
routers, bridges, cabling, etc.
- Make sure you are using the latest versions of workstation LAN
drivers.
- Check your LAN cards. You might try replacing the LAN cards and
drivers with those from a different vendor on both servers.
- Check to see if an application is active and locking part of the
file.
E5041 - File [file name] differs from its image on tape
Problem
During the Compare Disk to Tape portion of the backup job, the file
cited has been detected as having changed. This can happen for
several reasons:
1. The file has been modified between the time it was backed up
and the time that the compare operation ran.
2. The file's attributes may have been changed between the time
the file was backed up and the time the compare operation ran.
3. The file's Last Access Date may have been changed between the
time the file was backed up and the time the compare operation ran.
4. The file may not have been backed up correctly due either to a
bad source drive or bad media.
Resolution
If it is conceivable that the file may have been altered by a
normal process (eg: if a user may have modified the file while the
backup job was running) then no action is necessary, except perhaps
to perform another backup in order to save the most recent version
of the file. If this is not the case, then perform the following
steps:
1. Try backing up the file again with the compare option.
2. See the Tape Drive Troubleshooting Checklist and check for
media or hardware problems.
3. Try running the job again using a different tape (a tape
recommended by the tape drive's manufacturer should be used).
4. Restore the file in question from the tape to a temporary
directory. Then, compare the restored copy of the file to the
original using the DOS COMP command (for DOS v5 and below) or the
FC command (DOS v5 and above). If the files are identical, then
the backups are being performed properly, but there may be a
problem with the way in which ARCserve is reporting errors.
E5042 - Receive time out (Sequence = sequence #)
Problem 1
This error occurs due to one of the following causes:
1. The workstation has been turned off.
2. The connection is broken.
3. A network broadcast message is blocking access to the
workstation.
4. Some routing problem.
Resolution
For each of the causes, check the following:
1. Has the workstation been shut off?
2. From the server console screen configuration form, select Yes
for Use 512 kbyte packet to communicate with WS Agent. This will
force ARCserve to use a smaller packet size.
See also Agent Command Line Arguments
3. Press CTRL-ENTER or click OK at the workstation to clear any
network broadcast messages.
4. Check routers or other hardware problems.
Problem 2
The error message is generated in the ARCserve activity log when
attempting to backup a Windows NT Workstation with the NTagent.
The backup never completes.
Resolution
This problem may possibly be caused by a fragmentation problem in
NWCS (NetWare Workstation Compatible Service, installed on the NT
machine). To work around this problem, use the NT registry editor
to change the NWLNKIPX parameters, as follows:
1. From a Command Prompt under WindowsNT, type REGEDT32 then press
the ENTER key. This will bring up the Registry editor.
2. Focus on the HKEY_LOCAL_MACHINE window inside the editor. You
should see several subkeys, including HARDWARE, SAM, etc., under
HKEY_LOCAL_MACHINE.
3. Double click on the SYSTEM subkey under HKEY_LOCAL_MACHINE key.
4. Double click on the CurrentControlSet subkey under SYSTEM.
5. Double click on the SERVICES subkey under CurrentControlSet.
6. Double click on the NWLINKIPX subkey under SERVICES.
7. Double click on the PARAMETERS subkey under NWLINKIPX.
8. With the PARAMETERS key highlighted, select Add Value under the
Edit pull down menu. Type in RouterMtu in the Value Name field.
Select REG_DWORD in the Data Type selection. Click on OK.
9. A DWORD Editor should pop-up. From the RADIX group, select the
decimal button. Then type 2000 in the Data Entry field. Click OK.
10. You can verify these values on the right-hand side of the
window. Select Close under the Registry pull down menu to close
the editor.
11. These updates will take effect after a REBOOT.
E5043 - Unknown command [command number] received from workstation
Problem
Command number is incorrect.
Resolution
Check to confirm that the version of the Agent that is currently
running is the correct one for that version of ARCserve.
E5044 - Job is canceled by WS, - Check workstation disk space
Problem
1. The Agent cancelled this job.
2. This error will occur if the user attempts to restore data that
was originally backed up using the NTagent with the DOS, WIN or
OS/2 agents. The problem exists because the ARCserve WSTAPE module
does not have the ability to translate the data format that the
NTagent uses into the format that the other agents currently use.
Resolution
1. Have user update to ARCserve 5.01e.
2. The job may have been canceled because the destination drive is
full.
3. All data backed up with the NTagent should be restored with the
NTagent. The ability to translate these data formats will be added
to a later revision of WSTAPE.
E5048 - Failed to open file [file name] for comparison
Problem
The file may be locked or may have been deleted since the backup
was done.
Resolution
If the file is locked by another application, close that
application and submit another compare job.
E5049 - Access rejected by workstation - Invalid password
Problem
Error occurs when trying to backup a workstation that has the
agent's password protection feature enabled.
Resolution
The wrong password was entered when submitting a workstation backup
job. This is the password specified when loading DOSagent or
WINagent. Resubmit the job using the correct password.
E5050 - Invalid file header, signature:[signature]
Problem
Tape is not of compatible format.
Resolution
Try running an attended job instead of an unattended one. If the
problem persists, see Tape Drive Troubleshooting Checklist.
E5051 - Workstation has too many levels
Problem
1. There are more nested directory levels on a workstation drive
than ARCserve can process.
2. The DOS File Allocation Table may be corrupt.
Resolution
1. Try to use the Attended Backup mode by submitting the job to the
Local Machine, rather than the ARCserve server.
2. Verify and repair the DOS FAT table error by using the DOS
CHKDSK /F command or a third party disk maintenance utility.
E5052 - Failed to resume job, [error desc]
Problem
Refer to the error description for more information about the exact
error that occurred.
Resolution
This is usually due to some media or hardware error.
See Tape Drive Troubleshooting Checklist.
E5053 - Failed to write session header to tape
Problem
This error message is usually due to a media or hardware error
Resolution
See Tape Drive Troubleshooting Checklist.
E5055 - Source directory [directory name] does not have ':' or '/'
Problem
The job may have been corrupted.
Resolution
Try resubmitting the job. If the problem persists, see Recreating
the ARCserve Job Queue.
E5058 - Failed to rename file [file name]
Problem
ARCserve could not write the file being restored to the workstation
drive, because it could not rename the file it was replacing.
Resolution
1. Move, rename or delete the file to be replaced on the
destination drive and resubmit the job.
or
2. Instead of using the Rename File option, in the Conflict
Resolution configuration area of the ARCserve Manager Restore
window, choose to restore the file to another directory, and
resubmit the job.
This applies to:
|
