Error Messages

The following format is used throughout the document to list out the error messages
  • Error Message
  • Issue
  • Resolution
  • Cause

4.1 Login

4.1.1 Error Message: User does not exist.

Issue: When attempting to login to the platform with username and password, the following error is received: “User does not exist.”

Resolution: Please make sure that you entered the username correctly. Please register as a user in the platform if you haven’t done that by now.

Cause: Typically, the error indicates that the username does not match with an existing user in the system.

4.2 New Entity Recognizers

4.2.1 Error Message: Invalid File format

Issue: When the user is trying to upload a CSV file when creating a new entity recognizer and the error is received.

Resolution: Please check the file type and upload files that are of the specified type.

Cause: When the User tries to upload a file of a type different from the accepted types.

4.2.2 Error Message: Task is still in starting state, please wait for some time to stop

Issue: Starting a task while it is in progress.

Resolution: Please try after some time.

Cause: Given task is in progress. Please wait till the task stops.

4.2.3 Error Message: Task is not running, wait for task to start before stopping again

Issue: trying to stop a task which is already stopped.

Resolution: please start a task before try to stop.

Cause: stopping a task which is already stopped.

4.2.4 Error Message: Task can be resumed only in stopped state

Issue: Attempting to resume a running task.

Resolution: stop a running task before try to resume.

Cause: Attempting to resume a running task.

4.2.5 Error Message: User is not authorized to perform any action on task

Issue: User trying to operate on a task without having proper access to the task.

Resolution: Contact administrator for access and try again.

Cause: Access issue.

4.2.6 Error Message: domain name already exists

Issue: Domain name entered is in conflict with the existing domain.

Resolution: try a unique domain name.

Cause: Domain name conflict.

4.2.7 Error Message: Domain Invalid

Issue: Entered domain name is invalid.

Resolution: enter proper and unique domain name.

Cause: non-compliant domain name.

4.2.8 Error Message: Domain

Issue: In domains.is_user_action_valid, User is not permitted to perform the action.

Resolution: Request for proper access from the admin.

Cause: Access denied.

4.2.9 Error Message: Unable to update domain description, please try again later.

Issue: Database Is updating.

Resolution: Please try after some time.

Cause: updating domain description while Database is updating.

4.2.10 Error Message: Delete operation failed, dependent datasets should be deleted before deleting the domain.

Issue: Error while deleting a dataset.

Resolution: delete dependent data sets before deleting the root node.

Cause: Trying to delete a dataset before deleting depending datasets

4.2.11 Error Message: Unable to delete the glue database as there are tables associated with it. Contact Administrator

Issue: Issue in deleting glue database.

Resolution: delete tables associated with glue database before deleting glue database.

Cause: trying to delete glue db before deleting tables associated with it.

4.2.12 Error Message: Invalid DWH type setting in the backend, contact administrator

Issue: Issue in the backend.

Resolution: Contact Cloudwick support.

Cause: Backend operation error.

4.2.13 Error Message: Unable to get the values for user from user-dataset table

Issue: Issue with access.

Resolution: check with admin regarding the access.

Cause: user does not have required access.

4.2.14 Error Message: There was an error while retrieving search results. Please try after some time.

Issue: possible system error.

Resolution: please try after some time. If the issue persists, please contact the support team.

Cause: possible system error.

4.2.15 Error Message: Unable to connect to ElasticSearch with the given endpoint.

Issue: Incorrect endpoint.

Resolution: Provide correct endpoint name.

Cause: provided endpoint is not correct.

4.2.16 Error Message: Unable to get the values for the user.

Issue: no values exist for the user.

Resolution: Retrieval can happen on the existing values.

Cause: trying to query an empty database.

4.2.17 Error Message: Unable to raise the request. Please try after some time

Issue: User has access to the dataset.

Resolution: since the user has already has access to the dataset there is no need to request again.

Cause: raising multiple requests on the same dataset.

4.2.18 Error Message: Unable to raise the request. Please try after some time

Issue: access request is in place already.

Resolution: please contact the owner of the dataset.

Cause: cannot raise multiple access requests on a single dataset.

4.2.19 Error Message: Could not complete the request. Please try again

Issue: Application is refreshing.

Resolution: please try again after some time.

Cause: application refresh is in progress.

4.2.20 Error Message: A data classification entry with name exists, please choose different name

Issue: name given for data classification is already existing.

Resolution: try with a unique name.

Cause: name conflict with an existing classification name.

4.2.21 Error Message: Data classification name cannot contain white spaces

Issue: data classification name given does not confirm to the naming standard.

Resolution: provide a name with no whitespaces.

Cause: data classification name is not in compliance with naming standards.

4.2.22 Error Message: Invalid Data classification Name

Issue: data classification name given does not confirm the naming standard.

Resolution: please provide proper name for the data classification.

Cause: data classification name is not in compliance with naming standards.

4.2.23 Error Message: Invalid UserID

Issue: user is not authorised to perform the action.

Resolution: Request for proper access from the administrator.

Cause: Access denied due to unauthorised action.

4.2.24 Error Message: User is not authorized to query the dataset.

Issue: User has to be equipped with proper access.

Resolution: Request for proper access from the administrator.

Cause: Access denied due to unauthorised action.

4.2.25 Error Message: Allowed only one query per request.

Issue: User is trying to run multiple queries at a time.

Resolution: Please run a single query at a time.

Cause: since the user is trying to run multiple queries at the same time the issue is caused. Please run a single query at a time.

4.2.26 Error Message: Out of range for items per page, Limit is 1000

Issue: trying to retrieve more than 1000 in a single page.

Resolution: provide the value between 0(zero) to 1000.

Cause: attempting to retrieve more than 1000 items.

4.2.27 Error Message: Invalid sortorder param, sortorder must be in [“desc”, “asc”]

Issue: sort order is not proper.

Resolution: sorting order should be either in Asc (Ascending) or Desc (Descending).

Cause: Incorrect sort order.

4.2.28 Error Message: The dashboard already exists, with this name.

Issue: User is attempting to create a dashboard with an existing name.

Resolution: Provide a unique while creating a dashboard.

Cause: Dashboard name provided while creating is already exists.

4.2.29 Error Message: user does not exist in the system

Issue: create dashboard failed as %s user does not exist in the system.

Resolution: contact admin team.

Cause: attempting creating a dashboard for a user who does not exist

4.2.30 Error Message: ‘Dashboard delete api request %s raised by %s for Dashboard %s is failed with error %s.’

Issue: possible system error.

Resolution: try again after some time. Contact admin team if the issue persists.

Cause: possible system error.

4.2.31 Error Message: User action is not permitted.

Issue: User is not authorised to access the page.

Resolution: Request for proper access from the administrator.

Cause: Unauthorised access.

4.2.32 Error Message: Not authorized to see dashboard authorized users

Issue: User is not authorised to access the authorised users.

Resolution: Request for proper access from the administrator.

Cause: Unauthorised operation. Access denied.

4.2.33 Error Message: Failed to fetch the dashboard details, try again later.

Issue: User is attempting to fetch the details of the dashboard details without having proper access.

Resolution: Contact administrator for proper access.

Cause: Unauthorised access.

4.2.34 Error Message: System Error

Issue: possible system error.

Resolution: try again after some time. Contact admin team if the issue persists.

Cause: possible system error.

4.2.35 Error Message: Failed to retrieve dashboard.

Issue: Dashboard Id parameter is not found for dashboard name.

Resolution: verify the dashboard name. contact admin if the problem persists.

Cause: invalid input.

4.2.36 Error Message: user does not exist in the system

Issue: attempting to retrieve dashboard for a user who does not have proper access.

Resolution: contact admin for proper access.

Cause: unauthorised access.

4.2.37 Error Message: User action is not permitted

Issue: User cannot revoke/grant access to default groups.

Resolution: contact administrator.

Cause: Attempting to remove/add a user from/to default groups.

4.2.38 Error Message: Access could not be provided

Issue: The user is already present.

Resolution: since the user is already present in the system no need to provide the access.

Cause: Attempting to provide access to the user who is already equipped with the requesting access.

4.2.39 Error Message: Unable to provide access

Issue: attempting to retrieve the list of users who have requested the access while no one has requested.

Resolution: Retrieve the list of requested users as soon as user/s requests.

Cause: no user requests present.

4.2.40 Error Message: user does not exist in the system

Issue: attempting to retrieve the list of users who have requested the access while no one has requested.

Resolution: Can deny request only when a request is present.

Cause: no user requests present.

4.2.41 Error Message: access denied

Case-1

Issue: Dashboard access failed as the user accessing it does not exist in the system.

Resolution: please request the admin to check the validity of the user’s credentials.

Cause: unauthorised operation. Access denied.

Case-2

Issue: the user does not have proper access.

Resolution: please contact the admin for access.

Cause: unauthorised operation. access denied.

4.2.42 Error Message: user access type not valid

Issue: Provide Dashboard access failed as %s access type not valid.

Resolution: verify the access type you are trying to provide. Contact the administrator if the error persists.

Cause: access type attempting to provide does not exist.

4.2.43 Error Message: The user is not authorized to grant the access to dashboard.

Issue: Attempting for an unauthorised action.

Resolution: contact admin and request for necessary access.

Cause: unauthorised operation. Access denied.

4.2.44 Error Message: Unable to provide the access. Please try after some time.

Issue: possible server down or refresh is in progress.

Resolution: try after some time. If the issue persists, please contact the support team.

Cause: Attempting provide access while the system is being refreshed or possible server down.

4.2.45 Error Message: No dashboard was deleted as the dashboard name is not found.

Issue: the given dashboard name is not present as the dashboard does not exist.

Resolution: verify and enter the correct dashboard name.

Cause: incorrect dashboard name.

4.2.46 Error Message: Invalid DatasetId

Issue: the dataset entered is invalid.

Resolution: enter valid dataset id and try again.

Cause: the provided dataset is not correct.

4.2.47 Error Message: Unable to complete model operation. Please try again later.

Issue: System error.

Resolution: Please try again after some time. If the error persists, please contact the support team.

Cause: System error.

4.2.48 Error Message: Event doesn’t have required keys to carry out this operation

Issue: Keys that are missing and which are required to carry out the operation requested.

Resolution: Provide required keys and try again.

Cause: Keys that are missing and which are required to carry out the operation requested.

4.2.49 Error Message: Out of range for items per page, Limit is 1000.

Issue: Trying to retrieve more than 100 items in a page.

Resolution: provide value between 0(Zero) to 1000.

Cause: input provided is more than 1000.

4.2.50 Error Message: No model present with this model Id {}

Issue: Id provided is not available in the database.

Resolution: provide a valid and existing id.

Cause: model id provided is not available.

4.2.51 Error Message: Model name is already present, give a different name for model

Issue: using an existing model name while creating a new one.

Resolution: try with a different and non-existing name.

Cause: provided name is in conflict with an existing model name.

4.2.52 Error Message: Error updating model

Issue: failed to update metadata in dynamodb with response.

Resolution: Try after some time. Contact admin team if the issue persists.

Cause: possible server error.

4.2.53 Error Message: delete error

Issue: Trying to delete a non-existing model.

Resolution: verify the name of the model you want to delete.

Cause: no model exists with the given name.

4.2.54 Error Message: system error

Issue: possible server down.

Resolution: try after some time. If the issue persists, please contact the support team.

Cause: possible system error.

4.2.55 Error Message: Invalid body structure either of ArtifactsLocation and ExistingModelResource must exist

Issue: neither artifacts location nor existing model resource exists in event body.

Resolution: provide artifact location or existing model resource with a valid body structure.

Cause: invalid body and both artifact location and existing model resource is missing.

4.2.56 Error Message: Metadata doesn’t have any recognizer with id

Issue: provided recognizer id is not present with the system.

Resolution: verify the name of the recognizer. If the problem persists, please contact the support team.

Cause: no recognizer in the name given.

4.2.57 Error Message: User doesn’t have permissions to train a recognizer on the dataset.

Issue: unauthorised operation.

Resolution: request access to train a recognizer.

Cause: attempting an unauthorised operation.

4.2.58 Error Message: This is the only version available for recognizer name and cannot be reverted back. You can consider deleting it.

Issue: trying to revert to a previous version when there is no previous version.

Resolution: since it is the only version available you can’t revert, but you can consider deleting it.

Cause: no previous version to revert

4.2.59 Error Message: User doesn’t have permissions to create a recognizer. User needs to have owner/read-only access on dataset with id.

Issue: unauthorised action.

Resolution: request admin for access to create a recognizer.

Cause: unauthorised operation. Access denied.

4.2.60 Error Message: Metadata doesn’t have any recognizer with id.

Issue: Recognizer id provided does not exist in the metadata.

Resolution: verify the id you have entered. Contact admin if the problem persists.

Cause: no recognizer exists with the given name.

4.2.61 Error Message: Metadata is incomplete for this request to be carried out.

Issue: metadata incomplete.

Resolution: contact admin team.

Cause: metadata incomplete.

4.2.62 Error Message: NIL

Issue: trying to train an already trained recognizer.

Resolution: contact admin.

Cause: attempting override an already trained recognizer.

4.2.63 Error Message: Metadata has more than one value for recognizer with id

Issue: multiple entries for the given id in the metadata.

Resolution: select the one you want to.

Cause: multiple entries present in the metadata.

4.2.64 Error Message: Metadata is incomplete for this request to be carried out

Issue: metadata is not updated.

Resolution: please try again after some time. If the error persists, please contact the admin team/ support team.

Cause: metadata is in a refreshing state.

4.2.65 Error Message: Failed to update cers list in groups, try again later

Issue: probable system error or data is updating.

Resolution: please try again after some time. If the error persists, contact the support team.

Cause: probable system error or data is updating.

4.2.66 Error Message: No information available about resource.

Issue: no metadata for resources with given id.

Resolution: contact admin.

Cause: did not encounter metadata for resource with id %s.

4.2.67 Error Message: Entity recognizer with name {} already exists

Issue: Attempting to create a recognizer with an existing name.

Resolution: try with a unique name which is not present already.

Cause: Given recognizer name is in conflict with an existing name.

4.2.68 Error Message: Entity recognizer with recognizer id {} doesn’t exist

Issue: trying to operate on a non-existing entity recognizer.

Resolution: please verify the recognizer id. If the error persists contact admin team.

Cause: invalid recognizer id.

4.2.69 Error Message: Entity recognizer with recognizer id {} is in TRAINING status and cannot be deleted.

Issue: attempting to delete a recognizer while it is in training status.

Resolution: wait until the recognizer exits from training status.

Cause: invalid operation.

4.2.70 Error Message: couldn’t connect to dynamodb table with error

Issue: possible system error.

Resolution: please try after some time. If the issue persists contact support team.

Cause: possible system error.

4.2.71 Error Message: following permission missing.

Issue: attempting to access without having proper access.

Resolution: contact admin team for proper access.

Cause: unauthorised operation.

4.2.72 Error Message: Notebook with name {} already exists, choose different name.

Issue: trying to create a notebook with an already existing name.

Resolution: try to create the notebook with a different name.

Cause: notebook name conflict.

4.2.73 Error Message: Invalid EndpointId:

Issue: given endpoint id does not match.

Resolution: please verify and provide a valid endpoint id.

Cause: endpoint id given is not present.

4.2.74 Error Message: GlueEndpoint is already assigned.

Issue: the given endpoint is already assigned to some other user.

Resolution: try for a different endpoint.

Cause: endpoint is assigned to someone else.

4.2.75 Error Message: Glue endpoint {} must be in ready state

Issue: attempting to stop a glue endpoint while it is in stopped state.

Resolution: an endpoint can only be stopped when it is in ready or running state.

Cause: invalid operation.

4.2.76 Error Message: GlueEndpointId must be in object body

Issue: GlueEndpointId is either missing or not present in the object body.

Resolution: make sure the GlueEndpointID is present in the object body.

Cause: GlueEndpointId must be in object body.

4.2.77 Error Message: Failed to update notebooks list in groups, try again later

Issue: possible system error or system is being refreshed.

Resolution: please try after some time. If the issue persists contact admin/support team.

Cause: possible system down or system being refreshed.

4.2.78 Error Message: Notebook with ID {} doesn’t exist.

Issue: note is not present in the system.

Resolution: verify the notebook id and provide the correct notebook id.

Cause: invalid notebook id.

4.2.79 Error Message: Notebook instance must be in Stopped state.

Issue: attempting to run a notebook while it is running.

Resolution: a notebook must be in stopped status before running.

Cause: invalid operation.

4.2.80 Error Message: VolumeSizeInGB must be between 5 to 16000 (in GB)

Issue: provided volume size is out of the range (5 to 16000).

Resolution: provide the value between 5 to 16000.

Cause: invalid input.

4.2.81 Error Message: Notebook instance must be in a Stopped state because it is a legacy notebook and so need to attach new role.

Issue: Notebook instance must be in a Stopped state because it is a legacy notebook and so need to attach a new role.

Resolution: stop instance and try to update the new role.

Cause: Notebook instance must be in a Stopped state because it is a legacy notebook and so need to attach a new role.

4.2.82 Error Message: Invalid operation parameter, supported values “[start, stop, update, update-access]”

Issue: operation parameters provided are not valid.

Resolution: provide only Start, stop, update, update-access operational parameters.

Cause: invalid operational parameters.

4.2.83 Error Message: Notebook with ID {} does not exist.

Issue: Trying to delete a notebook which is not present.

Resolution: verify the notebook id you have provided. Contact admin team if the error persists.

Cause: invalid input.

4.2.84 Error Message: Invalid elements found in input fields

Issue: invalid inputs while creating etl job.

Resolution: provide correct inputs while creating etl job. Please contact admin team for input parameters.

Cause: invalid input.

4.2.85 Error Message: JobName cannot be empty.

Issue: job name is provided while creating etl job.

Resolution: provide a unique job name while creating an etl job.

Cause: no job name provided while creating an etl job.

4.2.86 Error Message: ETLJobType cannot be empty.

Issue: etl job type is not provided.

Resolution: provide proper job type.

Cause: no etl job type is provided while creating.

4.2.87 Error Message: Datasets cannot be empty.

Issue: provided datasets are empty.

Resolution: provide a non-empty dataset.

Cause: empty dataset provided to operate on.

4.2.88 Error Message: Job {} already exists. Choose a different name.

Issue: provide a job name is already present.

Resolution: job name should be unique.

Cause: job name conflicts with the existing job name.

4.2.89 Error Message: Allocated capacity parameter is not in valid range between 2 to 100

Issue: provided capacity parameter value is out of bound.

Resolution: there should be a minimum of 1 to a maximum of 100 values for capacity parameters.

Cause: invalid value provided.

4.2.90 Error Message: Unable to create glue etl job with error {}

Issue: possible system error or system is getting refreshed.

Resolution: please try after some time. Contact support/admin team if the problem persists.

Cause: possible system error or system is getting refreshed.

4.2.91 Error Message: Failed to update jobs list in groups, try again later

Issue: possible system error or system is getting refreshed.

Resolution: please try after some time. Contact support/admin team if the problem persists.

Cause: possible system error or system is getting refreshed.

4.2.92 Error Message: User {} is not the owner of the job {} to be added

Issue: non-owner is trying to add a job to a group.

Resolution: only the owner can make changes to the group.

Cause: unauthorised access.

4.2.93 Error Message: Failed to update jobs list in groups, try again later

Issue: possible system error or refresh is in progress.

Resolution: try again after some time. Contact admin team if the issue persists.

Cause: possible system error or refresh is in progress.

4.2.94 Error Message: Unable to delete job. Please try again

Issue: possible system down or refresh in progress.

Resolution: try after some time. Contact admin team if the issue persists.

Cause: possible system down or refresh in progress.

4.2.95 Error Message: User is not owner to perform this operation

Issue: user trying to perform this operation without having proper credentials.

Resolution: contact admin team for proper access.

Cause: unauthorised action. Access denied.

4.2.96 Error Message: Could not complete the request. Please try again

Issue: possible system error or refresh is in progress.

Resolution: try again after some time. Contact admin team if the issue persists.

Cause: possible system error or refresh is in progress.

4.2.97 Error Message: GlueEndpoint with ID {} doesn’t exist

Issue: trying to create a glue endpoint with an existing name.

Resolution: try with a unique name which is not already used.

Cause: invalid input. Given name is in conflict with an existing glue endpoint name.

4.2.98 Error Message: Unable to create dev endpoint with error

Issue: trying to create a glue endpoint with an existing name.

Resolution: try with a unique name which is not already used.

Cause: invalid input. Given name is in conflict with an existing glue endpoint name.

4.2.99 Error Message: while updating glue endpoints

Issue: possible system error or system in refresh state.

Resolution: try again after some time. Contact admin/support team if the issue persists.

Cause: possible system error or system in refresh state.

4.2.100 Error Message: glue_endpoint with ID {} doesn’t exist.

Issue: the id which is provided is not present in the system.

Resolution: please verify the id provided and try again.

Cause: no such id is present in the system.

4.2.101 Error Message: Glue endpoint must be in ready state to make any updates to it.

Issue: updating glue endpoint while it is not in a ready state.

Resolution: make sure the endpoint is in ready state before making any updates to it.

Cause: invalid action.

4.2.102 Error Message: Invalid operation parameter, supported values [update, update-access]

Issue: the operation provided is invalid.

Resolution: operation parameters can only be either update or update-access.

Cause: invalid input.

4.2.103 Error Message: glue_endpoint with ID {} doesn’t exist.

Issue: attempting to delete a non-existent glue-endpoint.

Resolution: verify the glue_endpoint id before attempting to delete.

Cause: invalid glue endpoint id.

4.2.104 Error Message: Glue endpoint must be in ready state to delete it.

Issue: trying to delete a glue endpoint while it is not in a ready state.

Resolution: try to delete the glue endpoint while it is not in a ready state.

Cause: invalid operation.

4.2.105 Error Message: Notebook {}, must be deleted before deleting endpoint”

Issue: attempting to delete an endpoint while notebook is still associated with the endpoint.

Resolution: delete attached notebooks before deleting the endpoint.

Cause: Unable to delete endpoint as notebook %s is attached to it.

4.2.106 Error Message: Invalid job type. Possible values are: glue, lambda, stepfunction, ingestion, etl or jdbc-cdc.

Issue: Job type provided is incorrect.

Resolution: provide job type as listed.

Cause: incorrect job type.

4.2.107 Error Message: Invalid schedule type. Possible values are: event|time|none.

Issue: invalid schedule type.

Resolution: there can only be 3 types of schedule types: Event, time or None.

Cause: invalid input.

4.2.108 Error Message: Failed to update schedules list in groups, try again later

Issue: possible system down or system refresh is in progress.

Resolution: try after some time. Contact admin team if the issue persists.

Cause: possible system error.

4.2.109 Error Message: User doesn’t have enough permissions to view a schedule

Issue: attempting view schedules without proper permissions.

Resolution: contact admin team for proper access.

Cause: unauthorised operation. Access denied.

4.2.110 Error Message: User doesn’t have enough permissions to delete a schedule

Issue: user is attempting to delete a schedule while having no access to delete.

Resolution: contact admin for required permission.

Cause: unauthorised operation. Access denied.

4.2.111 Error Message: User doesn’t have enough permissions to enable a schedule

Issue: user is attempting to delete a schedule while having no access to enable.

Resolution: contact admin for required permission.

Cause: unauthorised operation. Access denied.

4.2.112 Error Message: User doesn’t have enough permissions to disable a schedule

Issue: user is attempting to delete a schedule while having no access to disable.

Resolution: contact admin for required permission.

Cause: unauthorised operation. Access denied.

4.2.113 Error Message: User doesn’t have enough permissions to list scheduled executions

Issue: user is attempting to delete a schedule while having no access to list schedule execution.

Resolution: contact admin for required permission.

Cause: unauthorised operation. Access denied.

4.2.114 Error Message: NIL

Issue: attempting to sort out supported types.

Resolution: sort with ‘EndTime’.

Cause: unsupported sorting method.

4.2.115 Error Message: Failed to update the DMS dynamoDB table, admin must cleanup this inconsistency.

Issue: possible system error.

Resolution: try after some time. Please contact admin/support team if the error persists.

Cause: possible system error.

4.2.116 Error Message: Could not create the user. Please try again later.

Issue: possible system error.

Resolution: please try again after some time. Contact admin/support team if the error persists.

Cause: possible system error.

4.2.117 Error Message: Could not retrieve users details list

Issue: possible system error.

Resolution: try again after some time. Contact admin team if the issue persists.

Cause: possible system error.

4.2.118 Error Message: user does not exist in the system

Issue: Provide Dashboard access failed as evoker user does not exist in the system.

Resolution: request for proper access from the admin.

Cause: unauthorised operation.

4.2.119 Error Message: Not authorized to see dashboard authorized users

Issue: no proper access to view the authorised users of the dashboard.

Resolution: request access from the admin.

Cause: unauthorised operation.

4.2.120 Error Message: Dashboard doesn’t exist

Issue: no dashboard exists with the given name or no dashboards are available for the user.

Resolution: you can only view the dashboard after creation. Other scenario being no access, contact admin for proper access.

Cause: either no dashboard exists for the user or user has no proper access to view the dashboard.

4.2.121 Error Message: Could not retrieve authorized users

Issue: possible system error.

Resolution: please try again after some time. Contact admin if the error persists.

Cause: possible system error.

4.2.122 Error Message: Not authorized to see dataset authorized users

Issue: the user does not have proper access to see dataset authorised users.

Resolution: contact admin team for access.

Cause: unauthorised operation. access denied.

4.2.123 Error Message: Dataset doesn’t exist

Issue: dataset looking for does not exist.

Resolution: verify and provide correct dataset.

Cause: dataset does not exist.

4.2.124 Error Message: User cannot modify users/user-privileges in default groups

Issue: user is trying to modify default access which is default and not possible to change.

Resolution: contact admin for additional information.

Cause: invalid operation.

4.2.125 Error Message: Could not complete the request. Please try again

Issue: possible backend error.

Resolution: please try again after some time., contact admin/support team if the error persists.

Cause: backend/system error.

4.2.126 Error Message: Failed to create role, Invalid role permissions

Issue: attempting to create a role without having proper access.

Resolution: contact admin for the proper access.

Cause: invalid access.

4.2.127 Error Message: Invalid request body, missing keys

Issue: input body does not have required keys.

Resolution: verify the input given.

Cause: missing input keys.

4.2.128 Error Message: User is not authorized to view the role detail

Issue: unauthorised operation.

Resolution: contact admin team for the proper access.

Cause: access denied due to improper access.

4.2.129 Error Message: Invalid username format, A username can contain alphanumeric and special chars only (Underscore, Hyphen and Period)

Issue: provided username is not in prescribed format.

Resolution: Follow the instructions while creating username.

Cause: username provided is non-compliant with the standard.

4.2.130 Error Message: Invalid password format, A password can contain alphanumeric and special characters only

Issue: password provide is not in standard format.

Resolution: please follow the instructions.

Cause: non-compliant with the standard.

4.2.131 Error Message: In mailAgent.check_body_values, Port - %s does not comply to standards. Port can only contain digits and between 0-65535

Issue: port entered is out of range.

Resolution: please enter the port number in between the displayed.

Cause: out of range port numbers.

4.2.132 Error Message: Invalid account email format, it can contain alphanumeric and special characters only

Issue: invalid account email format.

Resolution: provide correct mail id which is in complaint with the instruction.

Cause: provided mail id is not in complaint with the standard.

4.2.133 Error Message: Failed to perform the health check on resources, try again later.

Issue: possible system error.

Resolution: try after some time. Contact support/admin team if the issue persists.

Cause: possible system error.

4.2.134 Error Message: Unable to connect to ElasticSearch with the given endpoint

Issue: incorrect endpoint.

Resolution: provide correct endpoint. Contact admin/support team if then issue persists.

Cause: incorrect endpoint.

4.3 Forgot Password

4.3.1 Error Message: Error.

Issue: When the user is trying to submit a username or email ID in the forgot password section and the error is received

Resolution: Please make sure that you have entered the username correctly. Please register as a user in the platform if you haven’t done that by now.

Cause: Typically, the error indicates that the username does not match with an existing user in the system.

4.4 Registration Page

4.4.1 Error Message: Registration Error.

Issue: When the user is trying to register using the registration page and the error is received.

Resolution: Please make sure that you entered the username correctly. Please register as a user in the platform if you haven’t done that by now.

Cause: When the username or the email ID is already registered to ADP.

4.4.2 Error Message: Registration Error.

Issue: When the user is trying to register using the registration page and the error is received.

Resolution: Please make sure that you enter an email ID of a valid domain.

Cause: When the email ID is not of a domain that is registered to ADP.

4.4.3 Error Message: User creation failed

Issue: When the user is trying to register using the registration page and the error is received.

Resolution: Please try again after some time.

Cause: When the back-end system encounters an error or an outage.

4.5 Global Errors

4.5.1 Error Message: Session Error.

Issue: When the user is using ADP and the following error is received.

Resolution: Logging in again would fix the issue.

Cause: When the session for a logged in user has ended.

4.5.2 Error Message: Access Denied

Issue: When the user is trying to access a page in ADP and the error is received.

Resolution: Please request the system administrator for access to the particular page or if the user has multiple roles try switching roles to check if his other roles have access

Cause: When the user role doesn’t have permission to access the page.

4.5.3 Error Message: Error loading content…

Issue: When the user is trying to access a page in ADP and the error is received.

Resolution: Please check your network connections and try again after some time.

Cause: When either there is a backend outage or if there is a network issue at the User’s end and the API calls fail.

4.6 Data Set

4.6.1 Error Message: access is already present for the dataset

Issue: Attempting to raise a request while having access for the particular dataset.

Resolution: Since you already have access to the dataset no need to request further.

Cause: The error indicates that the user has access but is trying to request again.

4.6.2 Error Message: Access Request is in Pending state

Resolution: Contact the owner of the particular dataset.

Cause: attempting to raise an access request for the same dataset multiple times.

4.7 Upload Data to a Dataset

4.7.1 Error Message: Invalid File format

Issue: When the user is trying to upload a file to a dataset and the error is received.

Resolution: Please check the filetype that the dataset is configured to accept and upload only files with that extension.

Cause: When the User tries to upload a file of type that is different from the file type that the Dataset accepts.

4.7.2 Error Message: File size exceeded

Issue: When the user is trying to upload a file to a dataset and the error is received.

Resolution: Please check the file size and upload files that has a size less than the mentioned maximum size.

Cause: When the User tries to upload a file that has size more than the mentioned maximum size.

4.7.3 Error Message: Dropzone error

Issue: When the user is trying to upload a file to a dataset and the error is received.

Resolution: Please try again after some time.

Cause: When the system is unable to process the upload request.

4.8 Upload Schema to Dataset

4.8.1 Error Message: Invalid File format

Issue: When the user is trying to upload a schema to a dataset and the error is received.

Resolution: Please check the schema file type that the dataset is configured to accept and upload only files with that extension.

Cause: When the User tries to upload a schema of type that is different from the file type that the Dataset accepts.

4.8.2 Error Message: File too big

Issue: When the user is trying to upload a schema to a dataset and the error is received.

Resolution: Please check the schema file size and upload files that has size less than the mentioned maximum size.

Cause: When the User tries to upload a schema file that has size more than the mentioned maximum size

4.8.3 Error Message: User not authorized to view the dashboard %s details

Issue: User is attempting to fetch the details of the dashboard details without having proper access.

Resolution: Contact administrator for proper access.

Cause: Unauthorised access.

4.9 Connections

4.9.1 Generic Issues

4.9.1.1 Error Message: Missing role information in event header

Issue: User tries to perform an operation related to a connection through other means than UI, like CLI or Postman etc.

Resolution: Add the role_id with appropriate role and try running the API request again.

Cause: The role_id parameter is missing from the body of the API request made.

4.9.1.2 Error Message: User action is not permitted

Issue: User tries to perform an operation related to connections functionality.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to perform an operation on this connection is neither the creator of it nor was mentioned as an authorized user

4.9.1.3 Error Message: Unsupported connection type {user_entered_entry}

Case-1

Issue: When the user tries to create a connection from the UI

Resolution: Create a bug ticket to the ADP team

Cause: The connection type in the response is faulty

Case-2

Issue: When the user tries to create a connection through other means than UI, like CLI or Postman etc.

Resolution: Add an appropriate connection type, currently supported through UI, in the API request made.

Cause: The connection type in the API request made has an unsupported/empty entry.

4.9.1.4 Error Message: All users in the given list are Un-authorised Users - {user_entered_entry}

Case-1

Issue: When the user tries to create a connection from the UI.

Resolution: Remove the invalid username(s) and proceed.

Cause: The selected user might have been removed from the system during the time of connection creation.

Case-2

Issue: When the user tries to create a connection through other means than UI, like CLI or Postman etc.

Resolution: Remove any invalid username(s) from the API request made.

Cause: The username(s) listed in the API request might not exist in the system.

4.9.1.5 Error Message: A connection with name {user_entered_entry} exists, please choose different name

Issue: When the user tries to create a connection from the UI.

Resolution: Choose a unique connection name other than the one entered.

Cause: The user entered connection name already exists.

4.9.2 JDBC Connection Creation

4.9.2.1 Error Message: Invalid JDBC URL

Issue: User tries to create a JDBC connection.

Resolution: should re-check if the JDBC url is entered and in proper format.

Cause: Either the JDBC url is not at all entered or is entered in improper format.

4.9.2.2 Error Message: Must pass Username, Password, and ssl in Connection Details for API connection type

Issue: User tries to create a JDBC connection.

Resolution: Should re-check if the username, password and ssl details are filled in.

Cause: The username, password and ssl details are mandatory fields for establishing an JDBC connection.

4.9.2.3 Error Message: Unable to create glue connection with error {dynamic_error_message}

Issue: User tries to create a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Unsuccessful creation of the Glue job might be due to various reasons.

4.9.2.4 Error Message: A connection with name {connection_name} exists, please choose different name

Issue: User tries to create a JDBC connection.

Resolution: Choose a unique connection name other than the one entered.

Cause: The user entered connection name already exists.

4.9.2.5 Error Message: Unsupported source ‘{source_type}’, only [mysql,aurora,oracle] are supported for now

Case-1

Issue: User tries to create a JDBC connection through UI.

Resolution: Choose the options that are supported by the ADP platform.

Cause: User tries to choose a different source_type than the ones currently supported i.e. mysql, aurora or oracle

Case-2

Issue: User tries to create a JDBC connection through other means than UI, like CLI or Postman etc.

Resolution: Re-check your API call to include only supported source_type(s).

Cause: The source_type in the API request made doesn’t exist or is not currently supported.

4.9.2.6 Error Message: creating

Issue: User tries to create a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Creation of the source endpoint has failed due to unknown reason

4.9.2.7 Error Message: Test connection lambda failed with error - {error_msg}

Issue: User tries to create a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Creation of test connection lambda failed due to the aforementioned error message

4.9.2.8 Error Message: Create connection failed, user {user_name} credentials are invalid, please verify credentials

Issue: User tries to create a JDBC connection.

Resolution: resubmit the username, password provided in the connection details.

Cause: The JDBC connection test was not successful due to wrong credentials entered

4.9.2.9 Error Message: unable to store secret key, please try again later.

Issue: User tries to create a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: There is a problem storing the Access & Secret Keys in the SSM store

4.9.2.10 Error Message: Failed to update the dynamoDB even after creating the connection object, admin must cleanup this inconsistency.

Issue: User tries to create a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the connection details, causing the resources created to be unaccounted for

4.9.2.11 Error Message: Invalid connection id - {connection_id}

Case-1

Issue: User tries to create a JDBC connection or tries to test the connection of an existing JDBC connection from the UI

Resolution: Refresh the page to check if the connection exists. If it does and the problem still persists, create a bug ticket to the ADP team

Cause: The JDBC connection might have been deleted prior to or during the process of testing the connection

Case-2

Issue: User tries to create a JDBC connection or tries to test the connection of an existing JDBC connection through other means than UI, like CLI or Postman etc.

Resolution: Provide a valid connection id in the API request being made.

Cause: The JDBC connection id passed in the API request made might be invalid.

Case-3

Issue: User tries to run a JDBC connection task.

Resolution: Refresh the page to check if the connection exists. If it does and the problem still persists, create a bug ticket to the ADP team.

Cause: The JDBC connection might have been deleted prior to running the task but was not reflected on the webpage.

Case-4

Issue: User tries to list the tasks under a JDBC connection.

Resolution: Refresh the page to check if the connection exists. If it does and the problem still persists, create a bug ticket to the ADP team.

Cause: The JDBC connection might have been deleted prior to or during the process of listing the tasks.

Case-5

Issue: When the user tries to register datasets in a bulk load JBDC connection from the UI.

Resolution: Refresh the page to check if the connection exists. If it does and the problem still persists, create a bug ticket to the ADP team.

Cause: The JDBC connection might have been deleted prior to or during the process of listing the tasks.

Case-6

Issue: User tries to start/stop/pause the tasks under a JDBC Bulk Load connection.

Resolution: Refresh the page to check if the connection exists. If it does and the problem still persists, create a bug ticket to the ADP team.

Cause: The JDBC connection might have been deleted prior to or during the process of listing the tasks

4.9.2.12 Error Message: Unsupported source ‘{source_type}’, only [mysql,aurora,oracle] are supported for now

Case-1

Issue: User tries to update a JDBC connection through UI.

Resolution: Choose the options that are supported by the ADP platform.

Cause: User tries to choose a different source_type than the ones currently supported i.e. mysql, aurora or oracle

Case-2

Issue: User tries to update a JDBC connection through other means than UI, like CLI or Postman etc.

Resolution: Re-check your API call to include only supported source_type(s).

Cause: The source_type in the API request made doesn’t exist or is not currently supported

4.9.2.13 Error Message: updating.

Issue: User tries to update a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Modification of the source endpoint has failed due to unknown reason.

4.9.2.14 Error Message: unable to update secret key in ssm, please try again later.

Issue: User tries to update a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: There is a problem updating the Access & Secret Keys in the SSM store.

4.9.2.15 Error Message: Failed to update the dynamoDB even after updating the connection object, admin must cleanup this inconsistency.

Issue: User tries to update a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the connection details, causing the resources created to be unaccounted for.

4.9.2.16 Error Message: Updating connection failed with new credentials of {user_name}, please verify

Issue: User tries to update a JDBC connection.

Resolution: Re-check the new credentials provided in the connection and try again.

Cause: The JDBC connection test was not successful due to wrong credentials entered.

4.9.2.17 Error Message: User {user_name} is not authorized to update connection details

Issue: User tries to update a JDBC connection.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to modify the connection details is neither the creator of it nor was mentioned as an authorized user.

4.9.2.18 Error Message: User {user_name} is not authorized to delete connection details

Issue: User tries to delete a JDBC connection.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to delete the connection details is neither the creator of it nor was mentioned as an authorized user.

4.9.2.19 Error Message: Extract source schema’s & tables lambda failed with error - {error_msg}

Issue: User tries to run a JDBC connection task to load data from source.

Resolution: Re-run the task and if the issue still persists, create a bug ticket to the ADP team.

Cause: The aforementioned error message occurs when there is an issue while scouting the data from the source.

4.9.2.20 Error Message: User {user_name} is not authorized to get source list

Issue: User tries to run a JDBC connection task to load data from source.

Resolution: Contact the admin to request access to this connection and try again.

Cause: The user that’s trying to perform this operation is not a creator nor is in the authorized users list for that connection.

4.9.2.21 Error Message: User {user_name} is not authorized to get list of tasks for a connection

Issue: User tries to list the tasks under a JDBC connection.

Resolution: Contact the admin to request access to this connection and try again.

Cause: The user that’s trying to perform this operation is not a creator nor is in the authorized users list for that connection.

4.9.2.22 Error Message: Hello user, dataset names {0} are already taken. Please choose different name for them before submitting again

Issue: When the user tries to register datasets in a bulk load JBDC connection from the UI.

Resolution: Consider unique dataset name and try again.

Cause: The dataset name user is after is already in use.

4.9.2.23 Error Message: Missing mandatory param TargetLocation in the input body

Issue: When the user tries to run a JBDC bulk load task from the UI.

Resolution: Target location is a mandatory parameter, please add it and try again. Currently S3 or auroramysql are supported.

Cause: The mandatory parameter TargetLocation is missing in the body of API request made.

4.9.2.24 Error Message: Not all mandatory params are set for scheduling the job, please verify

Issue: When the user tries to schedule a JBDC bulk load task from the UI.

Resolution: Re-check the form and fill out all the mandatory parameters and try again.

Cause: All the mandatory parameters are not set.

4.9.2.25 Error Message: CDC start time {start_time} should be in format ‘YYYY-MM-DDTHH:mm:ss’

Issue: When the user tries to create a JDBC bulk load task from the UI.

Resolution: Correct the CDC timestamp to match “YYYY-MM-DDTHH:mm:ss”.

Cause: The CDC timestamp format is not of the format “YYYY-MM-DDTHH:mm:ss”

4.9.2.26 Error Message: Create job schedule lambda failed with error - {error_msg}

Issue: When the user tries to create a JDBC bulk load task from the UI.

Resolution: Create a bug ticket to the ADP team.

Cause: Lambda that creates job schedule failed with the aforementioned error message.

4.9.2.27 Error Message: Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Issue: When the user tries to create a JDBC bulk load task from the UI.

Resolution: Create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the connection details, causing the resources created to be unaccounted for.

4.9.2.28 Error Message: Schedule creation failed with error {error_msg}

Issue: When the user tries to schedule a JDBC bulk load task from the UI.

Resolution: Create a bug ticket to the ADP team.

Cause: Lambda that creates job schedule failed with the aforementioned error message.

4.9.2.29 Error Message: User {user_name} is not authorized to register datasets for the task

Issue: When the user tries to register datasets by running a JDBC bulk load task from the UI.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to register datasets is neither the creator of the connection nor was mentioned as an authorized user to it.

4.9.2.30 Error Message: Invalid task-id - {task_id}

Issue: When the user tries to get the details of a JDBC bulk load task from the UI.

Resolution: Refresh the page to check if the task exists. If it does and the problem still persists, create a bug ticket to the ADP team.

Cause: The task might have been deleted prior to or during the process of listing that task.

4.9.2.31 Error Message: TaskAction param is required from input body

Issue: User tries to perform an operation on a JDBC connection task through other means than UI, like CLI or Postman etc.

Resolution: Add an appropriate TaskAction parameter to the API request body and try again.

Cause: TaskAction parameter is missing from the API request made.

4.9.2.32 Error Message: Task action of {task_action} is not supported for full-load type

Issue: User trying to perform either of Stop, Resume or Restart operations on a JDBC Full load connection task.

Resolution: Refrain from using the above tasks on a full load JDBC connection task.

Cause: stop, resume & restart task options are not supported for the full-load type.

4.9.2.33 Error Message: CDC data sync to S3 failed for task {task_name} with error {error_msg}

Issue: User tries to run a JDBC connection task with SyncToS3 on.

Resolution: Create a bug ticket to ADP team.

Cause: The task failed with the aforementioned error message.

4.9.2.34 Error Message: Task is still in starting state, please wait for some time to stop

Issue: User trying to stop a task from JDBC connection.

Resolution: Wait until the task status shows it’s running and then try stopping it.

Cause: The task has to be in running state for it to be stopped.

4.9.2.35 Error Message: Failed to stop data migration task, please try after some time

Issue: User tries to stop a data migration task.

Resolution: Retry after some time and if the problem still persists, create a bug ticket to the ADP team.

Cause: The task failed due to unknown reason.

4.9.2.36 Error Message: Task is not running, wait for task to start before stopping again

Issue: User trying to stop a task from JDBC connection.

Resolution: The task has not started yet, so no need to stop it.

Cause: Task should be in running state to be eligible for being stopped.

4.9.2.37 Error Message: Task can be resumed only in stopped state

Issue: User trying to resume a task from JDBC connection.

Resolution: Resume operation is not applicable here as the task is not stopped.

Cause: Task should be in stopped state for it to be eligible for resume operation.

4.9.2.38 Error Message: Failed to resume CDC data migration task, please try after some time

Issue: User trying to resume CDC data migration task.

Resolution: Retry after some time and if the problem still persists, create a bug ticket to the ADP team.

Cause: The task failed due to unknown reason.

4.9.2.39 Error Message: Task is already running

Issue: User tries to start a task.

Resolution: Wait for the existing run to complete before restarting it again.

Cause: A running instance of the same task is already present.

4.9.2.40 Error Message: Task can be restarted only in stopped state

Issue: User tries to restart a task.

Resolution: Wait for the job to finish before attempting to restart.

Cause: The task is not in stopped state for it to be restarted.

4.9.2.41 Error Message: Failed to restart CDC data migration task, please try after some time

Issue: User trying to restart a CDC data migration task.

Resolution: Wait for some time before attempting to restart it again. If the problem still persists, create a bug ticket to the ADP team.

Cause: Task failed to restart due to unknown reason.

4.9.2.42 Error Message: User {user_name} is not authorized to perform any action on task

Issue: User tries to perform an operation on a JDBC connection task.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user trying to perform an operation on the connection task is neither the creator of the connection nor was mentioned as an authorized user.

4.9.2.43 Error Message: Task is in running state, wait for current run to complete

Issue: User tries to run a DMS migration task of a JDBC connection.

Resolution: Wait for the task to finish before attempting to run again.

Cause: Task is already in running state, “start” operation doesn’t apply here.

4.9.2.44 Error Message: Cleanup is in progress

Issue: User tries to run a DMS migration task of a JDBC connection.

Resolution: Wait for the cleanup task to complete before attempting to run again.

Cause: Task is already in cleanup state, cannot run during this time.

4.9.2.45 Error Message: Replication instance creation failed with error - {error_msg}

Issue: User tries to run a DMS migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Task failed due to the aforementioned error message.

4.9.2.46 Error Message: Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Issue: User tries to run a DMS migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the cleanup progress, causing the metadata to become inconsistent.

4.9.2.47 Error Message: Please delete schedule ‘{schedule_name}’ associated with this task before deleting the task

Issue: User attempting to delete JDBC connection task(s).

Resolution: Try removing the associated schedule first before attempting to delete the task.

Cause: The associated schedule for the task is still active causing the task delete operation to fail.

4.9.2.48 Error Message: Failed to cancel data migration task, please try after some time

Issue: User attempting to stop the data migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Attempting to stop during the replication step of a data migration task has encountered an error.

4.9.2.49 Error Message: Unable to get the current status of migration task

Issue: User attempting to stop the data migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Upon successful termination of the data migration task, describing the task status encountered an issue.

4.9.2.50 Error Message: Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Case-1

Issue: User starts a data migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the cleanup progress, causing the metadata to become inconsistent.

Case-2

Issue: User attempting to stop the data migration task of a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the cleanup progress, causing the metadata to become inconsistent.

4.9.2.51 Error Message: Unable to cancel/delete data migration task {task_name}, please try after some time

Issue: User tries to cancel/delete a data migration task of JDBC connection.

Resolution: Wait for some time and retry the operation.

Cause: Several reasons like the task being in starting/running state would cause the cancel/delete operation to fail.

4.9.2.52 Error Message: User {user_name} is not authorized to delete task

Issue: User tries to delete a data migration task of a JDBC connection from the UI.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to delete the data migration task is neither the creator nor was mentioned as an authorized user for that connection.

4.9.2.53 Error Message: Unable to get the current status of migration task

Issue: User tries to view details of a data migration task of a JDBC connection from the UI.

Resolution: Usually this error needs no action from the user if the error occurs during intermediate states of the task. But If the problem arises after the task completes as well, create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the latest status of the task, causing the metadata to become inconsistent.

4.9.2.54 Error Message: Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Issue: User tries to view details of a data migration task of a JDBC connection from the UI.

Resolution: Create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the cleanup progress, causing the metadata to become inconsistent.

4.9.2.55 Error Message: User {user_name} is not authorized to see task details

Issue: User tries to view the details of a data migration task of a JDBC connection from the UI.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to view details of the data migration task is neither the creator nor was mentioned as an authorized user for that connection.

4.9.2.56 Error Message: Mandatory params of InstanceClass/AllocatedStorage are missing from input object

Issue: User tries to update the dms task instance through other means than UI, like CLI or Postman etc.

Resolution: Add the missing mandatory parameters listed in the error message and try again.

Cause: Mandatory params InstanceClass/AllocatedStorage are missing in the body of API request made.

4.9.2.57 Error Message: Replication instance can only be modified for running tasks.

Issue: User tries to update the dms task instance of JDBC connection.

Resolution: Start a DMS task and try modifying the instance.

Cause: The data migration task is not in running state to be able to modify the instance.

4.9.2.58 Error Message: Allocated storage should be more than ‘10%’ of the original

Issue: User tries to update the dms task instance of JDBC connection.

Resolution: Increase the instance storage size to match the criteria and try again.

Cause: The DMS instance storage is supposed to be more than 10% of the data source size.

4.9.2.59 Error Message: Replication instance is currently in modifying state, please wait before submitting changes again

Issue: User tries to update the dms task instance of JDBC connection.

Resolution: Wait for some time to let the old changes to take into effect before attempting to enforce new changes.

Cause: The recently requested changes are yet to be finalized before requesting new changes on the DMS instance.

4.9.2.60 Error Message: Replication instance modification failed with error - {error_msg}

Issue: User tries to update the dms task instance of JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Modification of the replication instance failed due to the aforementioned error message.

4.9.2.61 Error Message: Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Issue: User tries to update the dms task instance of JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the cleanup progress, causing the metadata to become inconsistent.

4.9.2.62 Error Message: Out of range for items per page, Limit is 1000

Case-1

Issue: User tries to list the registered datasets through UI.

Resolution: Create a bug ticket to the ADP team.

Cause: The number of datasets returned are greater than the limit of 1000.

Case-2

Issue: User tries to list the registered datasets through other means than UI, like CLI or Postman etc.

Resolution: Add a limit condition to the API request made to less than 1000.

Cause: The number of datasets returned are greater than the limit of 1000.

4.9.2.63 Error Message: Missing mandatory query param ‘bulkdataload’ for creating a connection

Issue: User tries to create a bulk data load JDBC connection through other means like postman or api etc. than UI.

Resolution: Add the missing parameter and try running the API request again.

Cause: Mandatory parameter ‘bulkdataload’ is missing from the body of API request made.

4.9.2.64 Error Message: Test connection failed

Issue: User tries to test a JDBC connection by fetching the list of schema and tables in the source.

Resolution: Create a bug ticket to the ADP team.

Cause: Failed to fetch the schema and tables from the source due to unknown error.

4.9.2.65 Error Message: Required parameters missing from input for S3 engine BucketName or BucketFolder

Issue: User tries to create a task of JDBC bulk load connection.

Resolution: Fill the BucketName and BucketFolder parameter and try again.

Cause: BucketName or BucketFolder parameter missing.

4.9.2.66 Error Message: Required parameters missing from input for kinesis engine StreamArn

Issue: User tries to create a task of JDBC bulk load connection.

Resolution: Enter the KinesisARN parameter and try again.

Cause: Kinesis Stream ARN not entered.

4.9.2.67 Error Message: Required parameters missing from input for elasticsearch engine EndpointUri

Issue: User tries to create a task of JDBC bulk load connection.

Resolution: Enter the EndpointUri and try again.

Cause: EndpointUri parameter missing.

4.9.2.68 Error Message: Required parameters missing from input for {EngineName} engine DatabaseName

Issue: User tries to create a task of JDBC bulk load connection.

Resolution: Enter the DatabaseName and try again.

Cause: When EngineName is either of mysql/aurora/aurora-postgresql and DatabaseName parameter missing in the connection details.

4.9.2.69 Error Message: Required parameters missing from input for {EngineName} engine OracleService name

Issue: User tries to create a task of JDBC bulk load connection.

Resolution: Enter the OracleService parameter and try again.

Cause: When EngineName is oracle and OracleService parameter not present in the connection details

4.9.2.70 Error Message: Required parameters missing from input for S3 engine BucketName or BucketFolder

Issue: User tries to modify a task of JDBC bulk load connection.

Resolution: Fill the BucketName and BucketFolder parameter and try again.

Cause: BucketName or BucketFolder parameter missing

4.9.2.71 Error Message: Required parameters missing from input for kinesis engine StreamArn

Issue: User tries to modify a task of JDBC bulk load connection.

Resolution: Enter the KinesisARN parameter and try again.

Cause: Kinesis Stream ARN not entered.

4.9.2.72 Error Message: Required parameters missing from input for elasticsearch engine EndpointUri

Issue: User tries to modify a task of JDBC bulk load connection.

Resolution: Enter the EndpointUri and try again.

Cause: EndpointUri parameter missing.

4.9.2.73 Error Message: Required parameters missing from input for {EngineName} engine DatabaseName

Issue: User tries to modify a task of JDBC bulk load connection.

Resolution: Enter the DatabaseName and try again.

Cause: When EngineName is either of mysql/aurora/aurora-postgresql and DatabaseName parameter missing in the connection details.

4.9.2.74 Error Message: Required parameters missing from input for {EngineName} engine OracleService name.

Issue: User tries to modify a task of JDBC bulk load connection.

Resolution: Enter the OracleService parameter and try again.

Cause: When EngineName is oracle and OracleService parameter not present in the connection details.

4.9.2.75 Error Message: Script upload to S3 ETL bucket failed, please verify.

Issue: When user tries to create a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADP team.

Cause: The glue script upload to S3 failed due to unknown reason.

4.9.2.76 Error Message: Unable to create the GLUE job, try again later.

Issue: When user tries to create a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Creation of the connection failed due to unknown reason.

4.9.2.77 Error Message: Unable to update the GLUE job, try again later.

Case-1

Issue: When user tries to update a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Updating the connection failed due to unknown reason.

Case-2

Issue: When user tries to delete a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Deleting the connection failed due to unknown reason.

4.9.2.78 Error Message: Glue script delete from S3 ETL bucket failed, please verify

Issue: When user tries to delete a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Deleting the connection failed due to unknown reason.

4.9.2.79 Error Message: Failed to update the dynamoDB table, admin must cleanup this inconsistency.

Issue: User tries to perform one of the following tasks - register datasets, start a task replication task creation, deleting a DMS connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the task status, causing the metadata to become inconsistent.

4.9.2.80 Error Message: Delete datasets lambda failed with error - {error_msg}

Issue: User fails to create a JDBC connection causing rollback process to trigger.

Resolution: Create a bug ticket to the ADP team.

Cause: Something went wrong with the rollback process while trying to delete the datasets registered during this process with the aforementioned error message.

4.9.2.81 Error Message: Create dataset metadata lambda failed with error - {error_msg} for dataset {dataset_name}

Issue: User tries to create a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the task status, causing the metadata to become inconsistent.

4.9.2.82 Error Message: Extract source dataset schema lambda failed with error - {error_msg} for dataset {dataset_name}

Issue: User tries to create a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Lambda that extracts source dataset schema failed due to aforementioned error.

4.9.2.83 Error Message: Complete dataset registration lambda failed with error - {error_msg} for dataset {dataset_name}

Issue: User tries to create a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Lambda that completes the registration status failed due to aforementioned error.

4.9.2.84 Error Message: Unable to get the current status of migration task

Issue: User tries to delete a JDBC bulk load connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Task failed while trying to fetch table statistics due to unknown error.

4.9.2.85 Error Message: Failed to create glue partition for table {dataset_name}

Issue: User runs a DMS task of JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Actual file load to the DWH is successful, but the Glue partition metadata is not updated due to unknown reason.

4.9.2.86 Error Message: Unable to update metadata of file in file loads table.

Issue: User runs a DMS task of JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Actual file upload was successful but storing the metadata of the file failed due to unknown reason.

4.9.2.87 Error Message: unable to delete secret key, please try again later.

Issue: User tries to delete a JDBC connection.

Resolution: Create a bug ticket to the ADP team.

Cause: There is a problem deleting the Secret Key in the SSM store.

4.9.3 S3 Connection Creation

4.9.3.1 Error Message: Must pass S3Bucket, AccessKey, and SecretKey in ConnectionDetails for S3 connection type.

Issue: User tries to create a S3 connection.

Resolution: Should re-check if the S3Bucket, AccessKey, and SecretKey are filled in.

Cause: The S3Bucket, AccessKey, and SecretKey are mandatory fields for establishing an S3 connection.

4.9.3.2 Error Message: unable to store secret key, please try again later.

Issue: User tries to create a S3 connection.

Resolution: Create a bug ticket to the ADP team.

Cause: There is a problem storing the Access & Secret Keys in the SSM store.

4.9.3.3 Error Message: Unable to create the GLUE job, try again later.

Issue: User tries to create a S3 connection.

Resolution: Create a bug ticket to the ADP team.

Cause: There is a problem creating Glue job for the connection.

4.9.3.4 Error Message: unable to delete secret key, please try again later.

Issue: User tries to create a S3 connection.

Resolution: Create a bug ticket to the ADP team.

Cause: There is a problem deleting the Access & Secret keys from the SSM store.

4.9.3.5 Error Message: Glue script delete from S3 ETL bucket failed, please verify

Issue: User tries to create a S3 connection.

Resolution: Create a bug ticket to the ADP team.

Cause: There is a problem deleting the Glue script from S3 bucket.

4.9.3.6 Error Message: In connections.delete_s3_connection, Unable to delete glue job, please verify.

Issue: User tries to create a S3 connection.

Resolution: Create a bug ticket to the ADP team.

Cause: There is a problem deleting the Glue job created for the connection.

4.9.4 External File System Connection Creation

4.9.4.1 Error Message: Must pass HostOS in ConnectionDetails for ext-fs connection type.

Issue: User tries to create an External File System connection.

Resolution: Should re-check if the Host OS is selected.

Cause: The HostOS is a mandatory field for establishing External File System connection.

4.9.5 External API Connection Creation

4.9.5.1 Error Message: Connection failed, please ensure that URL and query params passed are valid.

Issue: User tries to create an External API connection.

Resolution: Re-check the URL & query params to be in proper format. If issue still persists, raise a support ticket to the ADP team.

Cause: The URL or query params entered are invalid.

4.9.5.2 Error Message: Unable to create the GLUE job, try again later.

Issue: User tries to create an External API connection.

Resolution: Create a bug ticket to the ADP team.

Cause: There is a problem creating Glue job for the connection.

4.9.5.3 Error Message: Failed to update the dynamoDB even after creating the connection object, admin must cleanup this inconsistency.

Issue: User tries to create an External API connection.

Resolution: Create a bug ticket to the ADP team.

Cause: Technical issues with the backend storing the connection details, causing the resources created to be unaccounted for.

4.9.6 Get Connection Details

4.9.6.1 Error Message: Invalid HostOS - {hostname}.

Issue: User tries to view the details of a particular connection from the UI.

Resolution: Create a bug ticket to the ADP team.

Cause: The host os for which the connection was created is invalid or not supported anymore.

4.9.6.2 Error Message: User {user_name} is not authorized to view connection details.

Issue: User tries to view the details of a particular connection from the UI.

Resolution: Request the admin to be added the user as an authorized user to this connection.

Cause: The user requesting to view the connection details is neither the creator of it nor was mentioned as an authorized user.

4.9.7 Update Connections

4.9.7.1 Error Message: Invalid connection id - {}.

Issue: User tries to update an existing connection.

Resolution: Refresh the webpage to see if the connection still exists. If it does, and the problem persists, create a bug ticket to the ADP team.

Cause: The connection which user is trying to update might have been deleted before the update has finished by another authorized user.

4.9.7.2 Error Message: Unable to update glue connection with error {error_msg}

Issue: User tries to update an existing JDBC connection.

Resolution: Refresh the page and try to update the connection again. If the problem still persists, create a bug ticket to the ADP team.

Cause: Updating glue job definition has failed to aforementioned message.

4.9.7.3 Error Message: unable to update secret key, please try again later.

Issue: User tries to update an existing S3 connection.

Resolution: Refresh the page and try again. If the problem still persists, create a bug ticket to the ADP team.

Cause: The update failed as it was not able to update the secret key on SSM store due to unknown reason.

4.9.7.4 Error Message: Failed to update the dynamoDB even after creating the connection object, admin must cleanup this inconsistency.

Issue: User tries to update an existing connection.

Resolution: Bring this to the admin’s attention to cleanup inconsistency.

Cause: The update was successfully completed but the status/metadata of this task was not successfully stored in the backend leaving it in an inconsistent state

4.9.7.5 Error Message: User {user_name} is not authorized to update connection details.

Issue: User tries to update an existing connection.

Resolution: Request admin to grant you access as an authorized user on the connection to continue with this operation.

Cause: The user trying to update the connection is neither the creator nor an authorized user for the connection.

4.9.8 Delete Connections

4.9.8.1 Error Message: Unable to delete glue connection with error {error_msg}.

Issue: User tries to delete an existing JDBC connection.

Resolution: Create a bug ticket to the ADP team with the error_msg.

Cause: There was an issue while deleting the glue job with the aforementioned error message.

4.9.8.2 Error Message: Failed to delete entry in dynamoDB even after deleting the connection object, admin must cleanup this inconsistency.

Issue: User tries to delete an existing connection.

Resolution: Contact the admin so that this inconsistency can be cleaned.

Cause: The connection was successfully deleted but has failed to log it in the backend. This leaves the application with an inconsistent metadata.

4.9.8.3 Error Message: User {user_name} is not authorized to delete connection.

Issue: User tries to delete an existing connection.

Resolution: Request admin to grant you access as an authorized user on the connection to continue with this operation.

Cause: The user trying to delete the connection is neither the creator nor an authorized user for the connection.

4.10 New Jobs

4.10.1 Error Message: Invalid File format.

Issue: When the user is trying to upload a script to a Job on the Job details page and the error is received.

Resolution: Please check the file type and upload files that are of the specified type.

Cause: When the User tries to upload a file of a type different from the accepted types.