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