The table provides a list of exit codes returned by the /document command.
| Error Code | Status | Description |
|---|---|---|
| 0 | Success | Indicates that the operation has been completed without errors. |
| 2 | Execution terminated with Ctrl+Break | Indicates that the execution has been stopped with Ctrl+Break. |
| 10 | Command line usage error | Indicates that the syntax doesn’t match the expected command format. |
| 11 | Illegal argument duplication | Indicates that the same command-line argument was specified more than once. |
| 12 | Unsatisfied dependency | Indicates that a required argument is missing or mutually exclusive arguments were used together. |
| 15 | The value supplied for an argument is invalid | Indicates that an argument was provided with a value that doesn’t meet the expected format, range, or type. |
| 20 | Trial expired | Indicates that the trial period has expired, or the product has not been activated. |
| 30 | Project file corrupted | Indicates that the project file can’t be read or contains invalid data. |
| 40 | Server connection fail | Indicates that dbForge Studio could not connect to the specified server. |
| 105 | Resource unavailable | Indicates that a required file is missing. |
| 108 | There are no objects to perform the specified operation | Indicates that the operation could not be performed because no applicable objects were found. |
For more information about the /document command, see Automate generation of database documentation from the command line.