Forum Discussion

Aneetta's avatar
Aneetta
Data Storage
04-22-2025

Build To Destination Failure

While Trying build to Destination in an elasticube model, I am getting destination viewer error. Is it related to any configuration issues and is it necessary to provide the database and schema parameter while doing Build to destination?

Attaching the screenshot of the generated error

 

 

Data Models

2 Replies

  • DRay's avatar
    DRay
    Admin
    06-10-2025

    Hello Aneetta​,

    I’m following up to see if the solution I offered worked for you.

    If so, please click the 'Accept as Solution' button on the appropriate post. That way other users with the same questions can find the answer. If not, please let us know so that we can continue to help.

    Thank you.

  • DRay's avatar
    DRay
    Admin
    04-22-2025

    Hello Aneetta,

    Thank you for reaching out!

    The error code 3402, which is a "Destination viewer error," indicates that the viewer connection is invalid and not configured correctly. This error can occur due to several reasons:

    1. Invalid IP/Token Access: One possible cause is that the incoming request with a specific IP/Token is not allowed to access the data source, such as Snowflake. This can be due to network policies or incorrect IP whitelisting. The error message suggests contacting the account administrator for more details 1.

    2. Incorrect Role or Authorization: Another cause could be related to the role specified in the connection string. If the role does not exist or is not authorized, it can lead to this error. The suggestion is to check the roles and possibly use a different role like 'PUBLIC' if the specified role is not authorized 2.

    3. Configuration Issues: There might be issues with the configuration files, such as incorrect URLs or SSL certificate mismatches, which can also lead to this error. Ensuring that the correct configuration files are updated and match the expected setup is crucial 2.

    4. Authorization Settings: If the user is part of a group that does not have the necessary permissions in the authorization settings, it can cause this error. Adjusting the permissions in the authz section to include the necessary groups with appropriate permissions can resolve the issue 3.

    To resolve the error, you should verify the viewer connection settings, check network policies, ensure correct roles and permissions, and validate configuration files and SSL certificates.

    If you continue to have problems, I recommend opening a ticket with our support team. They will be able to work with you directly to gather and needed logs and get this resolved with you.