Problèmes connus

Lors d'une tentative de rafraîchissement des sources de données publiées, l'erreur suivante se produit par intermittence : « une erreur liée au contenu à distance a été détectée (502) ».

Tableau Bridge n’a pas toujours pu être restauré après une panne de réseau

Lors de l'impression au format PDF à partir de Tableau Desktop, l'erreur suivante peut se produire : « Impossible d'extraire la police intégrée "ProximaNovaLt-0-50". Certains caractères peuvent ne pas s'afficher ou s'imprimer correctement. »

La connexion à certains connecteurs de données web depuis Tableau Desktop 2019.4 entraînait une erreur « Le connecteur de données web renvoyait des données non valides. Code d'erreur : 95BE3012 »

Parfois, les classeurs utilisant les connexions Oauth publiés avec des « informations d'identification rapides » ne parvenaient pas à publier avec une erreur « Erreur de serveur interne Exception Tableau ».

À partir de la version 2020.3, un ensemble placé sur l’étagère de filtre n’affecte plus la liste affichée des valeurs pour tous les autres filtres Quick de la feuille.

Il arrivait que des tentatives d’actualisation dans Tableau Online d’un extrait publié hébergé sur AWS échouent avec une erreur de perte de la connexion au serveur MySQL lors de la requête.

Lors de tentatives de publication d’une source de données SAP HANA dans Tableau Online à l’aide d'une connexion en direct via Tableau Bridge, il arrivait qu’une erreur inattendue se produise, suivie du message « La source de données … a bien été publiée, mais Tableau n’a pas pu se connecter à la source de données publiée. ».

Lors de la publication d’un classeur connecté à plusieurs Google Sheets, l’écran d’authentification des Google Sheets se dédouble plusieurs fois avant la publication du classeur et apparaît comme si chaque Google Sheet devait être authentifié individuellement.

Message intermittent 503 service indisponible s’affiche lorsque de l’accès à un classeur.

Lors de l'exécution d'une requête dans Impala, le message d'erreur « La table ... n'existe pas » peut s'afficher lorsque vous rafraîchissez la vue ou définissez des filtres.

Parfois, l’actualisation des extraits échouait et l’erreur suivante apparaissait: « une erreur inconnue liée à contenu à distance a été détectée ».

Lors de la publication ou de l’accès à une vue Tableau Online utilisant la variable TableauServerUser, l’erreur suivante s’est produite : « Impossible d’évaluer le filtre utilisateur » ou « Impossible de se connecter au serveur ».

Parfois, les fichiers temporaires générés par Tableau Bridge ont continué d’augmenter au fil du temps et n’ont pas été effacés comme prévu.

Tableau Online admin views a parfois pris beaucoup de temps à charger, ou a éventuellement été interrompue.

La connexion à Postgres via Tableau Online a été un succès, mais l'erreur "erreur de syntaxe à ou près de "ta"" a été vu dans les journaux PostgreSQL.

Après avoir activation la fonction Catalogue ou mis à niveau Tableau Server, les flux de préparation existants avec le chemin Fichier > Source de données publiée > Flux > Deuxième source de données publiée n'ont pas affiché la deuxième source de données ou les classeurs associés.

Lorsque l’actualisation d’extrait planifiée d’une source de données Quickbooks Online s’exécute sur Tableau Online, l’erreur suivante se produit par intermittence : « Erreur d’authentification de l’API Intuit : jetons d’authentification invalides. Connectez-vous à nouveau et réessayez. »

Lorsque vous essayez d’actualiser une source de données/un classeur Amazon RedShift ou d’exécuter un abonnement, une erreur se produit : « Erreur d’exécution d’une requête : [SQLState 22PO2] Erreur : syntaxe d’entrée non valide pour l’entier ».

Dans le Tableau Prep Builder, les données de bigint étaient parfois mal arrondies.

Les valeurs des chaines avec des lettres majuscules sont traitées de façon incohérente dans les valeurs hors échantillon.

Dans la nouvelle fonctionnalité pour la version 2020.3.1 appelée Écrire à la base de données, si la base de données ou le schéma ne contiennent pas de tables (ils sont vides), la navigation vers le schéma ou la base de données ne sera pas possible. Le schéma doit contenir au moins une table créée pour être visible pour la sélection.

Depuis la version 2020.3.3, lorsqu'un filtrage enrichi est appliqué à des valeurs discrètes dans le flux des utilisateurs ou dans un nouveau flux créé avec des étapes groupées, l'annotation ne s'affiche pas sur la fiche Profil comme prévu, afin d'indiquer le changement ou d'apporter des modifications. Pour y remédier, il est possible d'utiliser le volet Modifications sur la gauche ou d'utiliser le volet Flux en haut de la fenêtre pour accéder à l'annotation de filtrage enrichi de valeurs discrètes ou au changement effectué.

Un nœud perd sa licence lorsque le service d'octroi de licence est déplacé vers un autre nœud dans un environnement serveur doté de plusieurs nœuds.

It was not possible to edit an axis range of a continuous bin when the range is fixed to set either the fixed start or fixed end to a decimal number.

An error would occur stating, "Invalid SET statement in the triggered action," when an attempt to connect to Teradata with a username that contained an apostrophe was performed.

When a workbook contained a file union, any subsequent workbook open attempts could fail because the column name would not exist in the data source due to a language translation.

The calculated field set in a title of a Viz is displayed as "All" when using a discrete date dimension for a table across or table down calculation.

The Data Quality Warnings would not refresh for a workbook if the data source connection is opened or a workbook with the connection is opened before signed into Tableau Server.

In the Relationship dialog, when a linking field was changed from an integer to a string, the dialog displayed the correct type but the query used the original data type which could result in a "type mismatch" error.

A table calculation could disappear from the view after the data source was published to Tableau Server.

"Error code: 6EA18A9E. Unable to create extract" could occur with text files when selecting a merged mismatched field as a matching field between two logical tables.

Creating an extract from an OData connection could fail after navigating to a worksheet.

CEILING() function could return incorrect results when using a scalar or a constant as the argument.

Échec d’une nouvelle installation lorsque la clé des cœurs activée n’était pas suffisante pour gérer les cœurs de la machine ou de la machine virtuelle.

TSM Web UI did not show Japanese when the browser is set to prefer Japanese over English starting in version 2019.2+.

When using a live embedded SAP HANA data source, any non-owner could not view and edit the workbook using web authoring.

Zero grid lines on a graph would disappear after selecting a dashboard filter action with animations.

When a live data source is published over an encrypted extract and the live data source is then converted to an extract, the error could occur stating that "hyper already exists".

The REST API previously did not allow for "+" to represent a space character in a filter parameter input.

Broken license fulfillments could display in TSM and be counted by Tableau Server if at least one good product key was activated.

When a URL had the "tabs=yes" specified, all tabs in the workbook appear and the active view was duplicated.

When a workbook or data source was published, the "viewer credentials" authentication option was translated incorrectly in Japanese.

In some circumstances, when the SMTP host value was set and saved in the Tableau Resource Monitoring Tool, the user interface would change the value listed to 'undefined'. This did not affect the underlying configuration but was an issue in the UI.

When the Resource Monitoring Tool agent cannot read a Tableau Server log folder due to permissions, the agent would stop processing all log information. Agents will now continue to process information from logs that do not have permissions issues.

When an external service was being leveraged on Tableau Server, the Tableau Resource Monitoring Tool could show "unknown" as the status for the Tableau Server Processes.

Using special UTF-8 characters in the database name would lead to a parsing error on certain operating system configurations.

When using the "#" character in a password and enforcing special characters was enabled with local authentication, an error would display that the password must include at least one special character.

The parameter control date picker would display today's date as "Month YYYY" format which did not match Tableau Desktop.

When an extract is created in the user interface of Tableau Server, the data source filters based on a date would be ignored.

Revision history on a site would be disabled when the Extract Encryption at Rest setting was changed via Tabcmd.

Sur Windows Server 2012 R2 et Tableau Server 2020.3, des performances dégradées de chargement des visualisations peuvent se produire lorsque l’agent New Relic Infrastructure ou d’autres logiciels de surveillance tiers utilisant les compteurs WMI s’exécutent sur le même nœud que Hyper et le Magasin de fichiers.

A new Zookeeper instance would sometimes fail to start when deploying a coordination service if one already existed.

A REST API call that specified a workbook name and contained special characters would fail.

The command "tsm maintenance reindex-search" would sometimes fail and the Tabadmincontroller logs would contain " Read timed out error and ERROR com.tableausoftware.tabadmin.webapp.init.RebuildSearchIndex - Failed to rebuild search index."

Embedded views would sometimes fail loading the second visualization when multiple Sites were configured and there was no Guest user with "An unexpected error occurred on the server. Click the Refresh button in your web browser and try again."

The MIN() function added in the query causes performance degradation since 2020.2.0.

After successful login, an iframe embedded dashboard would fail to load if the URL contained the hash characters, "%23".

With SAP HANA, Tableau Server could issue queries twice, once before the SAP Prompt and then again afterwards.

A dashboard containing a map would sometimes not load after applying a filter from all values to a single value.

When recovering from a node 3 failure in a 3 node cluster, the "ServiceOperationTimeoutException" error was received after running the command "tsm topology deploy-coordination-service -n node1 --ignore-node-status node3". The command failed to redeploy the coordination service.

Group names created with 2 or more spaces in the name were incorrectly displayed on the Groups page.

Previous manual sort orders would not be retained after adding a field by drag and drop to change another order.

Using the MSAS 15.1.x driver, an error would occur when dragging any field into the view, "Error Code A7AE04D2. Unknown error communication with the data source
(COM 0xC1010000)."

Oracle error "ORA-01424: missing or illegal character following the escape character", would sometimes display when dragging a table to the canvas.

"Initial Connection : Hyper : Failed to start a new hyper instance. AssignProcessToJobObject() failed.: Access is denied" would display when creating an extract on Citrix XenApp.

Tableau Desktop installation property DRIVEDIR did not work as expected.

'Getting data from server' pop-up window would sometimes display when trying to edit a Calculated Field.

The "Sort Field" menu bar would sometimes disappear on the data source page after navigating from worksheet to data source page.

Improved the offline and connected view experience in the Mobile App. When a favorited view was selected, the ‘Interactive Preview’ screen was offline irrespective of their app state (connected or not connected).

The Hyper API license on PyPi.org was not displayed.

Hyperd would sometimes fail to start with "'system_error: MountId<3145741>::getPath(): No such device".

An embedded dashboard prompts for login when no active user session exists for users in a Kerberos SSO enabled environment.

Revision history on a site was disabled when "Extract Encryption at Rest " setting was changed via Tabcmd.

When an attempt was made to change a schedule for one or more subscriptions, an error could occur stating, "Subscription with subject '' could not be found. Verify that it still exists and try again.".

Duplicated translations appeared in the Dashboard menu. "Caption" was translated as "Title" in zh-CN.

In Desktop 2019.2.2 and higher a performance issue would occur when connecting to Hadoop Impala on the Macintosh OS.

Some text file based workbooks would cause the VizQL Server to spike and not release the CPU until the process was restarted.

It was not possible to connect to instances at "servicenowservices.com" when using the ServiceNow connector.

With Impala an ISO-8601 cast from a string to a date and time field failed on 2020.2 and higher with the error, "Invalid character value for cast specification".

When the Managing Users option is set to "Only Server Administrators", it is not possible to create a local group as a Site Administrator.

When hovering over a value displayed on a Viz, an error would sometimes occur, "Uncaught TypeError: Cannot read property 'indexOf' of null.

When the Guest user is disabled on the Default Site, the Guest user would not be able to download underlying data on other sites.

On slow networks, an embedded viz using in-frame SAML authentication could end up looping before the login was successful.

Materialized Views job could fail with "Call not allowed".

When connected to a large spatial file that is a published data source, and an attempt to load a geometry field was performed, an error would display, "Error: BinaryTupleReader::NextWireValueAligned:941 Not enough data for header".

Performance degradation would sometimes occur when an extract refresh was performed for Google BigQuery.

A query could take an excessive amount of time on a complex worksheet and not load.

Sometimes Tableau Desktop would quit when signing out of Tableau Online.

Connecting to Google BigQuery would sometimes be slow on the initial load of datasets.

WDC based connectors would not respect proxy configurations from PAC files starting with 2019.4.

A workbook connected to an Impala data source could result in the error "AnalysisException: LEFT OUTER JOIN requires an ON or USING clause" when "none" is selected in a parameter.

When using Denodo 7.0 and higher data sources, queries on the new Denodo date type ‘localdate’ fields would incorrectly return a date & time, when it should have returned a date only.

To refresh extracts for an Oracle JDBC connection to the same database, the user would be prompted for the password to each connection instead of one prompt.

Creating an Oracle extract would sometimes result in the error, "Invalid datetime value Error Code: DD90F63D, Unable to create extract".

If the data source filter was initially set to exclude all values, changing the existing data source filter would not work correctly.

An error would sometimes occur retrieving OData feeds with the message, "Error '20B40A5E'. The table does not exist" .

Salesforce data extract refresh would sometimes fail with the error, "LogicAssert at ExtractDataTask.cpp line X: fk != relationNames.end()".

Creating a Salesforce data extract in Tableau Desktop 2020.2 would sometimes fail with "Extract not created" when the Salesforce object was created from joined tables.

Auto update could have an inconsistency between the user interface and a twb file with the 'lock-update' flag.

Opening a workbook with an extract where the extract was created within a packaged workbook could sometimes fail with the message, "Internal Error - An unexpected error occurred and the operation could not be completed. Error code 6EA18A9E".

After selecting Ask Data, an error would sometimes occur when connected to a large data source, "Encountered the following error and now waiting to retrying indexing: Can't index data due to a system error."

With some versions of Tableau Prep Builder, the registration prompt would occur with every launch of Tableau Prep Builder even when Tableau Desktop registration had already been completed.

The 2020.4.1 installer will show a new option in the "Install customizations" to select the option for the ability to "check for product updates". This option is for future functionality and currently does not work.

After an upgrade to 2020.3, loading a view containing a published extract could fail to load with the error, "Could not find Hyper hosts to connect to. Unable to connect to the Tableau Data Extract server. Check that the server is running and that you have access privileges to the requested database."