Télécharger dès maintenant
This version is available from the Customer Account Center.

Cette version contient un correctif de sécurité crucial pour Tableau Desktop, Tableau Server et Tableau Reader, qui permet de réduire l'exposition aux attaques HDM (homme du milieu) ou par déni de service. Pour contrer ces attaques, nous avons mis à niveau la bibliothèque OpenSSL utilisée par les produits Tableau concernés.

Date de publication:
12 Juin, 2014
Numéro de version Tableau Desktop:
Numéro de version Tableau Server:
Tableau Desktop (Back to top)
Issue ID

When connecting to Excel, the following error would sometimes occur: "The parameter is incorrect," followed by additional data. The problem would typically occur when a 32-bit version of Tableau Desktop was attempting to use a 64-bit driver to connect to a Microsoft Excel file.


When using SSL offloading with a non-default port, clicking a thumbnail for a workbook located on the server without being logged into the server would result in the following error message: "Couldn't connect to server" instead of the sign-in prompt.


Amazon Redshift connections could fail with a "an error occurred validating the custom SQL connection" message. This could be caused by several circumstances, including "date" data types and inefficient metadata queries.


Graphics Device Interface (GDI) leaks would occur, causing Tableau to stop responding. The problem was observed when creating user filters or editing sets.


For Hadoop connection types, added support for user name and password authentication. SSL is available for connections to HiveServer2.


Replacing references for a field would cause a filter associated with selected worksheets to revert to just the current worksheet.


It was not possible to publish to a Tableau Server project that contained a special character, such as a plus sign (+), in its name.


When using blended data, dropping a dimension from the primary data source and a date dimension from the secondary data source into the view, setting the date dimension to discrete and exact date, and then adding it to the Filters shelf as a relative date filter would cause a "No such column" error.


A sort option for the Total column was not showing in Tableau Desktop even when it was showing as expected for the same Total column in Tableau Server.


Amazon Redshift workbooks were not allowing subscriptions if the SSL-required option was not selected. This impacted version 8.1.6 and earlier workbooks.


Manually repositioning labels for U.S. states, would cause some marks to snap into place in locations other than either their starting position or where you attempted to move them.


When connecting to a Salesforce data source, Tableau Desktop would drop the connection and then revert to the Connect to Data dialog box without returning an error.

Tableau Server (Back to top)
Issue ID

The version of PostgreSQL used by Tableau Server was upgraded to 9.3.4. This upgrade resolves a PostgreSQL issue that, for some customers, resulted in increased database size and decreased performance. This problem resulted in many repetitions of "WARNING: pgstat wait timeout" in the PostgreSQL log files. Customers that worked around this issue using” tabadmin set pgsql.use_vacuum_job=true” need to reset this value to the default using "tabadmin set pgsql.use_vacuum_job=false". Tableau recommends you do the reset before upgrading, but you can do so immediately after installing the new version if you need to.


For the Guest User account, text for download links, share links, tooltips, and other UI text, would be displayed in the incorrect language. This problem was caused by User Preferences being incorrectly saved for the Guest User account.


In a distributed environment (1 primary node, 2 worker nodes), the standby data engine and repository would be intermittently unavailable. The problem would occur during refreshes of large extracts (> 1 GB).


The PostgreSQL ODBC driver used by Tableau Server was upgraded to version 09.03.0300.


Refreshing an extract would generate a "could not determine a constructor for the tag !binary" error message. The problem would only occur when manually selecting a schedule and clicking "Run Now" and when the workbook name contained double-byte characters.


When a workbook view containing a map was published to Tableau Server, the map legend range indicator text would sometimes be cut off after a filter selection was made.


When restoring a backup after an upgrade, the tabadmin restore command could fail due to a backup error that was not noted in warning or error messages. This was due to the backup.sql file not being added to the .tsbak file during the Backup step, so it could not be restored to the server.


Using ODBC drivers to connect to an Oracle Business Intelligence Enterprise Edition (OBIEE) data source published with "Prompt User for Credentials," would return the following error: "An unexpected error occurred on the server. If you continue to receive this error please contact your Tableau Server Administrator."


Some errors (for example, an error generated by a missing data source) could restrict access to the Data Sources page for administrators. Non-administrative users could navigate to the page, but an administrator would get an "internal error" message.

non-humans click here