If a task you are performing with the SQL Compare command line interface fails, and you do not see an error message explaining the reason for the failure, you may see one of the exit codes listed below:
Some arguments must not appear more than once in a command line.
There is an unsatisfied argument dependency or violated exclusion when the command line is run. For example:
The numeric value supplied for an argument is outside the range of valid values for that argument.
The value supplied for an argument is too large.
The value supplied for an argument is invalid.
Software license or trial period has expired.
SQL Compare encountered serious warnings that apply to the deployment.
If you're using SQL Compare, you can ignore these warnings by specifying /AbortOnWarnings:None
If you're using SQLCI, you can ignore these warnings by specifying /additionalCompareArgs=/AbortOnWarnings:None
For more information about /AbortOnWarnings, see Switches used in the command line.
SQL Compare encountered high level errors when parsing a scripts folder.
Use /IgnoreParserErrors to force SQL Compare to continue without exiting.
The Error Parsing Scripts dialog box in the SQL Compare user interface provides additional information to help you resolve script parser errors.
The databases being compared are identical or no objects have been included.
To suppress this error use /Include:Identical
The command line was used incorrectly. For example, an incorrect flag, or incorrect syntax may have been used.
Data required by SQL Compare is invalid or corrupt.
A resource or service required to run SQL Compare is unavailable.
See the log for more details.
The report was not created.
This is returned if SQL Compare attempts to write to a file that already exists, and the /force switch has not been set.
The action can't be completed because the user does not have the necessary permission.
This is returned when the /assertidentical switch is used and the source and target are not identical.
Execution failed because of an error.
Execution stopped because of a Ctrl-Break.
The command line arguments can't be executed. For example, you may have provided two mutually exclusive switches.
There is no acceptable license. If you have one, use /activateSerial:<SerialKey>. If you don't have a license, please contact email@example.com for a either a trial extension key or to purchase a license.
Activation was cancelled because the cancel button was pressed during the process.
An unhandled exception occurred. The exception message and stack trace will be included in the output.