Backup3G/EWC/Error Listing EWC
From Documentation
←Older revision | Newer revision→
Contents |
FSntcpio
Error FSbusplit: Couldn't change to directory <directory> Reason FSbusplit was unable to change to <directory>. Solution Check that the directory exists and is accessible.
Error FSbusplit: Couldn't read file <file> Reason FSbusplit was unable to access the specified file. Solution Check that the file exists and is accessible.
Error Partition size not specified. Aborting. Reason FSbusplit requires specifying a partition size. Solution Check that the partition size is specified with the -P flag.
Error WARNING: -s or -S flags only allowed in selected file backup
WARNING: Flags ignoredReason File selection flags -s or -S can only be specified when performing a selected file backup. Solution Only specify these flags if you are performing a selected backup.
Error WARNING: Couldn't access <directory>/.FSbackup
WARNING: Defaulting to FULL backupReason Performing an incremental backup relies on having access to a file called .FSbackup in the root of the directory to be backed up. You will get this message if this file does not exist or is not readable. Solution Check that the file exists and is readable.
Error WARNING: Couldn't write to directory <directory>
WARNING: Defaulting to FULL backupReason Performing an incremental backup relies on having write access to the directory being backed up. You will get this message if the SYSTEM account cannot write to the specified directory. Solution Allow the SYSTEM account to have write access to the specified directory.
^ |
FSregback
Error Couldn't find ebc.dat Reason Sregback uses ntcpio to recover the ebc.dat file. This file contains details of the registry keys backed up. This error will occur if ntcpio reports that it was successful, but the ebc.dat file was not recovered. Solution Check that the tape contains a valid registry backup and is not corrupt.
Error Error: <directory> directory already exists Reason In order to perform a registry backup or restore a temporary directory must be created. FSregback will fail if this directory already exists. Solution It is likely that the directory is left over from a previous registry backup or recovery. If this is the case, remove the directory.
Error Failed to backup profiles Reason Once the profile list has been determined, FSregback attempts to backup the profile directories using ntcpio. This error occurs if ntcpio fails to backup these directories. Solution Check for other error messages from the ntcpio command.
Error Failed to backup registry Reason Once the registry has been dumped to file, FSregback attempts to back these files up using ntcpio. This error occurs if ntcpio fails to backup these files. Solution Check for other error messages from the ntcpio command.
Error Failed to output profiles Reason FSregback calls regback to output the list of profiles to be backed up. This error occurs if regback returns a non zero exit status. Solution Check for other error messages from the regback command.
Error Failed to output registry Reason FSregback calls regback to output the registry. This error occurs if regback returns a non zero exit status. Solution Check for other error messages from the regback command.
Error Failed to recover profile(s) Reason For a profile recovery, the data is recovered using ntcpio. If ntcpio fails for any reason, this error will occur. Solution It is possible that the data is corrupt. Check for ntcpio error messages.
Error Failed to recover registry Reason For a registry restore, the data must first be extracted from tape and saved to file. This is done by the ntcpio command. Also regback is used to restore the keys from file. If ntcpio or regback fail for any reason, this error will occur. Solution It is possible that the data is corrupt. Check for ntcpio and regback error messages.
Error Failed to recover registry header Reason For an index to be generated, FSregback uses ntcpio to recover the ebc.dat file. This file contains details of the registry keys backed up. This error will occur if ntcpio failed to recover this file. Solution It is possible that the data is corrupt. Check for ntcpio and regback error messages.
Error Unable to change to <directory> Reason To perform a registry backup or restore FSregback must change to <directory>. Failure to change to this directory will result in this error. Solution Check that the directory exists and is accessible
^ |
FSremote
Error FSbusplit: Couldn't change to directory <directory> Reason FSbusplit was unable to change to <directory>. Solution Check that the directory exists and is accessible.
Error
^ |
busplit
Error FSbusplit: Couldn't change to directory <directory> Reason FSbusplit was unable to change to <directory>. Solution Check that the directory exists and is accessible.
Error
^ |
cos
Error FSbusplit: Couldn't change to directory <directory> Reason FSbusplit was unable to change to <directory>. Solution Check that the directory exists and is accessible.
Error
^ |
devio
Error FSbusplit: Couldn't change to directory <directory> Reason FSbusplit was unable to change to <directory>. Solution Check that the directory exists and is accessible.
Error
^ |
devscan
Error FSbusplit: Couldn't change to directory <directory> Reason FSbusplit was unable to change to <directory>. Solution Check that the directory exists and is accessible.
Error Error: Couldn't access drive <drive>: <error number> Reason: The drive specified could not be accessed. Either the drive name is invalid or there is a problem with the tape drive. The exact error can be determined by running: net helpmsg <error number> Solution: Check that the tape name is correct and that the tape drive is working.
Error: Couldn't allocate memory for I/O buffer Reason: Devscan was unable to allocate enough memory for the buffer. The system is short on memory. Solution: Free up some memory by shutting down other applications.
Error: Error <number>: Failed to initialise tape Reason: A general error has occurred whilst trying to initialise the tape. The exact error can be determined by running: net helpmsg <error number> Solution: Will depend on the error that has occurred. It is possible that the tape or tape device is faulty.
Error: I/O error: file <file>, block <block> Reason: Devscan encountered an error reading at file <file> and block <block>. Solution: Try reading the tape again. If the problem persists it is likely that the data or tape is corrupt.
Error: Illegal blocksize (-b) Reason: The value supplied for the blocksize is invalid. Blocksize must be an integer value. Solution: Use integer value as argument for blocksize. e.g. devscan -b 32
Error: Illegal datasize (-d) Reason: The value supplied for the datasize is invalid. Datasize must be an integer value. Solution: Use integer value as argument for datasize. e.g. devscan -d 1048576
Error: Illegal number of files (-f) Reason: The value supplied for the number of files is invalid. The number of files must be an integer value. Solution: Use integer value as argument for number of files. e.g. devscan -f 4
Error: Tape is not partitioned Reason: The tape in the drive is not formatted correctly with valid tape partitions. Solution: Partition the tape correctly.
Error: There is no tape loaded Reason: There is no tape in the specified drive. Solution: Load a tape in the specified drive.
^ |
end_label
Error end_label: Illegal or missing media capacity Reason In order to have an end_label, the media capacity must be supplied as an argument to end_label. Either the value was not supplied or the value supplied is invalid. Solution Supply a valid media capacity value.
^ |
ewc.exe
Error FSbusplit: Couldn't change to directory <directory> Reason FSbusplit was unable to change to <directory>. Solution Check that the directory exists and is accessible.
Error Error: Couldn't find Home Directory Reason: The variable EWC_HOME needs to be set for the Enterprise Windows Client to set various paths. Either the EWC_HOME variable is not set or the registry entry is invalid. Solution: Set the EWC_HOME variable to point to the location of the Enterprise Windows Client home directory. Check the registry entry for the Enterprise Windows Client HomeDir value.
Error: Couldn't find server directory Reason: This error results from a failed attempt by ewc.exe to change to the server directory. Solution: Ensure that the Enterprise Windows Client is installed correctly. Also check that the server directory exists and is accessible.
Error: Failed to read file: <file> Reason: The specified file could not be found or opened. Solution: Check that the file exists and is accessible. The file should be located in the server directory.
Error: Failed to write to file: <file> Reason: The specified file could not be written to. Solution: Check that appropriate permissions exist for the file to be opened or created.
Error: Fatal Error Reason: The Enterprise Windows Client has encountered a fatal error. Solution: It is likely that this fault was caused by a system error. Restart the Enterprise Windows Client.
Error: Incr Tcl Initialisation Error Reason: The Enterprise Windows Client failed to initialize incr tcl. Solution: Fatal error, the software has been corrupted. Re-install the Enterprise Windows Client.
Error: Internal Error Reason: The Enterprise Windows Client failed to access a critical file. The startup.tcl file in the lib directory. Solution: Fatal error, the software has been corrupted. Re-install the Enterprise Windows Client.
Error: Library Initialisation Error Reason: The Enterprise Windows Client failed to initialize an internal library. Solution: Fatal error, the software has been corrupted. Re-install the Enterprise Windows Client.
Error: Tcl Initialisation Error Reason: The Enterprise Windows Client failed to initialize tcl. Solution: Check that the tcl76.dll exists and is accessible in the Enterprise Windows Client bin directory.
Error: Tk Initialisation Error Reason: The Enterprise Windows Client failed to initialize tk. Solution: Check that the tk42.dll exists and is accessible in the Enterprise Windows Client bin directory.
^ |
file_excl.exe
Error Couldn't open <file> Reason file_excl was unable to open the specified file. Solution Check that the file exists and is accessible.
Error Bad file pattern: <pattern> Reason The file pattern is NULL or the syntax is invalid. Solution Supply a valid file pattern.
^ |
file_list.exe
Error Couldn't open <file> Reason file_list was unable to open the specified file. Solution Check that the file exists and is accessible.
Error Couldn't access <file> Reason Unable to determine the files attributes. Solution Check that the file exists and is accessible.
Error Can not read directory <directory> Reason Unable to read entries from the specified directory. Solution Check that the directory exists and is accessible.
^ |
mt.exe
Error FSbusplit: Couldn't change to directory <directory> Reason FSbusplit was unable to change to <directory>. Solution Check that the directory exists and is accessible.
Error Error: <device>: compression not supported Reason: The device does not support hardware compression. Solution: No solution.
Error: <device>: device busy Reason: The device is currently being controlled by another process. Solution: Wait for the command to finish.
Error: <device>: no such device or address Reason: The device name supplied is not a valid tape device. Solution: Specify a valid device name. e.g. mt -f tape0
Error: <device>: there is no media in the drive Reason: In order to perform magnetic tape operations, a tape must be loaded in the specified drive. Solution: Load a tape in the specified drive.
Error: mt: error accessing device: <error number> Reason: mt was unable to access the tape device. The exact error can be determined by running: net helpmsg <error number> Solution: Will depend on the error that has occurred.
Error: mt: error accessing tape: <error number> Reason: mt was unable to access the tape. The exact error can be determined by running: net helpmsg <error number> Solution: Will depend on the error that has occurred.
Error: mt: error setting compression: <error number> Reason: mt was unable to set the compression either on or off. The exact error can be determined by running: net helpmsg <error number> Solution: Will depend on the error that has occurred.
^ |
ntcpio.exe
Error FSbusplit: Couldn't change to directory <directory> Reason FSbusplit was unable to change to <directory>. Solution Check that the directory exists and is accessible.
Error Error: Couldn't change to <directory> Reason: regback was unable to change to the directory specified with the -d option. Solution: Check that the directory exists and is accessible.
Error: Error accessing profile <user sid>: <error number> Reason: An error was encountered whilst trying to access the specified user profile. Solution: Will depend on the error that has occurred.
Error: Error accessing registry Reason: regback was unable to access the registry. It is possible that the registry is corrupted or is temporarily inaccessible. Solution: Check that the registry has not been corrupted.
Error: Error Creating data file Reason: Details of which keys have been backup up are stored in a file called ebc.dat. This error occurs if this file was unable to be created. Solution: Check permissions on the directory where the file is created. Unless otherwise specified this will be a directory in /tmp.
Error: Error getting process token Reason: Unable to to get the process token. System error. Solution: No solution.
Error: Error opening <key>: <error number> Reason: An error was encountered whilst trying to access the specified registry key. Solution: Will depend on the error that has occurred.
Error: Error opening <key>: Access Denied Reason: You do not have permission to access the specified registry key. Solution: Only users with sufficient privileges can access the registry.
Error: Error saving <key>: <error number> Reason: The system call to write the specified key to file failed. Solution: Will depend on the error that has occurred. The problem is likely to be either in accessing the registry or writing the data to file.
Error: Error replacing <key>: Access Denied Reason: You do not have permission to restore the specified registry key. Solution: Only users with sufficient privileges can restore the registry.
Error: Error replacing <key>: <error number> Reason: The system call to restore the specified key from file failed. Solution: Will depend on the error that has occurred. The problem is likely to be either in accessing the registry or reading the data from file.
Error: Insufficient Privileges Reason: You do not have permissions to perform the requested action. Solution: This command can only be performed by users whose policy includes the backup right.
Error: Unable to get profile path for <user sid>: <error number> Reason: An error was encountered whilst trying to access the specified registry entry for the user profile. Solution: Will depend on the error that has occurred.
Error: Unknown Privilege <SE_BACKUP_NAME> Reason: The privilege <SE_BACKUP_NAME> does not exist on this host. Solution: The operating system configuration has been altered. This privilege should exist.
Error: Unknown Privilege <SE_RESTORE_NAME> Reason: The privilege <SE_RESTORE_NAME> does not exist on this host. Solution: The operating system configuration has been altered. This privilege should exist.
Error: Unknown Privilege <SE_SHUTDOWN_NAME> Reason: The privilege <SE_SHUTDOWN_NAME> does not exist on this host. Solution: The operating system configuration has been altered. This privilege should exist.
^ |
regback.exe
Error FSbusplit: Couldn't change to directory <directory> Reason FSbusplit was unable to change to <directory>. Solution Check that the directory exists and is accessible.
Error Error: Couldn't change to <directory> Reason: regback was unable to change to the directory specified with the -d option. Solution: Check that the directory exists and is accessible.
Error: Error accessing profile <user sid>: <error number> Reason: An error was encountered whilst trying to access the specified user profile. Solution: Will depend on the error that has occurred.
Error: Error accessing registry Reason: regback was unable to access the registry. It is possible that the registry is corrupted or is temporarily inaccessible. Solution: Check that the registry has not been corrupted.
Error: Error Creating data file Reason: Details of which keys have been backup up are stored in a file called ebc.dat. This error occurs if this file was unable to be created. Solution: Check permissions on the directory where the file is created. Unless otherwise specified this will be a directory in /tmp.
Error: Error getting process token Reason: Unable to to get the process token. System error. Solution: No solution.
Error: Error opening <key>: <error number> Reason: An error was encountered whilst trying to access the specified registry key. Solution: Will depend on the error that has occurred.
Error: Error opening <key>: Access Denied Reason: You do not have permission to access the specified registry key. Solution: Only users with sufficient privileges can access the registry.
Error: Error saving <key>: <error number> Reason: The system call to write the specified key to file failed. Solution: Will depend on the error that has occurred. The problem is likely to be either in accessing the registry or writing the data to file.
Error: Error replacing <key>: Access Denied Reason: You do not have permission to restore the specified registry key. Solution: Only users with sufficient privileges can restore the registry.
Error: Error replacing <key>: <error number> Reason: The system call to restore the specified key from file failed. Solution: Will depend on the error that has occurred. The problem is likely to be either in accessing the registry or reading the data from file.
Error: Insufficient Privileges Reason: You do not have permissions to perform the requested action. Solution: This command can only be performed by users whose policy includes the backup right.
Error: Unable to get profile path for <user sid>: <error number> Reason: An error was encountered whilst trying to access the specified registry entry for the user profile. Solution: Will depend on the error that has occurred.
Error: Unknown Privilege <SE_BACKUP_NAME> Reason: The privilege <SE_BACKUP_NAME> does not exist on this host. Solution: The operating system configuration has been altered. This privilege should exist.
Error: Unknown Privilege <SE_RESTORE_NAME> Reason: The privilege <SE_RESTORE_NAME> does not exist on this host. Solution: The operating system configuration has been altered. This privilege should exist.
Error: Unknown Privilege <SE_SHUTDOWN_NAME> Reason: The privilege <SE_SHUTDOWN_NAME> does not exist on this host. Solution: The operating system configuration has been altered. This privilege should exist.
^ |
service
Error Could not open <file> Reason The specified file could not be opened. The application home db directory is also checked for this file. Solution Check that the file exists and is accessible.
Error WINDIR variable not set Reason The service script relies on the variable WINDIR being set. It uses this variable to locate the Windows NT net command. i.e. $WINDIR/system32/net
Solution Check that the SYSTEM account has the WINDIR variable set correctly.
| ^ |
Copyright © 1990-2024 Functional Software. All rights reserved.