Out-of-Date Error Codes

If an error occurs in an API, no result is returned. You can locate the error cause based on the error codes of each API. If an error occurs in API calling, HTTP status code 4xx or 5xx is returned. The response body contains the specific error code and information.

Error Response Body Format

If an error occurs during API calling, an error code and a message will be displayed. The following shows an error response body.

{ 
    "error_msg": "The boot partition does not exist.", 
    "error_code": "SMS.6531" 
}

In the response body, error_code is an error code, and error_msg provides information about the error.

Error code description

**Table 1** Error code description
Status Code	Error Code	Description
400	SMS.1038	Only the tasks that are created or monitored can be paused.
400	SMS.1039	Only paused tasks can be resumed.
400	SMS.1040	Only migration tasks that fail to be created or migrated can be restarted.
403	SMS.2002	You do not have permission to perform this operation.
401	SMS.2003	Invalid HTTP request method.
401	SMS.2004	The requested content contains more than 10,240 bytes.
401	SMS.2005	The request type Content-Type is not specified.
401	SMS.2006	The request type must be application or json.
500	SMS.2007	Background exception
400	SMS.2009	The command sent by the client is inconsistent with that on the SMS service.
401	SMS.2013	The source server already exists.
400	SMS.2015	The in-progress or stopped tasks cannot be deleted.
400	SMS.2206	The OS type of the source server is not in the migration support list.
400	SMS.2216	Failed to create the migration task because the specified source server does not exist.
403	SMS.2248	The resource that does not belong to you cannot be deleted.
404	SMS.2252	No migration task is associated with the specified source server.