Known issues

From Tableau Desktop, when selecting Tableau Server on the data source page to connect to a published data source, one or more published data sources were missing and/or could not be used.

Tableau Desktop 2019.4.0 does not recognize the following 3 Japanese cities: 1. 丹波篠山市 (Tamba-Sasayama, Hyōgo)- city changed its name from 篠山市 to 丹波篠山市 in May 2019. 2. 標津町 (Shibetsu-chō, Hokkaido) 3. 那珂川市 (Nakagawa, Fukuoka)- city founded on October 2018, from 筑紫郡那珂川町.

When installing or upgrading to a Tableau Desktop or Tableau Prep Builder version released after 1 June 2019 on macOS Catalina, a “‘Tableau Desktop.pkg’ can’t be opened because Apple cannot check it for malicious software.” error occurred. This behaviour is related to the macOS notarisation process.

TabPy secure connections do not work for Tableau Desktop on MacOS. The current method for gathering certificates to perform client side validation in Tableau Desktop requires curl built with OpenSSL while MacOS uses DarwinSSL which does not share the same functionality.

Connecting to some Web Data Connectors from Tableau Desktop 2019.4 resulted in an error "The web data connector returned invalid data. Error Code: 95BE3012"

Workbooks using Oauth connections published with "prompt credentials" sometimes failed to publish with an "Internal Server Error TableauException" error.

Connections to CSV files using a separator other than comma (,) sometimes did not bring in all data.

In Tableau Prep Builder, sometimes bigint data was rounded incorrectly.

When attempting to run a flow that contains many inputs the following error occurs: "Failure evaluating to database: ERROR: collation mismatch, use COLLATE statements to resolve."

When publishing several steps by right clicking "Save Flow As" > "Publish to Server", the publish dialog starts off with the "Saved Steps" tag added to the published flow. However, if the user clicks around in the publish dialog, that tag disappears.

When running a flow of Oracle data that involves a join between two aggregates in Tableau Prep 2019.2.3, it gives the error "Something went wrong and we were unable to process output step: Failure parsing AQL: Oracle database error 972: ORA-00972: identifier is too long..."

Prep Builder page is blank when trying to load flow editor due to a race condition affecting the scripts that need to be loaded.

Unable to cancel a running Prep flow in Tableau Online. Flow stuck "in progress" blocking other flows from running.

Attempting to overwrite a published data source using Tableau Prep Builder sometimes resulted in the following error "loomTableauServerResourceBundle-VizportalPublishDatasourceExceptionMsg"

Subscriptions created between 10/23 and 11/05 may not run on Tableau Online and instead the error "NullPointerException" is received.

When you made a filter selection and then selected multiple marks on the view, sometimes incorrect marks were highlighted.

A giant "X" appears when viewing custom views in Tableau Server on Internet Explorer 11 and Windows 7.

When using Run Now to run an extract, the job creator ID displayed was for the user who created the extract task, not the user who ran the task.

Refreshes scheduled via Tableau Desktop had a creator ID of 0, rather than the ID of the user who scheduled the refresh.

When upgrading Tableau Server on Windows from 2018.1.x and earlier versions (all pre-TSM) to 2019.4 through a non-default location, the installer does not present the 'Upgrade Tableau Server...' option, as it does not recognize the non-default install location, but instead does a clean install.

Restoring Tableau Server required twice the expected amount of available disk space.

Running -tsm maintenance ziplogs sometimes failed with an error during the step "100% - Writing ziplogs archive to disk" and the resulting .zip file was missing files. For more information, see this KB.

Signing into Tableau Server and loading embedded views sometimes failed on Safari 12 after upgrading Tableau Server to 2019.4.2, 2019.3.4, 2019.2.8, 2019.1.12, 2019.3.14, 2018.2.17, 2018.1.20, 10.5.23, or 10.4.24.

When Tableau Bridge client is not running, sometimes no email notifications are sent to the data source owner that the next scheduled refresh is going to fail.

Worksheets containing a Boolean filter from a Snowflake data source change after publishing and show incorrect data.

Sometimes, temp files generated by Tableau Bridge continued to increase over time and were not cleared out as expected.

After changing the site URL of a Tableau Online site, the following error occurred when using Tableau Desktop to open a workbook that connected to a data source published before the site URL change was made: "Item not found (error code 12)"

Tableau Online admin views sometimes took a long time to load, or eventually timed out.

Connecting to Postgres via Tableau Online was successful, but error "syntax error at or near "ta"" was seen in the PostgreSQL logs.

Clicking "Cancel Extract Creation" sometimes failed with "Failed to cancel extract creation job" and extract continued to process.

All Tableau releases have been upgraded to JDK 8 minor version 232 GA.

In MacOS Mojave dark mode, significant UI text is missing in the Data pane, Analytics pane, and Save dialog when exiting.

Embedded views failed to load after updating to Chrome 80. For more information and solutions, see this KB.

Tableau Server users with incorrect Google BigQuery permissions must wait up to 5-7 minutes before being given the opportunity to change credentials due to retry logic.

If there is an increase in settings like nprocs and other process limits on a Linux system running Tableau, then there should be an increase in kernel.pid_max and vm.max_map_count to avoid native thread errors.

Confusing registration file warning message, "Unable to flatten service registration info, because there is no registration file." needs no action from users setting configuration using TSM.

Arbitrary 10k limit for SSL certificate chain file upload causes this error, "External SSL Configuration Error: The file 'intermediate_longer.cert' exceeds the maximum allowed size of '10.240' bytes."

On a live site: extract refresh succeeded, then seemed to fail, but in fact did succeed and recorded new versions of everything in postgres, before deleting the new extracts so workbooks point to nowhere.

DataServer data source with default sort created and published in Tableau Desktop 2018.1, but when this data source is used with Tableau Desktop or Web Editor, then saved to a server that is > 2018.1 the default sort is not respected.

Upgrading from Tableau 2019.1 build number 19.1216.2115 to Tableau 2019.1 build number 19.1217.2115 fails, while restoring repository.

Tableau 2018.3 fails to upgrade with error, "The data directory was initialized by PostgreSQL version 9.5, which is not compatible with this version 9.6.15".

When connecting to CSV files from a Dutch locale version of Tableau Desktop, initially 'comma' is not recognized as a field separator. After selecting any other character and then changing it back to comma, everything works as expected. The issue does not occur when using a different locale, for example English (Ireland).

When connecting to multiple SAP HANA tables, vertical scrollbars were not enabled for Variables or Input Parameters.

Zip code 60686 was mapped in the incorrect location.

The "New Union" button was missing when connecting to DB2.

After upgrading Tableau Server from 9.3 to 2019.2.4 every URL returns a "414 Request-URI Too Long" error.

Filtering a view based on an extract at the quarter level sometimes filtered all data from the view.

When trying to connect to a published data source from Tableau Desktop on an automatic configuration script (PAC) for proxy settings, no data sources appeared in the Search for Data dialog.

After exporting a workbook to PowerPoint, apostrophes " ' " in the workbook name were encoded as "'".

Redshift extract creation failed without any error message if a query was cancelled by the database.

If more than 13 alerts or errors were present in a flow, only the first 13 displayed and the rest of the pane was blank.

Copy and pasting a union in a flow resulted in the following error "the step is missing one or more input"

When certain departments were selected, the registration window displayed every time Tableau Prep Builder was opened.

On MacOS an error occurs when saving or exporting a packaged flow if wildcard union was used containing names with certain Japanese characters. Saving the same flow on Windows does not show any error.

Tableau Prep 2019.2.3 detects and displays a null value where in previous versions (2019.1.3 & 2019.2.2) the column contained no null values.

Running a flow in Tableau Prep 2019.2.3 outputs a different number of rows than in Tableau Prep 2019.1.4.

Localized "Named Range" string can produce inconsistent results in sheet matching pattern when using a different UI language in Prep Builder.

Getting a Java Heap error in Prep 2019.2.3, where the flow used to run in Prep 2019.2.2, due to inefficient memory. (Flow now requiring x 3.5 more memory.)

Error with "Can't find field" after re-opening a flow with a column renamed and then type changed.

System error "Failure evaluating to database: Abstract query SELECT [field name] is not defined" when connecting to an excel file.

Custom SQL that runs on Tableau Desktop 2019.1.4 fails in Tableau Prep 2019.1.3 and 2019.2.2 with error "function pg_catalog.substring(jsonb, integer, integer) does not exist;".

Tableau Prep CLI scheduling is not connecting to run flow. Reporting error code (%errorlevel%) is showing "0" stating that nothing is wrong, when Tableau Prep is unable to reach Tableau Server to publish flow.

If not selecting all input nodes for a union, the "Save steps as flow" will fail. Copying some of the inputs to a union and pasting it into the same flow will cause the union step to display an error that can only be resolved by removing the union step and recreating it.

If a flow contains more than 13 alerts/errors in the Alerts pane, only the first 13 error messages display, the rest of the list is blank.

In Italian [it-IT] "Remove Extra Spaces" and "Trim Spaces" have the same translations.

Connecting to Teradata from Tableau Prep Builder failed with the error "Unable to connect to your data because the Initial SQL parameter 'LoginUser' isn't supported"

When publishing a flow from the CLI, permission errors of insufficient privilege throw exceptions instead of showing valid error messages, necessitating technical support involvement to troubleshoot.

After launching a statistical file in Tableau Prep Builder 2019.2.3 this error is received, "Tableau Prep Builder stopped running because an underlying process stopped unexpectedly."

Error saving flow as .tfl after inserting a .tflx into an existing flow. Generic error appears "Can't save the file".

When trying to create a new calculated field containing an iffnull(), Prep Builder throws error "Unknown Field Name..." despite the field being present in the flow.

When passing an invalid filter value from MSAS via URL on Tableau Server, the following error occurs: "Analysis Services database error 0x80004005: Query (16, 52) Parser: The syntax for '' is incorrect."

In a Windows or Linux 3-node environment upgrading from 2018.1 fails to apply topology due to "Rebuild search index" step failing.

Single backgrounder process intermittently hits deadlock on shutdown during periodic restart and enters bad state.

Restore job's disk space select fails due to over-estimation of space needed for postgres data and produces unclear "checkDiskSpace failure" report.

Certain worksheets do not display data for certain users on Tableau Server, even though permissions match unaffected users.

Guest User not appearing under the "Users" tab after enabling at Server and Site levels.

VizQL Server processes on node6 and node7 intermittently become idle with no log activity reported for the affected vizqlserver processes, but TSM status show all vizqlserver processes are UP.

In web authoring, when an Explorer user changes the Filter Type to 'Multiple Values (custom list)' and start adding an item, it causes the following error: "Initial workbook edits for the session were recovered. To open the saved workbook, click File, and then click Revert."

When a user tries to access a view through a URL that contains spaces (%20), the user is not logged in, though SAML Authentication and Guest Access is enabled; nor is the user redirected to a login page.

When published to Tableau Server 2018.3.7, the tooltips are slow to render.

UPN prefix longer than 20 characters imports username with sAMAccountName, not UPN prefix as expected.

Upgrading Tableau Server failed at "71% - Failed to start search server" and "Failed to rebuild Search Index" if Tableau Server was installed in a file path that contained parentheses "()".

When running parallel refreshes of workbooks that contain extracts of published extracts, the error "Transferred a partial file" intermittently occurred.

Some worksheets in non-default sites did not load correctly for guest users when guest access was disabled on the default site.

After upgrading Tableau Server and/or loading a Tableau Server view, errors 400 and 414 occurred. For more information, please refer to this Tableau Knowledge Base article.

Changing filters sometimes resulted in an "Invalid set function" or "No Such column" error when connected to Redshift.

Clicking the ID of a failed job from a non-default site resulted in the error "An error occurred while getting the Job Details for this Job".

SAMLservice failed to start on multi-node installations of Tableau Server 2019.3 and newer versions with site SAML enabled, which prevented users from logging in.

With browser locale set as Indonesian or Hebrew, creating a new workbook or adding a data source failed with the error "The formatters-and-parsers..js file has not been loaded".

When adding a node to a Tableau Server cluster on Windows, the installation of Tableau Server on the new node eventually fails and rolls back and the following error might occur: "Tableau Service Manager (TSM) Error: The server may not have started properly. Part of the installer exited with error code:1. Check the logs: [path]\logs\app-worker-install.log for more information. [OK]"

When disabling or unchecking "Allow Support Access" to a Tableau Online site, the following error is displayed: "Some or all of the settings failed to save. Try again."

Login to Tableau Server on Linux delayed by 20 to 30 seconds when the echo service is unreachable on domain controllers.

Reference line text formatting appears different from Tableau Desktop once published up to Tableau Online.

Subscriptions intermittently fail with error "The view snapshot in this email could not be properly rendered" due to "Datasource not found in repository".

Canceling a background job for a flow failed with a "Failed to cancel background job type[RunFlow]" error.

Canceling a job from the Jobs page successfully stopped the job, but the number under Queue Time (min) continued to increase.

When viewing the published workbook, the view loads for a few seconds and then throws Uncaught TypeError: "Cannot read property 'quickFilter' of null" error, when loading dashboard in Tableau Server 2019.4 and later.

Log file growth was faster than expected, and could lead to running out of disk space. For more information, see this Tableau Knowledge Base article.

Some extract refresh failures did not send email notifications.

Installing Tableau Server sometimes failed with an "access violation exception (0xC0000005)" error.

Canceling the background job for a flow failed with the error "Failed to cancel background job type[RunFlow]"

Connecting to Google Sheets via Web Edit sometimes failed with the following error ""An error occurred when connecting to your data source. The data source might be corrupt or not valid."

Tableau Server sometimes failed to send an email when the data engine's status changed.

Searching the Data Pane in Japanese or Chinese sometimes had unexpected results.

Refreshing a Google BigQuery extract that used custom SQL failed with "The Google BigQuery service was unable to compile the query. Syntax error: Unexpected" if certain characters were present in the name of the custom SQL query.

Unable to connect to Google BigQuery field that is part of a Record. Error "Name 'fieldname' not found inside 'recordname'".

When clicking the "Forgot Password" option from the Tableau Server login page, nothing happened after inputting a username and no e-mail was received.

In the Tableau Server Resource Monitoring tool, icons on the menu bar were close in color to the background and difficult to see.

In the Tableau Content Migration tool, the icon for contacting Support was a similar color to the background and difficult to see.

In the Tableau Resource Monitoring Tool, The CPU usage chart sometimes showed unexpected gaps.

Tableau Resource Monitoring Tool sometimes stopped displaying new data due to high memory usage by a background process.

Tableau Bridge sometimes generated temp files that did not clear and continued to grow, consuming available disk space.

Tableau Bridge sometimes failed to launch when used with third party data preparation tools.

Added the ability to toggle between grid and list views for favorited content.

If you have the Data Management add-on, you will see data quality warnings on Tableau Mobile.

Added server name validation when signing into Tableau Mobile. Entering an invalid server name now results in a “The server name provided is not a valid server URL” message.