Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

How do I troubleshoot QuickSight datasets and namespaces when I get errors or stuck status?

7 minute read
0

When I try to create or manage Amazon QuickSight datasets and namespaces, I experience issues.

Resolution

Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshooting errors for the AWS CLI. Also, make sure that you're using the most recent AWS CLI version.

Troubleshoot namespace stuck in the CREATING state

If your Amazon Quick namespace is stuck in the CREATING state, then you can't create another namespace with the same name. Complete the following steps:

  1. To check the status of the namespace, run the following describe-namespace AWS CLI command:

    aws quicksight describe-namespace \
  --aws-account-id 111122223333 \
  --namespace your-namespace-name

    Note: Replace 111122223333 with your AWS account ID and your-namespace-name with the name of your namespace.

    In the output, if the CreationStatus field shows a RETRYABLE_FAILURE state, then delete the namespace and retry the namespace creation.

    In the output, if the CreationStatus field shows a NON_RETRYABLE_FAILURE state, then contact AWS Support.

  2. To delete the stuck namespace, run the following delete-namespace AWS CLI command:

    aws quicksight delete-namespace \
  --aws-account-id 111122223333 \
  --namespace your-namespace-name

    Note: The preceding command deletes users, groups, and assets described in the namespace and can't be undone. Replace 111122223333 with your account ID and your-namespace-name with the name of your namespace.

  3. To create the namespace, run the following create-namespace AWS CLI command:

    aws quicksight create-namespace \
  --aws-account-id 111122223333 \
  --namespace your-namespace-name \
  --identity-store QUICKSIGHT

    Note: Replace 111122223333 with your account ID and your-namespace-name with the name of your namespace.

Note: The default quota is 100 namespaces per AWS account. To request a quota increase, contact AWS Support.

Resolve dataset creation permission errors

If you try to create a dataset without the correct permissions, then you might get permission errors or an AccessDeniedException.

To resolve, take the following actions:

  • If you use AWS Lake Formation, then grant the QuickSight service role permissions to the databases and tables.
  • If the user that created the data source left the organization, then transfer ownership of the data source to an active user. To transfer ownership, run the following update-data-source-permissions AWS CLI command: 
    aws quicksight update-data-source-permissions \
  --aws-account-id 111122223333 \
  --data-source-id your-data-source-id \
  --grant-permissions Principal=arn:aws:quicksight:aa-example-1:123456789012:user/default/NEW_USER,Actions=quicksight:DescribeDataSource,quicksight:DescribeDataSourcePermissions,quicksight:PassDataSource,quicksight:UpdateDataSource,quicksight:DeleteDataSource,quicksight:UpdateDataSourcePermissions
    Note: Replace 111122223333 with the account ID of the user who left the organization, your-data-source-id with your data source ID, and aa-example-1 with your AWS Region. Replace 123456789012 with the new user's account ID and NEW_USER with your new username.
  • If you have Amazon Athena federated queries, then grant the QuickSight service role the lambda:InvokeFunction permission for the AWS Lambda functions that the Athena connector uses.

Resolve dataset creation errors

InvalidParameterValueException error message

If you use the CreateDataSet API operation with custom SQL, then you might get the following error message:

"InvalidParameterValueException with null columns"

The Columns parameter can't be null for custom SQL sources. To resolve this error, include valid column definitions in the PhysicalTableMap parameter.

If you specify an incomplete DatasetParameters parameter in the CreateDataSet API operation, then you might get an InvalidParameterValueException error message.

To resolve this error, make sure that each parameter has a valid ID, Name, and value Type.

AccessDeniedException error message

If you have console access and use the AWS CLI to create your dataset, then you might get an AccessDeniedException error message.

To resolve this error, grant the AWS Identity and Access Management (IAM) user or role the quicksight:CreateDataSet permission in their IAM policy.

Malformed namespace error message

If you specify an incorrect principal Amazon Resource Name (ARN) when you call CreateDataSet or UpdateDataSetPermissions API operations, then you might get the malformed namespace error message.

To resolve this error, make sure that you use the correct ARN format.

Example ARN:

arn:aws:quicksight:aa-example-1:111122223333:user/your_namespace/USERNAME

Note: Replace aa-example-1 with your Region, 111122223333 with your account ID, your_namespace with the name of your namespace, and USERNAME with your username.

Unsupported column type

If you use the CreateDataSet API operation on an Amazon Simple Storage Service (Amazon S3) file source that isn't in JSON format, then you might get an unsupported data type error for InputColumns.

Amazon S3 file sources that aren't JSON files only support the STRING data type in InputColumns. To resolve this error, set the Type of each InputColumns parameter in the S3Source parameter to STRING.

Resolve data source connectivity issues during dataset creation

If your Athena data sources databases or tables aren't visible, then take the following actions:

If you have virtual private cloud (VPC) connectivity issues with your or Amazon Relational Database Service (Amazon RDS) data sources, then take the following actions:

If you have Amazon Simple Storage Service (Amazon S3) manifest file issues, then take the following actions:

If you have unsupported data type errors, then take the following actions:

  • Use the CAST SQL function to convert unsupported column types to supported types in your Athena view or custom SQL.
  • Use the CAST SQL function to change timestamp with timezone to timestamp.

If you have a secondary data source connector and get the "Unknown host failure" or hostname resolution error messages, then take the following actions:

Resolve dataset visibility and access issues

If your previously created datasets, analyses, or dashboards aren't visible, then check that you granted the user the correct permissions on the dataset. Run the following describe-data-set-permissions AWS CLI command:

 aws quicksight describe-data-set-permissions \
      --aws-account-id 111122223333 \
      --data-set-id your-data-set-id

Note: Replace 111122223333 with your AWS account ID and your-data-set-id with your data set ID.

If another user created the datasets, then request that the dataset owner or a QuickSight administrator share the dataset with your user or group.

If datasets are in restricted folders, then check that you granted your user the appropriate folder permissions. Datasets that are in restricted folders are only visible to users with explicit folder access.

If datasets disappeared after a deployment issue where you deleted and recreated datasets, then visuals linked to the old dataset IDs can't automatically reconnect. To resolve this issue, recreate the visuals, or use the UpdateAnalysis or UpdateDashboard API operations to replace the old dataset reference with the new dataset ARN.

Restrict dataset creation for specific users

To control which users can create datasets, take the following actions:

Related information

Authorizing connections to Athena

Troubleshooting QuickSight

Data source connectivity issues for QuickSight

Namespaces in QuickSight

Topics
Analytics
Tags
Amazon Quick Sight
Language
English
AWS OFFICIALUpdated a month ago
No comments

Relevant content