If a task you are performing with the SQL Data Compare command line interface fails, and you do not see an error message explaining the reason for the failure, then inspecting its exit code may show one of those listed below:

0 - Success

1 - General error code

3 - Illegal argument duplication

Some arguments cannot be used more than once in a command line.

8 - Unsatisfied argument dependency

There is an unsatisfied argument dependency or violated exclusion when the command line is run. For example:

• /arg2 depends on /arg1 but you have specified /arg2 without specifying /arg1
• /arg2 cannot be used with /arg1 but you have used both

32 - Value out of range

The numeric value supplied for an argument is outside the range of valid values for that argument.

33 - Value overflow

The value supplied for an argument is too large.

34 - Invalid value

The value supplied for an argument is invalid.

35 - Invalid license

Software license or trial period has expired.

62 - High level parser error

SQL Data Compare encountered high level errors when parsing a scripts folder.

Use /ignoreParserErrors to force SQL Data Compare to continue without exiting.

63 - Databases identical

The databases being compared are identical or no objects have been included.

64 - Command line usage error

The command line was used incorrectly. For example, an incorrect flag, or incorrect syntax may have been used.

65 - Data error

Data required by SQL Data Compare is invalid or corrupt.

This often indicates that a constraint violation occurred while running the deployment script. Check your schema to ensure that when you are migrating data you do not violate any constraints in the schema. You should either modify the data you are migrating, or change the SQL Data Compare command line options to resolve the problem.

69 - Resource unavailable

A resource or service required to run SQL Data Compare is unavailable.

70 - an unhandled exception occurred

See the log for more details.

73 - Failed to create report

The report was not created.

74 - I/O error

For example, this is returned if SQL Data Compare attempts to write to a file that already exists, and the /force switch has not been set.

77 - Insufficient Permission

The action cannot be completed because the user does not have the necessary permission.

126 - SQL Server error

Execution failed because of an error.

130 - Ctrl-Break

Execution stopped because of a Ctrl-Break.

400 - Bad request

The command line arguments can't be executed. For example, you may have provided two mutually exclusive switches.

402 - Not licensed

There is no acceptable license. If you have one, use /activateSerial:<SerialKey>. If you don't have a license, please contact sales@red-gate.com for a either a trial extension key or to purchase a license.

499 - Activation cancelled by user

Activation was cancelled because the cancel button was pressed during the process.

500 - Unhandled exception

An unhandled exception occurred. The exception message and stack trace will be included in the output.