This topic describes API errors, trigger conditions for API errors, and relevant solutions.

Format of common error messages: 
ODPS-04CCCCX: General description - Context-related description
API errors are related to the following modules: Web (CCCC ranges from 1000 to 1999, Worker (CCCC ranges from 2000 to 2999), Scheduler (CCCC ranges from 3000 to 3999), Executor (CCCC ranges from 4000 to 4999), and Message Service (CCCC ranges from 5000 to 5999). The following table describes common errors.
Error code Module Severity Trigger condition Processing method
ODPS-0410001:Missing authentication parameters Web-Authentication 1 The error message returned because authentication parameters are missing and error 400 is returned. Add the missing authentication parameters.
ODPS-0410011:Invalid authentication parameters Web-Authentication 1 The error message returned because authentication parameters are invalid and error 400 is returned. Modify the authentication parameters.
ODPS-0410021:Invalid signature method Web-Authentication 1 The error message returned because the signature algorithm is not supported and error 400 is returned. Change the signature algorithm.
ODPS-0410031:Authentication request expired Web-Authentication 1 The error message returned because the authentication request times out and error 400 is returned. Reinitiate the authentication request.
ODPS-0410042:Invalid signature value Web-Authentication 2 The error message returned because the authentication signature is invalid and error 401 is returned. Modify the signature.
ODPS-0410051:Invalid credentials Web-Authentication 1 The error message returned because the user authentication information is invalid and error 401 is returned. Modify the authentication information and reinitiate the authentication request.
ODPS-0420031:Invalid xml in HTTP request body Worker-Request handler 1 The error message returned because the parameter is invalid and error 400 is returned. Modify the parameter.
ODPS-0420041:Missing parameter in HTTP request Worker-Request handler 1 The error message returned because the parameter is missing and error 400 is returned. Add the missing parameter.
ODPS-0420051:Missing parameter in HTTP request Worker-Request handler 1 The error message returned because the parameter is missing and error 400 is returned. Add the missing parameter.
ODPS-0420061:Invalid parameter in HTTP request Worker-Request handler 1 The error message returned because the parameter is invalid and error 400 is returned. Change the parameter to a valid parameter.
ODPS-0420061: Invalid parameter in HTTP request - Fetched data is larger than the rendering limitation. Please try to reduce your limit size or column number Worker-Request handler 1 The error message returned because the number of rows of data in the output exceeds 10,000.
  • Method 1: If you do not need to view more than 10,000 rows of data, include the LIMIT keyword in the SELECT statement to limit the number of rows of data that can be returned. For example, you can execute the select * from sale_detail where region='china' order by total_price limit 3; statement.
  • Method 2: Remove the limit on the number of rows that can be displayed. This way, you can view more than 10,000 rows of data. For more information, see Limited rows are displayed.
  • Method 3: If you want to view more than 10,000 rows of data, you can run the Tunnel Download command to download the instance data that is generated by using the SELECT statement to the on-premises machine. For more information about how to download data of an instance, see Download data of an instance.
ODPS-0420071:Invalid header in HTTP request Worker-Request handler 1 The error message returned because the message header is invalid and error 400 is returned. Modify the message header to a valid header.
ODPS-0420081:Method not allowed Worker-Reqeust handler 1 The error message returned because the method is not supported and error 405 is returned. Change the method to a supported method.
ODPS-0420095:Access Denied Worker-Request handler 5 The error message returned because the user does not have the operation permissions and error 403 is returned. Grant the user the operation permissions based on the error message. For example, if the error message is You have no privilege 'odps:CreateInstance' on {acs:odps:*:projects/maxcompute_dev}, the owner of the maxcompute_dev project must grant the user the CreateInstance permission on the project. For more information about user authorization, see MaxCompute permissions.
ODPS-0420111:Not found the project Worker 1 The error message returned because the project does not exist and error 404 is returned. Change the project name to the name of an existing project.
ODPS-0420121:The project has already existed Worker 1 The error message returned because the project already exists and error 409 is returned. Change the project name to avoid name conflicts.
ODPS-0420131:Invalid project name Worker 1 The error message returned because the project name is invalid and error 400 is returned. Change the project name to a valid name.
ODPS-0420141:Invalid group name Worker 1 The error message returned because the group name is invalid and error 400 is returned. Change the group name to a valid name.
ODPS-0421111:Not found the resource Worker 1 The error message returned because the resource does not exist and error 404 is returned. Change the resource name to the name of an existing resource.
ODPS-0421121:The resource has already existed Worker 1 The error message returned because the resource already exists and error 409 is returned. Change the resource name to avoid name conflicts.
ODPS-0421131:Invalid resource name Worker 1 The error message returned because the resource name is invalid and error 400 is returned. Change the resource name to a valid name.
ODPS-0421141:Invalid resource type Worker 1 The error message returned because the resource type is invalid and error 400 is returned. Change the resource type to a valid type.
ODPS-0421151:Delete resource conflict Worker 1 The error message returned because a conflict occurs when you delete a resource, and error 409 is returned. Check whether the resource can be deleted.
ODPS-0421161:Download resource denied Worker 1 The error message returned because the download of resources is rejected and error 403 is returned. Check whether you have the permissions to download resources.
ODPS-0421173:Download resource error Worker 3 The error message returned because resources fail to be downloaded and error 404 or 500 is returned. Re-download the resources.
ODPS-0421181:Invalid resource content Worker 1 The error message returned because the directory where the resources are saved is invalid and error 400 is returned. Change the resource directory to a valid directory.
ODPS-0421191:Invalid ContentDisposition in HTTP header Worker 1 The error message returned because the value in the Content-Disposition header field is invalid and error 400 is returned. Change the value in the Content-Disposition header field to a valid value.
ODPS-0421201:Add or update resource failed Worker 1 The error message returned because resources fail to be added or updated and error 400 or 500 is returned. Identify the cause of the failure and add or update the resources again.
ODPS-0421213:Save resource error Worker 3 The error message returned because resources fail to be saved and error 500 is returned. Identify the cause of the failure and save the resources again.
ODPS-0422111:Not found the table Worker 1 The error message returned because the table does not exist and error 404 is returned. Change the table name to the name of an existing table.
ODPS-0422121:The table has already existed Worker 1 The error message returned because the table already exists and error 409 is returned. Change the table name to avoid name conflicts.
ODPS-0422131:Invalid table name Worker 1 The error message returned because the table name is invalid and error 400 is returned. Change the table name to a valid name.
ODPS-0422141:Not found the partition Worker 1 The error message returned because the partition does not exist and error 404 is returned. Change the partition name to the name of an existing partition.
ODPS-0422174:Invalid column type Worker 4 The error message returned because the column type is invalid and error 400 is returned. Change the column type to a valid type.
ODPS-0423111:Not found the function Worker 1 The error message returned because the function does not exist and error 404 is returned. Change the function name to the name of an existing function.
ODPS-0423121:The function has already existed Worker 1 The error message returned because the function already exists and error 409 is returned. Change the function name to avoid name conflicts.
ODPS-0423131:Invalid function name Worker 1 The error message returned because the function name is invalid and error 400 is returned. Change the function name to a valid name.
ODPS-0424111:Not found the instance Worker 1 The error message returned because the instance does not exist and error 404 is returned. Change the instance name to the name of an existing instance.
ODPS-0424145:Delete instance conflict Worker 1 The error message returned because a conflict occurs when you delete an instance and error 409 is returned. Check whether the instance is in use.
ODPS-0424151:Invalid state setting Worker 1 The error message returned because the parameter is invalid and error 400 is returned. Modify the parameter.
ODPS-0425111:Not found the job Worker 1 The error message returned because the job does not exist and error 404 is returned. Change the job name to the name of an existing job.
ODPS-0425121:The job has already existed Worker 1 The error message returned because the job already exists and error 409 is returned. Change the job name to avoid name conflicts.
ODPS-0425131:Invalid job name Worker 1 The error message returned because the job name is invalid and error 400 is returned. Change the job name to a valid name.
ODPS-0426111:Invalid event parameter Worker 1 The error message returned because the event parameter is invalid and error 400 is returned. Change the event parameter to a valid parameter.
ODPS-0426123:The event has already existed Worker 3 The error message returned because the event already exists and error 409 is returned. Change the event name to avoid name conflicts.
ODPS-0426133:Not found the event Worker 3 The error message returned because the event does not exist and error 404 is returned. Change the event name to the name of an existing event.
ODPS-0426145:Invalid event operation Worker 5 The error message returned because the event operation is invalid and error 400 is returned. Make sure that the event operation is valid.