Skip to main content

#Tableau Server76 personnes en discutent

Hello Everyone, 

 

I noticed a new behavior in filter selection after we upgraded to Tableau Server 2026.3.0 and I wanted to check if this was common to other people / if someone had found a fix. I'll try to make myself clear. 

 

When I have a long list of values in a filter - let's imagine countries - and that I select one of them and apply the filter, if I then want to select another, I used to click on "All" then click on it again to clear the filter and then look for the next country I want to filter on. This used to work fine. Now when I do this, the search automatically selects all search results with the previously selected country unticked. 

 

So let's imagine I used to have filter values AA, AB, AC, AD and had filtered on AA, if I search "A" I will see AB, AC, AD selected and AA unselected which is very odd, forcing me to either manually select the desired value or to use the apply button when unselecting all so that the filter "resets". 

 

Did anyone else notice something similar ? I checked on Desktop and the issue doesn't happen, only on Server/Cloud so this looks to be definitely tied to the update.  

 

Could this be patched in the next update ? This is really bothering our users 

 

#Tableau Server

2 réponses
  1. 21 oct., 20:44

    Having this exact same issue (and everyone else in my org). Happening on tableau cloud/website and not the desktop editor. I am pretty sure its tied to this new cloud update as well. Have not found a fix yet but wanted to follow this post in case someone else does.

0/9000

Failure during GSSAPI security context exchange 

 

GSSException: 

Mechanism level: Checksum failed 

 

Caused by: 

KrbException: Checksum failed 

 

Aes256CtsHmacSha1EType.decrypt 

 

#Tableau Server

2 réponses
  1. 21 oct., 15:06

    Hi @David Arnold

     

    you are not sharing much information or context to comment. 

    Anyway, you should first contact your domain admin to look into the Domain controller event logs to get more insights.

0/9000

Creating a new workbook with a datasource with connection to MS SQL using the Tableau server GUI works fine but when clicking the "Data Source" tab the page initially loads ok but then there is a delay followed by "Unexpected Error" 

 

The error message is: 

Session ID: 71705F88A636490B90F1B1EF0D85F7C4-1:1 

Uncaught Error: Minified React error #185; visit

https://reactjs.org/docs/error-decoder.html?invariant=185

for the full message or use the non-minified dev environment for full errors and additional helpful warnings. 

 

The additional information when following the link is: 

Upon opening the above URL, here is the message ---

"Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops." 

 

I have restarted the browser, restarted tableau server, and started from scratch with a new workbook and datasource. 

 

We have many workbooks and datasources connecting to this sql server and they worked fine yesterday. 

 

All datasources to this MS SQL server are affected. 

 

 

 

Tableau Server Version: 2025.3.3 (20253.26.0206.0336) 64-bit Windows 

 

#Tableau Server

5 réponses
  1. 4 sept., 13:10

    This error was caused by login failure on AD by the Tableau service account. 

     

    Another problem that was caused was failure of Tableau to start up and then fail to either start or stop. 

     

    Both were resolved by correcting the account and rebooting the server 

     

    -Arvid

0/9000

Windows server 2022 is in extended support and we need to upgrade to Windows server 2025.  Which Tableau Server version supports it? 

 

#Tableau Server

4 réponses
0/9000

Hi, 

We setup the Tableau Server 2026 with Local authentication, and in the process of hosting the site externally, for security reasons, we need to have MFA for the login process. I don't see an option for MFA. This project is for external customers, who are not in our domain, and will not be added to the domain. 

 

What options do we have for MFA or any additional security options than just username + password. 

 

#Tableau Server  #MFA

3 réponses
  1. 15 oct., 22:52

    Since the server is accessible to external customers, adding MFA is definitely worth considering. It would be helpful to know whether Tableau Server supports MFA with local authentication directly or if an external identity provider is needed. Hope you find a solution that works for your setup.

0/9000
1 réponse
  1. 15 oct., 02:29

    You may want to confirm that you are logged in to Tableau Public. Also, please check the data source you are working with. Not all data sources will work on Tableau Public.You may want to confirm that you are logged in to Tableau Public. Also, please check the data source you are working with. Not all data sources will work on Tableau Public.

     

     

0/9000

Our security team raised one vulnerability in our tableau 2024.2.13 linux server and solution require the java version to be greater than 11.0.32.0.9-1.el8. Can someone please confirm if Tableau server upgrade to version 2025.3.8 will resolve this. 

 

#Tableau Server

6 réponses
  1. 14 oct., 10:29

    Hi @Nitesh Kumar KUSHWAHA

     

    I really doubt. 2025.3.9 has OpenSSL 3.4.1 11 Feb 2025 so you can see how behind Tableau is. And also these CVE are from end of August 2026, so no time for Tableau to test and integrate anyway. 

    But looking at the attack vector, I don't see why you should worry.

0/9000

We are getting very close to maxing out on memory and I need to find a solution for the issue or at least a way to minimize the impact. 

 

#Tableau Server  #Tableau

4 réponses
  1. 13 oct., 21:15

    You could check the session settings and review how long inactive sessions are being retained. Reducing unnecessary session retention may help with memory usage, but it’s worth checking the impact on active users before making changes.

0/9000

Currently RMT is running on a separate server (Windows 2019) and whenever it's restarted the RMT statistics fail to update, sometimes restarting the MQ and RMT services works to get the statistics coming through 

 

#Tableau Server

2 réponses
  1. 13 oct., 21:15

    Hi Emeric, yes you are correct and that's exactly what the Tableau engineer asked me to do, just working through the before restart and after restart output now.... it's a strange one that normally a delayed start on the RMT service at reboot would fix, but alas the search continues. Thanks and much appreciated 

     

0/9000

Technical Challenges When Migrating Tableau Server Assets to Power BI (LODs, Schemas, & Metadata) 

 

For teams currently managing BI modernization projects that involve shifting assets off Tableau Server into Power BI, bridging the architectural gap between the two platforms can create significant technical friction. 

 

When transitioning workbook logic and server models, the three biggest technical hurdles we consistently see are: 

 

  1. LOD Expression Mapping: Converting Tableau’s FIXED, INCLUDE, and EXCLUDE logic into clean, performant DAX measures (CALCULATE, ALLEXCEPT, SUMMARIZE) without altering aggregate results.
  2. Data Model Restructuring: Shifting from Tableau's data blending / wide extracts to structured Power BI Star Schemas and semantic models.
  3. Calculated Field Audit: Auditing .twb/.twbx XML structures to catalog hidden or un-utilized calculations before rebuilding.

Our team has been documenting conversion patterns and automation frameworks to address these logic translation hurdles. 

 

If anyone here is currently planning a Tableau-to-Power BI migration and wants to compare notes on calculation mapping or metadata extraction, feel free to drop a comment below or send me a message! 

 

#Tableau Server

0/9000