Exit Codes Used in Command Line for /dataexport
Last modified: October 18, 2023
If data export is run through the command-line interface, 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. |
2 | Ctrl-Break | Execution stopped because of a Ctrl-Break. |
3 | Failed. | |
10 | Command line usage error | The command line was used incorrectly. For example, an incorrect flag, or incorrect syntax may have been used. |
11 | Illegal argument duplication | Some arguments must not appear more than once. |
20 | Trial expired | The trial period has expired, or dbForge Studio for MySQL has not been activated. |
30 | Project file corrupted | Project file corrupted. |
40 | Server connection fail | Server connection failed. |
103 | Execution error | A script execution error occurred. |
105 | Resource is unavailable | A file is missing. |
107 | Failed to create report | The report has not been created. |
108 | No objects | There are no files for data export. |
Was this page helpful?
Want to find out more?
Overview
Take a quick tour to learn all about the key benefits delivered by dbForge Studio for MySQL.
All features
Get acquainted with the rich features and capabilities of the tool in less than 5 minutes.
Request a demo
If you consider employing this tool for your business, request a demo to see it in action.