Tableau Server 2019.2.2

When loading workbooks connected to MSAS using Kerberos delegation, an intermittent "Analysis Services database error 0x80004005" error occurred.

Images in subscription emails received using Gmail were received as an attachment rather than in the email body.

Prior to signing into some web data connectors, an error would appear in the sign-in window:"The URL points to a website, not a web data connector – a web page with code to get data from a website"

Sometimes connecting to SAP HANA took longer than expected after upgrading to 2019.1.

An internal server error would occur when publishing a workbook to Tableau Server 2019.1 or higher installed on Windows with Norwegian Bokmål locale.

When you ran a menu action to filter a target sheet, selecting a mark in a non-target sheet would clear the original action selection, resulting in the target sheet becoming blank.

In Tableau Server 2018.2 or higher, some dashboards did not show data upon initial load, requiring one or more manual refreshes of the view in order for it to appear.

Workbooks could not be downloaded when capitalisation of folders in the specified Tableau Server installation path did not match the capitalisation of the actual file path on disk.

When you used the quick sort button in a column header to sort a crosstab view, no indicator was given to the user that Tableau Server acknowledged the sort request.

An unexpected server error would occur when loading a view using a trusted ticket after the VizQL session had already expired. The view would then appear to attempt to reload but never complete.

"Warming up external query cache on data change" tasks had frequent and excessive failures in the Background tasks for non-extracts admin view.

Reported core licences in use was inaccurate for systems with more than 64 logical processors or configured with multiple processor groups.

Calculated fields in published data sources that used user functions could not be edited via web edit and comments on those fields were not visible.

When Tableau Server was installed in a non-default location on Windows, the Obliterate script did not remove tableauservicesmanagerca.jks.

TSM allowed HTTP TRACE requests.

Custom default number formatting for calculated fields containing user functions would revert to the original default format after publishing the data source.

When connecting to Sybase ASE and updating the connection details, the following error would occur: "An error occurred while communicating with SAP Sybase ASE."

If the user account used to install Tableau Server was removed from the machine or domain, configuration changes would fail and Tableau Server could become degraded.

After a failed backup, partial copies of backup files created were left over and not deleted in the Tableau Server data directory under the relative path of data\tabsvc\tabadminagent\0\filetransfer.

After publishing a workbook that contained a parameter on Tableau Server, the drop-down menu of the parameter would inherit the colour of the object behind it, creating a mismatch in the design between Desktop and Server.

On Tableau Server, pressing the ESC key would reset a single value drop-down filter to display "(All)" values even though the filter was customised to not "Show all values".

On computers with Skylake X CPUs or other CPUs with the AVX512 instruction set, sometimes loading views caused Hyper processes to restart unexpectedly, or other server stability issues.

Subscription emails had a different return_path email address that did not match with the "From" e-mail address.