KNOWLEDGE BASE

Every time run a flow from the prep command line will add a new refresh tokens to the connected clients if the flow connects to the published datasource.


Published: 07 Feb 2024
Last Modified Date: 13 Feb 2024

Issue

The flow run from the Prep command line fails with the following error:
 

JAVA_HOME is set to : C:\Program Files\Tableau\Tableau Prep Builder 2023.2\scripts\..\Plugins\jre temporarily

The connection file is in V2 format.

Preparing to run the flow : C:\Users\fjin\Documents\test.tfl

Loading the flow.

Creating temp directory at C:\Users\fjin\AppData\Local\Temp\prep-cli-17649066804179423002

Loaded the flow.

Updating credential for connection com.tableau.loom.doc.fileformat.parameters.StringParameter@daa632f8

Adding username to the Tableau server connection.

Adding content url to the Tableau server connection.

Adding password to the Tableau server connection.

Updated the connections with supplied credentials.

Signed in successfully as fjin to site Default ()

Established input connections to remote connection: http://ip-10-108-30-68.us-west-2.compute.internal (Default)

Established input connections with remote data sources.

Server connections detected in input connections.

Checking the flow document for errors.

class ErrorInfo {

  executedNodeErrors: {2a400a79-3bf1-4b20-a0f9-f9e01172209e=[class NodeError {

    class Error {

      class AbstractError {

        additionalInfo: {dbname=OrdersSample-Superstore, error-message=An error occurred while communicating with Tableau Server

        No Tableau Server user found.

        DataServiceFailure

        There was an error with the data source "". Verify that the data source is configured correctly., query-category=Data, projectName=Default, datasourceName=Orders (Sample - Superstore), class=sqlproxy, directory=/dataserver, odbc-native-protocol=yes}

        id: ConnectionErrorExceptionMsg

        message: Can't connect to datasource Orders (Sample - Superstore). An error occurred while communicating with Tableau Server

        No Tableau Server user found.

        DataServiceFailure

        There was an error with the data source "". Verify that the data source is configured correctly.

      }

    }

    nodeId: 2a400a79-3bf1-4b20-a0f9-f9e01172209e

    property: /

  }]}

  generalErrors: []

  nodeErrors: {2a400a79-3bf1-4b20-a0f9-f9e01172209e=[class NodeError {

    class Error {

      class AbstractError {

        additionalInfo: {dbname=OrdersSample-Superstore, error-message=An error occurred while communicating with Tableau Server

        No Tableau Server user found.

        DataServiceFailure

        There was an error with the data source "". Verify that the data source is configured correctly., query-category=Data, projectName=Default, datasourceName=Orders (Sample - Superstore), class=sqlproxy, directory=/dataserver, odbc-native-protocol=yes}

        id: ConnectionErrorExceptionMsg

        message: Can't connect to datasource Orders (Sample - Superstore). An error occurred while communicating with Tableau Server

        No Tableau Server user found.

        DataServiceFailure

        There was an error with the data source "". Verify that the data source is configured correctly.

      }

    }

    nodeId: 2a400a79-3bf1-4b20-a0f9-f9e01172209e

    property: /

  }]}

}

There are errors in the flow. Unable to run the flow.

Check that the credentials .json file includes all required credentials.

Open the flow in Tableau Prep to view error details.

 

Environment

  • Tableau Prep 2023.2 (23.20.23.0613.1550)
  • Tableau Server 2022.1.17 (20221.23.0811.1403)

Resolution

Upgrade to Tableau Prep Builder 2023.2.3 or later.

Cause

Every time you run a flow from Prep command line, a new refresh token is added to the connected clients if the flow connects to the published datasource.
The error occurs when you run the flow repeatedly from the same client exceeding the default max number of 24 tokens.

Additional Information

When the refresh tokens reaches the max count (by default is 24), the following error occurs when running the flow via the command line from the same client. 
 
Did this article resolve the issue?