Error messages for resource Migrate

Lists common error response fields and examples for Migrate resource requests.

If an error occurs when executing an option of resource Migrate, an HTTP return code not equal to 200 is returned.

In addition, there is output in the JSON data, which can contain up to three pieces of information.

“Error” always appears in the output with the problem description, e.g.
HTTP/1.1 400 Bad Request

{"Error": "Method 'STARRT' is not supported"}
In addition, the “Reason” for the problem can be displayed for some error messages, e.g.
HTTP/1.1 400 Bad Request

{"Error": "Migrate failed",
"Reason": "No parameters specified to define the migration process"}
Finally, the actual “Exception” is displayed if such an exception was recognized in the “Reason” as the cause of a problem, e.g.
HTTP/1.1 500 Internal Server Error

{"Error": "Migration failed.",
"Reason": "Error connecting to Agent. Message received:",
"Exception": "java.net.ConnectException: Connection refused: connect"}

If the migration process fails (connection error, database error, ...), it is also recommended to take a look at the “TRACE” log file, as it contains a detailed error message (including possible exceptions). In the event of an error the contents of the log files are also included in the output to make it easier to investigate the cause.