|
Product: StorageExpress Backup Server
E2002, E2006, E2008, E2010, E2013, E2018, E2023, E2024, E2027, E2028, E2029, E2030, E2031, E2032, E2033, E2034, E2035, E2036, E2038, E2055, E2073, E2078, E2081, E2088, E2097, E2110, E2127, E2129, E2131, E2133, E2197, E2215, E2216, E2265, E2266, E2285, E2286, E2287, E2313, E2321,
E2002 - User [user name] Does Not Have Supervisory Rights on Server[server name]
Problem Certain ARCOPY operations require the user to have supervisor rights.
Resolution Assign supervisor rights to the user or modify the job to use an account with supervisor rights.
E2006 - Failed to Locate Directory [directory name] on Workstation
Problem Either the specified directory directory doesn't exist, or the path name is incorrect.
Resolution Verify that the correct directory name is specified in the job form and that the directory exists.
E2010 - Failed to Allocate Memory ([number] bytes)
Problem There is not enough server memory available.
Resolution See Checking the File Server's Memory Status.
E2013 - Failed to Issue InocuLAN Scan Request - [NetWare error code]
Problem The status of the InocuLAN interface is being shown as busy. ARCserve will wait five minutes for the InocuLAN scan to begin and then generate this error message.
Resolution Check the InocuLAN Activity Log and/or documentation for specific information on InocuLAN's operational status.
E2018 - Failed to Close [filename]'s Bindery -[NetWare error code]
Problem The user does not have appropriate rights for this function. The bindery cannot be closed, and therefore cannot be copied, unless the user is a Supervisor or equivalent.
Resolution Assign Supervisor rights to the user or modify the job to utilize a user name that has Supervisor rights.
E2023 - Failed to Establish Connection with WS @ [workstation address], [NetWare error code] - Agent Not Loaded
Problem ARCserve has failed to contact the workstation agent, most likely due to the agent's not having been loaded.
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.
E2024 - Failed to Copy [file name] - Requested:[file size] Actual: [how much was copied successfully], [NetWare error code]
Problem The amount of data copied successfully does not match that which was requested. This could be due to insufficient disk space on the target volume, directory or space restrictions on the account being used to access the target volume, or corruption in the source file.
Resolution 1. Make sure that the target volume has sufficient free disk space to hold the file(s) to be copied.
See also TECHNOTE: ARCserve and File Server Disk Space Problems.
2. Check for directory and user restrictions using the NetWare DSPACE utility.
3. Make sure that the source file has not become corrupted.
E2027 - Failed to Create File [file name] -[error description] E2028 - Failed to Write Report File (file name) E2029 - Failed to Create Work File [file name] to Store Migration Info, [error description] E2030 - Failed to Create MAC Directory [directory name] [MAC long name], [NetWare error code] E2031 - Failed to Create MAC File [file name] [long name] E2088 - Failed to Record File to be Deleted -[error description] E2129 - Error Writing [file name] - [error description] E2266 - Error Writing Retry Missed File Log [log name], [error description]
Problem A file could not be created on the target volume, either because there is insufficient disk space available, or because the account being used to access the target volume has insufficient rights.
Resolution 1. Check that there is sufficient disk space on the target volume for the file(s) to be copied.
2. Make sure that the account being used to create the job has sufficient rights to create files on the target volume, and that there are no space restrictions preventing the creation of the file(s).
See also TECHNOTE: ARCserve and File Server Disk Space Problems
Note: Use SYSCON to check assigned rights, use DSPACE to check user and directory restrictions.
E2027 Failed to create file <server>/<volume>\ARC$NEXT.NXT - Permission denied
Problem While copying files from a subdirectory on one volume to another, the above error is displayed. However, the files are copied successfully.
Resolution The file ARC$NEXT.NXT is a placeholder created on the root of the destination volume. If the user does not have sufficient rights at the root to create the file, then the error is reported. Provided that the user has appropriate rights to the destination directory, the files will be copied successfully and the E2027 error can be ignored.
E2027 Failed to create file [file name] - [error description].
Problem You don't have proper rights to create a file, or there is no disk space available.
Resolution Check your assigned rights. Check disk space.
E2032 - Failed to Begin FTS Session, [NetWare error code] E2033 - Failed to Begin FTS Job, [NetWare error code] E2034 - Failed to Add FTS Record, [NetWare error code] E2035 - Failed to End FTS Session, [NetWare error code] E2036 - Failed to End FTS Job, [NetWare 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
E2038 - [Directory name] Not Found - [error description] E2133 - File [file name] Not Found
Problem Either the specified directory or file doesn't exist, or the account being used to access it does not have sufficient rights to access it.
Resolution Make sure that the file/directory has not been renamed or deleted. Check to see that the user has appropriate rights to the file/directory.
E2055 Failed to Get <volumename> Volume Number -98
Problem User was getting E2055 during the copy job after the server was downed and brought back up.
Resolution All volumes were not mounted on both the host and remote server.
E2071 Failed to Create Directory [directory name] - [error description].
Problem There can be several reasons for this error to occur: There is no available disk space. User does not have proper rights to create the directory. Maximum number of directory levels has been reached?
Resolution For each of the reasons, check the following: Check disk space on the server. Use DSPACE to check for any user and directory restrictions. Use SYSCON to make sure the user has rights to create directories. Check to see if the maximum number of directory levels has been reached.
E2073 - Failed to Open File[file name]-[error description] E2078 - Failed to Open MAC File [file name][MAC long name]
Problem Either the file has been incorrectly specified when creating the job, or it has already been opened in exclusive mode by another application or the account being used to access the file doesn't have the appropriate rights to open it.
Resolution Check to see that the filename exists in the specified directory. Use the NetWare MONITOR utility to determine if another user has the file open. Check to see that user account has the rights necessary to open the file.
E2081 - Failed to receive job from scheduler. Queue [queue name], ret=[ NetWare error code]
Problem There is a problem retrieving a job from the ARCserve Job Queue.
Resolution Put the original job on hold and resubmit the same job again. If the same error is generated, it will be necessary to recreate the ARCserve Job Queue.
See Recreating the ARCserve Job Queue.
E2097 Failed to scan [filename]'s trustees.
Resolution Bindery may be corrupted. Try repairing bindery using BINDFIX utility.
E2110 - Failed to Delete [file name] - [error description]
Problem The account attempting to perform the operation does not have sufficient rights to delete the specified file.
Resolution Alter the rights of the account attempting to perform the function or use another account with appropriate rights.
E2127 - Error Reading [file name] - [error description]
Problem There is either some corruption in the specified file or the connection or the connection to its source has been broken.
Resolution Make sure file's source directory is accessible to the network and make sure that the file has not been corrupted and is readable.
E2131 - Failed to Open File [file name], Execute Only
Problem ARCserve cannot open this file because it has been flagged as an EXECUTE ONLY file.
Resolution Remove the "X" attribute using the NetWare FLAG utility.
E2197 - "Service Connection with File Server [server name] is Broken!"
Problem This message appears after other error messages because the connection to the specified server has been broken.
Resolution 1. Check that the specified server exists on the network.
2. Check the physical communications path to the server, such as routers, bridges, cabling, etc.
3. Make sure that the latest versions of the LAN drivers are being used on both servers.
4. 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.
Also, see E0168 for connection troubleshooting.
E2215 - Failed to Complete InocuLAN Scan on [directory name] - [NetWare error code]
Problem InocuLAN has reported an error in its attempt to perform a virus scan on the specified directory. This could be either be attributable to an InocuLAN problem or the account being used to access the directory does not have the appropriate rights to it.
Resolution Make sure that the user has the appropriate rights to the specified directory. See the InocuLAN Activity Log and/or documentation for specific information on the status of the InocuLAN scan.
E2216 - Wait for InocuLAN Result - Time Out
Problem The InocuLAN virus scan took too long, and the directory will be skipped.
Resolution ARCserve waits for twenty minutes for InocuLAN to finish its scan. See the InocuLAN Activity Logs and/or documentation for specific information on the status of the InocuLAN scan.
E2265 Error Reading Retry Missed Files Log [log name], [error description].
Problem There is some corruption with the file or the connection has been broken.
Resolution: Use DOS to verify that there isn't a problem with the file. Check to see if the connection is gone.
E2285 - Failed to Recreate Queue [queue name] E2286 - Failed to Recreate User [user name] E2287 - Client [client name] does not have bindery access.
Problem The account being used to perform this function does not have supervisory rights. The user must be a supervisor equivalent to perform disk mirroring when the destination is the ARCserve host server.
Resolution Assign supervisory rights to the user account or log in as Supervisor when creating a job of this type.
E2313 - Failed to Lock File [file name], [error description]
Problem ARCserve cannot lock the specified file because it is in use.
Resolution 1. Use the NetWare MONITOR utility to determine which user or process has the specified file open.
2. When creating the job using the ARCserve Manager, do not select Use Lock Mode if Deny Write Fails from the Open File Method dialog in the Backup Options screen if there is a good chance the files will be in use. Instead, choose Deny None if Deny Write Fails. This will allow a user to view a file while it is being backed up.
This applies to:
|