If schema export is run through the command-line interface using the /schemaexport key, the following exit codes are returned depending on the execution result:
| Error Code | Description | Additional Information |
|---|---|---|
| 0 | Success | The operation has been completed without errors. |
| 1 | Unhandled exception. See the log for more detail. | An unexpected error occurred during execution. Review the log file for details about the exception. |
| 2 | Execution terminated with Ctrl+Break | The execution was stopped by Ctrl+Break. |
| 3 | Failed | The operation completed with errors. |
| 10 | Command line usage error | The command line was used incorrectly. For example, an incorrect flag or syntax has been used. |
| 11 | Illegal argument duplication | Some arguments shouldn’t appear more than once. |
| 12 | Unsatisfied dependency | There is an unsatisfied argument dependency or violated exclusion. |
| 20 | Trial expired | The trial period has expired or dbForge Studio hasn’t been activated. |
| 30 | Project file corrupted | The operation could not proceed because the project file was corrupted. |
| 40 | Server connection fail | Server connection failed. |
| 103 | Script executed with errors | A script execution error occurred. |
| 105 | Resource unavailable | A file is missing. |
| 108 | There are no objects to perform the specified operation | The operation could not be performed because no valid objects were found that match the specified criteria. |