The object represents the available error codes. noError (1): the operation completed successfully, serverNotResponding (2): server providing the copying is not responding fileNotFound (3): the required source file is not found accessViolationDst (4): Destination file cannot be written or created due to access violation, e.g. authentication failure, destination file is RO or in-use invalidSrcFile (5): invalid Source file CRC, signature or header invalidRollbackSrc (6): invalid source for configuration rollback operation connectionFail (8): the copy file session can't start due to failure of TCP/IP or SSH connection lackOfSpace (9): the copy destination doesn't have enough space for the file lackOfInternalResources (10): the device doesn't have enough internal resources (e.g. free RAM) to carry out the copy operation endedTimeout (11): operation timeout occurred accessViolationSrc (14): Source file cannot be read due to access violation, e.g. authentication failure, source file is RO or in use transferToStandbyFailed (15): Transfer of the copied file from Active card to Standby card failed. otherError (255) The (7) and (8) errors can occur during configuration rollback processing. Agent reports the (7) error when it tries to perform configuration rollback (e.g. due to failure of a new configuration activation), but it can't find valid rollback configuration. Agent reports the (8) error if it can't save running configuration when it activates a new configuration set. As a result the next time configuration rollback will fail.