Troubleshooting B2D Configuration
  • 14 Jun 2022
  • 2 Minutes to read
  • Dark
    Light

Troubleshooting B2D Configuration

  • Dark
    Light

Guidelines

Most errors related specifically to the setup or configuration of B2D are identified as such in the opening line(s) of the error message, describing a general area where the issue might be. Subsequent lines in the error message provide the relevant details to address the relevant issue, as with all build errors.

Notes

  • Each issue might be discovered during different phases of the build, but should fail relatively early (approximately during the first minute).
  • Usually only one issue will be presented, and not necessarily in a particular order. For instance, if both the storage authentication and the destination connection string are incorrect, the user will usually randomly see one of those errors, and only when it’s handled, will get the other.
  • Configuration changes will apply immediately (for builds that are yet to start). There is no need for restarts.

Identified General Issues

  • Destination storage error. Verify the build destination storage configurations.
  • Destination storage authentication failed. Make sure the connection credentials are valid, and the user has sufficient permissions.
  • Destination database error. Verify the build destination database configurations.
  • Destination database authentication failed. Make sure the connection credentials are valid, and the user has sufficient permissions.
  • Destination connection failed. Verify the database configurations of the build destination.
  • Destination connection failed: Unauthorized. Verify the roles and privileges of the destination database user.

Build Error Examples

As with any build error, there will not necessarily be specific wording or specific BE references.

  • S3 bucket not configured:
    • Destination storage error. Verify the build destination storage configurations.
    • Error details: BE#366389 Failed to create S3 bucket.
    • No bucket name configured; Cannot create bucket for this cube.
  • S3 region not configured:
    • Destination storage error. Verify the build destination storage configurations.
    • Error details: BE#366389 Failed to create S3 bucket: uploaddataredshift.
    • No region configured; Cannot create bucket for this cube.
  • Bad S3 region name:
    • Destination storage error. Verify the build destination storage configurations.
    • Error details: BE#366389 Failed to create S3 bucket: uploaddataredshift.
    • Sdk client: Unable to execute HTTP request.
    • Unknown host: Uploaddataredshift.s3.us-eas-2.amazonaws.com; Cannot create bucket for this cube.
  • Missing or incorrect access keys or authentication:
    • Destination storage authentication failed. Make sure the connection credentials are valid.
    • Error details: BE#366389 Failed to create S3 bucket: uploaddataredshift.
    • Sdk client: Unable to load AWS credentials from any provider in the chain:
      [...]; Cannot create bucket for this cube.
  • Typo in writer role in Snowflake:
    • Destination database error. Verify the build destination database configurations:
      [...]
    • Snowflake SQL: SQL compilation error:
    • Role 'WRITERR' does not exist or is not authorized.
  • Bad user or password:
    • Destination database authentication failed. Make sure the connection credentials are valid.
    • Error details: Could not connect to destination SnowflakeJDBC.
    • Connector response: Failed to connect to data source - incorrect username or password was specified.
  • Role not granted in Snowflake:
    • Destination connection failed: Unauthorized. Verify the roles and privileges of the destination database user.
    • Error details: Could not connect to destination SnowflakeJDBC.
    • Connector response: Failed to connect to data source - role 'B2D_WRITER' specified in the connect string is not granted to this user.
    • Contact your local system administrator, or attempt to login with another role, e.g. PUBLIC.
  • Warehouse access not granted in Snowflake:
    • Destination database error. Verify the build destination database configurations.
      [...] Connection parameter 'warehouse' is not specified or cannot be used.
    • Database access not granted in Snowflake:
    • Failed to apply schema: [...]
    • Unable to use database '...', make sure access was granted.

Was this article helpful?