Error codes
Common Dataphin error codes with causes and solutions.
|
Classification |
Details |
|
Bbox |
|
|
TaskScheduler |
|
|
OS |
|
|
Project |
|
|
DataProcess |
|
|
ComputeEngine |
|
|
DataSource |
DPN.Bbox.Any
Cause: Internal system error.
Solution: Submit a ticket, or contact Dataphin helpdesk for assistance.
DPN.Bbox.MetaCenterServiceError
Cause: The metadata service is unavailable.
Solution: Submit a ticket, or contact Dataphin helpdesk for assistance.
DPN.Bbox.ModelNotFound
Cause: The model corresponding to the specified model ID was not found.
Solution: Submit a ticket, or contact Dataphin helpdesk for assistance.
DPN.Bbox.ServerError
Cause: Internal system error.
Solution: Submit a ticket, or contact Dataphin helpdesk for assistance.
DPN.Commons.InternalError
Cause: Internal system error.
Solution: Submit a ticket, or contact Dataphin helpdesk for assistance.
DPN.Os.InternalError
Cause: Internal system error.
Solution: Submit a ticket, or contact Dataphin helpdesk for assistance.
DPN.TaskScheduler.Api.AccessTokenNotFound
Cause: Internal system error.
Solution: Submit a ticket, or contact Dataphin helpdesk for assistance.
DPN.DataProcesss.SqlLogicValidationError
Cause: SQL statement validation error.
Solution: Check the SQL statement to ensure that it is correct.
DPN.TaskScheduler.Global.UncategorizedError
Cause: Internal scheduling system error.
Solution: Submit a ticket, or contact Dataphin helpdesk for assistance.
DPN.TaskScheduler.Util.GsonDeserializeError
Cause: An error occurred during Gson deserialization.
Solution: Submit a ticket, or contact Dataphin helpdesk for assistance.
DPN.Bbox.AttributeMissing
Cause: The identifier field for the statistical period of the atomic metric was deleted, and the corresponding logical field cannot be found by field ID.
Solution: Reset the identifier field for the statistical period of the atomic metric. For more information, see Create an atomic metric .
DPN.Bbox.CatalogNotFound
Cause: The public English name of the business category or project is incorrect.
Solution: Check the SQL code for spelling errors in the public English name of the business category or project.
DPN.Bbox.DimensionNotFound
Cause: The dimension corresponding to the specified dimension ID was not found.
Solution: In the Standardized Modeling module, search for the dimension by its English name to check whether it exists.
-
If the dimension was deleted, modify the current task object and submit or publish it again.
-
If the dimension is offline, publish or submit it again.
If the error persists after you perform these operations, submit a ticket , or contact Dataphin helpdesk for assistance.
DPN.Bbox.FieldNotFound
Cause: The field corresponding to the specified field name was not found.
Solution: Check whether the field exists in the corresponding model. In Asset Map, search by keyword to view the table details and verify that the table contains the field that caused the error. For more information about how to search for a table, see Search for data .
DPN.Bbox.IllegalSql
Cause: The SQL code segment is invalid.
Solution: Check whether the SQL segment from the error message is valid in the context of the entire SQL statement. For more information about supported MaxCompute syntax, see Common commands .
DPN.Bbox.LogicModelException
Cause: The logical model definition is invalid.
Solution: Modify the model based on the provided error message.
DPN.Bbox.MetadataNotFound
Cause: The metadata corresponding to the specified table name was not found.
Solution: Verify the table name is correct. In Asset Map, search by keyword to view the table details and confirm that the table exists and its name is spelled correctly. For more information about how to search for a table, see Search for data .
DPN.Bbox.PublishFail
Cause: Task publish failed.
Solution: Troubleshoot the issue based on the error message in the publish record.
DPN.Bbox.UnsupportedCatalogVariable
Cause: The variable that represents the public English name of the business category or project is incorrect.
Solution: Modify the variable name in the SQL statement to the public English name of the business category or project. The placeholder for the public English name of a project is ${public_english_name_of_project}. The placeholder for the public English name of a business category is ${public_english_name_of_business_category}.
DPN.ComputeEngine.ConfigRepeat
Cause: The compute engine configuration you are creating or editing duplicates an existing one.
Solution: Modify the compute engine configuration.
DPN.ComputeEngine.MaxComputeAkNotMatchCurrentTenant
Cause: The AccessKey of the MaxCompute compute engine does not belong to the Alibaba Cloud account that owns the Dataphin instance. Solution: Check the MaxCompute compute engine AccessKey configuration.
The MaxCompute project and the Dataphin instance must belong to the same Alibaba Cloud account.
DPN.ComputeEngine.MaxComputeAkQueryMainAccountError
Cause: An error occurred when querying the Alibaba Cloud account for the MaxCompute compute engine AccessKey.
Solution: Check the MaxCompute compute engine AccessKey configuration.
DPN.DataSource.UrlSsrfCheckFailed
Cause: Access to Dataphin internal systems is not allowed.
Solution: Check the data source URL configuration.
DPN.DataProcess.NodeOutputNameAlreadyExistWithNodeName
Cause: The node output name already exists.
Solution: Modify the node output name. For more information, see Configure basic information for a node .
DPN.Os.CatalogNotFound
Cause: The catalog preceding the table was not found.
Solution: Check the following to troubleshoot the issue:
-
Check whether the Dataphin project or business category exists.
-
Check the variable reference format in the query statement:
${public_english_name_of_project}.physical_tableor${public_english_name_of_business_category}.logical_table.
DPN.Os.ColumnAmbiguous
Cause: The field in the SQL code is ambiguous.
Solution: Add the table name before the field name or modify the SQL code.
DPN.Os.ColumnAuthCheckFailed
Cause: You do not have permission for the field.
Solution: Request permission for the field. For more information, see Request, renew, and return table permissions .
DPN.Os.ColumnNotFound
Cause: The field was not found.
Solution: Check the following to identify the cause of the error:
-
If the error occurs when you submit the node, check whether the table exists in the development environment.
-
If the error occurs when you publish the node, check whether the table exists in the production environment.
DPN.Os.SqlParserFailed
Cause: Failed to parse the SQL statement.
Solution: Check the SQL statement for syntax errors. For more information about supported MaxCompute syntax, see Common commands .
DPN.Project.DisplayNameDuplicated
Cause: The project name you are creating or editing duplicates an existing project name.
Solution: Modify the project name. For more information, see Add a project member.
DPN.Project.NoPermission
Cause: The current member does not have administrative permission for any project.
Solution: Contact a super administrator or another project administrator to add the member as an administrator to a project.
DPN.Project.ParameterError
Cause: Invalid project parameter.
Solution: Identify the issue based on the invalid parameter returned. If you need help, submit a ticket , or contact Dataphin helpdesk for assistance.
DPN.Project.ProjectComputeEngineValidateFailed
Cause: Failed to validate the compute engine during project creation.
Solution: Check the following to identify the cause of the error:
-
Check the connectivity of the compute engine. For more information, see Network Connectivity Solutions.
-
Ensure that the compute source configuration is correct.
DPN.TaskScheduler.Api.RequestError
Cause: An error occurred when sending a remote request.
Solution: This may be caused by a server-side network issue. Try again, or contact Dataphin helpdesk for assistance.
DPN.TaskScheduler.Client.ApiError
Cause: An error occurred when calling a scheduling system API. See the error details for the specific cause.
Solution: Find the solution based on the error code in the error details. If you need help, contact Dataphin helpdesk for assistance.
DPN.TaskScheduler.Task.TaskToRerunNotFinished
Cause: Rerunning an instance that is already running is not supported.
Solution: Rerun the instance after its status changes to Successful or Failed.
DPN.TaskScheduler.Node.NodeParamParseError
Cause: Failed to parse the node parameter settings. For example, KeyA=$KeyB
Solution: Check the node parameter settings and ensure that the parameter values can be parsed correctly.
DPN.TaskScheduler.Node.IllegalNodeIdFormat
Cause: The format of the node ID is invalid. It should be [n_number].
Solution: Check the node ID format and try the call again. If the error persists, submit a ticket , or contact Dataphin helpdesk for assistance.
DPN.TaskScheduler.Node.NodeDependencyCycleDetected
Cause: A circular dependency exists in the upstream dependencies of the node.
Solution: Check for and remove the circular upstream dependency, and then submit or publish the node again.
DPN.TaskScheduler.Node.NodeNotFoundByIdAndTenantId
Cause: The node corresponding to the specified node ID was not found.
Solution: Check whether the node ID is correct and whether the corresponding node has been deleted or is offline.
DPN.TaskScheduler.Node.NodeNotFoundByNodeId
Cause: The node corresponding to the specified node ID was not found.
Solution: Check whether the node ID is correct and whether the corresponding node has been deleted or is offline.
DPN.TaskScheduler.Node.NodeNotFoundByOutputName
Cause: The node corresponding to the specified output name was not found.
Solution: Check whether the node output name is correct and whether the corresponding node has been deleted or is offline.
DPN.TaskScheduler.Node.NodeNotFoundByOutputNameAndTenantId
Cause: The node corresponding to the specified output name was not found.
Solution: Check whether the node output name is correct and whether the corresponding node has been deleted or is offline.
DPN.TaskScheduler.Node.NodeOutputNameEmpty
Cause: The node output name is empty.
Solution: Specify a node output name. For SQL nodes, the recommended format for the output name is [project_name].[table_name].
Node output names must be unique within the system.
DPN.TaskScheduler.Node.NodeOutputNameOccupied
Cause: The current node output name is already in use.
Solution: The specified output name is already in use by another task. For SQL tasks, the recommended format for the output name is [project_name].[table_name].
Node output names must be unique within the system.
DPN.TaskScheduler.Node.NodeToDeleteContainsDownstreams
Cause: A downstream dependency was detected for the node that you are trying to delete.
Solution: Remove the dependency of the downstream node on the current node and try again.
DPN.TaskScheduler.Node.OutputNameToUpdateContainsDownstream
Cause: A downstream dependency was detected for the output name that you are trying to modify.
Solution: Remove the dependency of the downstream node on the current node output name and try again.
DPN.TaskScheduler.Resource.ResourceNotFoundByResourceCode
Cause: The resource corresponding to the specified resource name was not found. This can be caused by an invalid resource name, a deleted resource, or an unavailable resource service.
Solution: Ensure that the resource exists in the current project and that the resource reference format is correct. The resource reference format is @resource_reference{"[resourcecode]"};. If the issue persists after troubleshooting, contact Dataphin helpdesk for assistance.
DPN.TaskScheduler.Task.IllegalTaskIdFormat
Cause: The provided task ID format is invalid.
Solution: Check whether the instance ID format is [t_number] and then try the call again.
DPN.TaskScheduler.Task.TaskNotFoundByTaskId
Cause: The instance corresponding to the specified instance ID was not found.
Solution: Confirm that the instance exists before performing the operation. If you are on a webpage, refresh the page and try again. Instance retention policy:
-
Recurring instances and their operational logs are retained for 15 days.
-
One-time instances, data backfill instances, and their operational logs are retained permanently.
DPN.TaskScheduler.Task.TaskNotFoundByTaskIdAndTenantId
Cause: The instance corresponding to the specified instance ID was not found.
Solution: Confirm that the instance exists before performing the operation. If you are on a web page, refresh the page and try again. Instance retention policy:
-
Recurring instances and their operational logs are retained for 15 days.
-
One-time instances, data backfill instances, and their operational logs are retained permanently.
DPN.TaskScheduler.Task.TaskRunning
Cause: Rerunning a running instance is not supported.
Solution: Rerun the instance after it finishes. Only instances in the Successful or Failed state can be rerun.
DPN.TaskScheduler.Task.TaskToKillHasFinished
Cause: Stopping an instance that is not running is not supported.
Solution: The instance has already finished running. You do not need to stop it.
DPN.TaskScheduler.Task.TaskToResumeNotPaused
Cause: Resuming an instance that is not paused is not supported.
Solution: The current instance is not paused. You do not need to resume it.
DPN.TaskScheduler.Tenant.DatasourceNotFoundById
Cause: The data source corresponding to the specified data source ID was not found. The data source may have been deleted.
Solution: Check whether the data source exists, or contact the node owner to check the data source configuration of the node.
DPN.TaskScheduler.Tenant.FetchProjectDatasourceError
Cause: Failed to obtain the project's compute engine. The Dataphin compute engine service may be temporarily unavailable.
Solution: The Dataphin compute engine service may be temporarily unavailable. Try again later. If the issue persists, contact Dataphin helpdesk.
DPN.TaskScheduler.Tenant.FetchTenantDatasourceError
Cause: Failed to obtain the project's compute engine. The Dataphin compute engine service may be temporarily unavailable.
Solution: The Dataphin compute engine service may be temporarily unavailable. Try again later. If the issue persists, contact Dataphin helpdesk.
DPN.TaskScheduler.Tenant.InvalidTenantId
Cause: The current tenant is unavailable. This may be because the service has expired and has not been renewed, or Dataphin has not been activated.
Solution: Activate or renew Dataphin. For more information, see Activate Dataphin or Renewal.
DPN.TaskScheduler.Node.NodeParamCycleReferenceDetected
Cause: A circular dependency exists in the node parameter settings. For example, KeyA=$KeyB; KeyB=$KeyA or bizdate=$bizdate.
Solution: Check whether the node parameter settings contain statements such as KeyA=$KeyB; KeyB=$KeyA or bizdate=$bizdate.