Updated Log4j files to version 2.17.1
Update: Tableau has identified that this release still contains some Newrelic files running Log4j version 2.17.0.

Deleting a user from Tableau Server would sometimes result in an error reading, "'Key (modified_by_user_id)=(90549) is not present in table "users"'.

The subscribe button would sometimes not be available on a workbook that contained an embedded Google BigQuery ODBC live connection.

The "filter" action in admin view would sometimes not work when the user language was in Japanese or Deutsch.

Snowflake OAuth credentials would sometimes not save properly in Tableau Online after being embedded.

Tabcrashreporter would sometimes crash due to unhandled exceptions in network threading.

When utilizing a 3 node high availability environment, if the initial node was stopped Tableau Server would become unlicensed and the user would be unable to login.

Changing the time filter in a dashboard would sometimes result in the following error, "Uncaught TypeError: Cannot read properties of null (reading 'sliderHandle')"

Combined headers would sometimes be missing a white space separator if the UI language was not English.

When attempting to login to Tableau Server on Internet Explorer 11, it would sometimes result in a blank screen.

Login and navigating in the Tableau Server UI would sometimes be slow when using the Server ATR activation method starting with 2021.1.

When attempting to build a container image using the latest versions of the container setup tool (2021.2.0, 2021.3.0 and 2021.4.0) with input of any Tableau Server install package RPM released in calendar year 2022, it would fail with an unsupported version error.

When connecting to a database (with JDBC) or with OAuth authentication the connection would sometimes time out. The error message may include Error Code DACBE23F

After upgrading to a new version of Tableau Server it would sometimes result in Redis processes failing to start and showing the following error: "Could not create server TCP listening socket *:: listen: Unknown error". Please see this Knowledge Base article for more details.

With the ATR activation method, the activation service could result in excessive logging at the "info" level.