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.
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.
In a distributed environment, when configuring a backup primary, tabadmsvc sometimes did not re-install successfully on workers.
When multiple browser tabs of the same view were open, you could refresh the view in each tab except for the last.
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.
Data sources published to Tableau Server caused the start of week and fiscal year settings 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.
Creating an extract of a published data source caused the start of week to change.
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.
Performing manual security scans of Tableau Server revealed an XSS vulnerability when using IE11.
Running the tabadmin start and restart commands returned an error when the tabadmin user’s permissions did not allow connecting to postgres directly.
Disabled the SSLv3 protocol in Tableau Server to mitigate the POODLE (CVE-2014-3566) vulnerability.
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.”
Integer fields in calculations with Oracle data sources were being unnecessarily rounded and truncated on Tableau Server.
Vizqlserver processes were using large amounts of CPU and causing Tableau Server to become unresponsive.
The REST API Get Users From Site method was returning duplicate values.
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.
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.
In published workbooks, Relative Date filters skipped March 9th 2014. This would happen on any date where Daylight Savings began or ended.
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.
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.