LabSSH Error Codes

LabSSH uses the following error codes:

CodeDescription
402420Socket error
402421Internal memory allocation call failed
402422Licensing error
402423LabSSH uninitialized. Please call "Init.vi" prior to using LabSSH
402424invalid option or parameter was passed into API call
402425Timeout occurred while waiting for response from server
402426Authentication method not supported
402427File or disk error
402428Environment error
402429Bad internal library usage
402430Invalid internal parameter, or internal exception occurred
402431System call failed
402450Error receiving banner from remote host
402451Unable to send banner to remote host
402452Invalid MAC received
402453Encryption key exchange with remote host failed
402454Unable to send data on socket
402455Unrecoverable error exchanging keys
402456Unable to initialize hostkey importer
402457Unable to verify hostkey signature
402458Decryption error
402459Socket disconnected
402460Invalid SSH protocol response received
402461User password expired
402462Authentication failed (bad username/password/publickey combination)
402463Username/publickey combination invalid
402464Unable to startup channel
402465Unable to complete request on channel
402466Packet received for unknown channel
402467Receive window full, data dropped
402468Received packet that was too large
402469Channel disconnected
402470Channel requested to be closed
402471Invalid SCP protocol response received
402472Compression error
402473Remote host refused request
402474Invalid publickey subsystem response
402475Buffer too small
402476Unhandled compression error
402477Packet exceeded maximum size
402478Unable to receive on socket
402479Transport encryption error
402500End of file received
402501No such file exists on remote filesystem
402502User does not have sufficient permissions to perform the operation
402503Error occurred, but no specific error code exists to describe the failure
402504Badly formatted packet or other SFTP protocol incompatibility was detected
402505Attempted operation could not be completed by the remote server because it does not support the operation
402506Invalid SFTP handle encountered
402507File path does not exist or is invalid
402508File already exists
402509File is on read-only media, or the media is write-protected
402510Requested operation could not be completed because there is no media available in the drive
402511Requested operation could not be completed because there is insufficient free space on remote filesystem
402512Requested operation could not be completed because it would exceed the user's storage quota
402513A principal referenced by the request (either the 'owner', 'group', or 'who' field) was unknown
402514File could not be opened because it is locked by another process
402515Directory is not empty
402516File is not a directory
402517Filename is not valid
402518Too many symbolic links encountered or, an SSH_FX_NOFOLLOW open encountered a symbolic link and open specified NOFOLLOW
402519The file cannot be deleted
402520One of the parameters was out of range, or the parameters specified cannot be used together
402521File was a directory in a context where a directory cannot be used
402522Read or write operation failed because another process's mandatory byte-range lock overlaps with the request
402523Request for byte range lock was refused
402524Operation was attempted on a file for which a delete operation is pending
402525File is corrupt; a file system integrity check should be run
402526Principal specified cannot be assigned as an owner of a file
402527Principal specified cannot be assigned as the primary group of a file