Download Now

This version is available from the alternative download site.

Release Date:
October 28, 2014
Desktop Build Number:
Server Build Number:
Tableau Desktop (Back to top)
Issue ID

Extracts that were configured for incremental updates were causing a "Tableau data engine error: 8: The handle is invalid. - PC_NamedPipe : : Send (WriteFile)" error, while a full refresh would complete successfully.


On the Extract Data screen, when you selected Incremental refresh, an "All rows will be added" message was displayed rather than a message telling you how many rows would be added.


When you used the Server > Open Workbook option in Tableau Desktop and selected Find By Project, the project list was empty.


When you join tables that have duplicated column names, Tableau Desktop generates an alternate name for the duplicate. Creating an extract that uses the duplicate column could result in the alternate name being reverted to the original name and made unique by adding a 1 (version and version1, for example). This could cause errors in calculations if the alternate name was referenced.


In a workbook that contains a story, tooltip edits in a worksheet were not reflected in the story point until you refreshed the story point.


When renaming a workbook tab, you could not use the mouse to select some of the existing text.


Connecting to workbook with a connection to a stored procedure on the Mac caused the error: “[Simba][SqlServerODBC](60) Response error: Invalid object name ‘#tmp’.,. Unable to connect to the server ‘’.


In Tableau on the Mac, when publishing a workbook with an NTLM connection to SQL Server, the error “Unable to connect to the ODBC Data Source” occurred.


When using a workbook with a connection to an MSAS cube, if Windows locale settings were changed, some calculated fields showed incorrect results under some conditions.


In Tableau Desktop, joining tables in Excel or text files with an inner join could result in dropped rows and changing the join to a left join would make the missing rows reappear.


Adjusting how totals are calculated (example: selecting a visible field, clicking Total Using > Average) a "Cannot blend the secondary data source because one or more fields use the / function, which cannot be computed locally" error appeared.


When connected to a multidimensional (cube) data source, performance was slow when dragging a hierarchical dimension to the view.


Printing or printing to PDF from a Mac did not properly fit A4-sized dashboards on A4 paper.


When you entered text in a horizontal container on a dashboard and cleared the Fixed width option, saving the workbook did not save the width and the Fixed width option was re-selected when you opened the workbook again.


If you performed an action on a dashboard (select an item for example), then went to another dashboard, you could not clear the action when you returned to the original dashboard.


After using the clipboard from another application, copying data to the clipboard caused Tableau Desktop to unexpectedly close.


When you manually set the start, end and center values of a diverging color palette and some data points were outside the range, data points would show up as black on a view.


Pasting a list that was copied from Excel into a quick filter custom list on the Mac would result in the list getting concatenated as a single string rather than as the original list.


If you selected a page orientation of Landscape when printing a worksheet or dashboard, this setting was ignored and the output was printed in portrait mode.

Tableau Server (Back to top)
Issue ID

Running the tabadmin start and restart commands returned an error when the tabadmin user’s permissions did not allow connecting to postgres directly.


Performing manual security scans of Tableau Server revealed an XSS vulnerability when using IE11.


When a workbook was published to Tableau Server, titles that had "Fit Width" selected did not extend the full width above a scroll bar (if a scroll bar is present). The same titles in Tableau Desktop do extend the full width, including above any scroll bar.


In some cases, putting a field on the Pages shelf caused significantly slower performance when working with the view on Tableau Server than when using it on Tableau Desktop.


Creating an extract of a published data source caused the start of week to change.


When connected to a data extract, setting a dashboard filter action to Exclude All Values, and then creating a context field in a worksheet caused values to be excluded when using the dashboard filter action, regardless of selection.


Data sources published to Tableau Server caused the start of week and fiscal year settings to change.


Multiple Values (custom list) quick filters would generate a "Unknown server error" when they were included in the first selected story point on a published workbook.

Sometimes changes made to a published data source, such as hiding a field or converting a dimension into a measure, are not preserved when a new workbook is created in Tableau Server using the published data source.


When multiple browser tabs of the same view were open, you could refresh the view in each tab except for the last.


In a distributed environment, when configuring a backup primary, tabadmsvc sometimes did not re-install successfully on workers.


In published workbooks, Relative Date filters skipped March 9th 2014. This would happen on any date where Daylight Savings began or ended.


The REST API Get Users From Site method was returning duplicate values.


Downloading a workbook that is connected to a published data source residing on the default site, which was a data source that was originally published to a non-default site, caused the error: “No data source ‘’ found in repository” when the data source was deleted from the non-default site.


When publishing a workbook with an OData connection that had a URL of more than 255 characters, an internal error with response code 500 occurred.


The process status URLs associated with some server processes allowed access to some sensitive environment information, such as worker ID and port number, without requiring admin authentication.


Vizqlserver processes were using large amounts of CPU and causing Tableau Server to become unresponsive.


When a query involved a large number of uniqueKeys, tdeserver64.exe could consume increasing amounts of memory without releasing it, until Tableau Server stopped responding.


Resolved some OpenSSL security vulnerabilities.


Integer fields in calculations with Oracle data sources were being unnecessarily rounded and truncated on Tableau Server.


Clicking the Back button in IE9 and IE10 when accessing views embedded in an AngularJS page caused the page to stop responding and error: “SCRIPT5009: 'ss' is undefined.”


Disabled the SSLv3 protocol in Tableau Server to mitigate the POODLE (CVE-2014-3566) vulnerability.

Tableau Reader (Back to top)
Issue ID

When you tried to open a packaged workbook containing a local cube file, Tableau Reader displayed a "Tableau Reader cannot open files referencing an external data source." message and failed to open the workbook.

Tableau Mobile (Back to top)
Issue ID

When a Tableau Server was enabled for SAML authentication using the Shibboleth IdP, users could not sign in to the server from the Tableau Mobile iPad app.


When signed in to a SAML-enabled Tableau server from the Tableau Mobile iPad app, tapping Sign Out on the Settings page did not sign you out as expected.

In iOS8, exporting an image, data, crosstab or PDF would generate a "Cannot Open View The requested URL was not found on this server." error.

This version is available from the Customer Account Center.