#Tableau Server80 diskutieren mit

We have been experiencing recurring Tableau Server degradation on our production environment running Tableau Server 2025.3.3.  

We have observed multiple service crashes and the server occasionally enters a degraded state.

• Mainly Vizdata Native service instances have entered an error state
• VizQL Server instances have also experienced crashes, although they recover and come back up
• Windows Event Viewer shows the following application errors:

1. vizdataservice.exe crashed with exception code(access violation) with jemalloc identified as the faulting module.
2. run-vizqlserver.exe crashed with exception code(heap corruption) with ntdll identified as the faulting module

• The crashes have occured at different times, across multiple Tableau processes

We have reviewed some of the service logs and crash files, but we have not yet identified a definitive root cause. We are investigating whether this could be related to Tableau Server build, a shared dependency, memory management, data source activity or any other underlying issue. 

1. Has anyone experienced similar recurring crashes or degraded status on Tableau Server? 

2. Could these errors be related to a product build, a specific workload or a shared dependency? 

Any suggestions or similar experiences would be greatly appreciated. 

Thank you in advance! 

Hi all! 

I am experiencing an issue with my Tableau dashboard scroll position. When I navigate to different tabs on my dashboard, the scroll position will reset to the bottom of the dashboard. It does not matter if I have scrolled to the bottom or not when on the current page.  

I am using Tableau Desktop to build, Tableau Public to publish, and am embedding the dashboard on a private company-wide site. The issue reproduces on Tableau Public and embedded on my private company site. I have published dashboards using these steps before, and have not run into this issue before.

I have managed to rule out the following solutions:

• Dashboard device view (ex: preview, desktop, default)
• Dashboard navigation buttons are at the very top of my page
• Issue reproduces on Tableau Public and embedded on my private company site
• Each dashboard page is around the same dimensions
  • I have not experienced this issue with the scroll bar with dashboard pages of different dimensions previously, so I strongly believe this is not the issue
• To test, I uploaded a dashboard that I built on Tableau Desktop, published to Tableau Public to publish, and embedded on a private company-wide site without this issue
  • My result was that I experienced the same issue with the scroll bar when this was not previously present :(

Does anyone have any advice for this issue? Thank you!  

Hello Tableau Community, 

I'm looking for advice on a Hive migration that touches a large number of published workbooks on Tableau Server. I've tested several approaches and found a limitation I'd like to confirm or get around. 

ENVIRONMENT 

- Tableau Server 2025.1.11 on Linux (Oracle Enterprise Linux 8.10) migrating to AWS EC2 Linux 

- Data source type: Cloudera Hadoop / Hive (class='hadoophive'), authenticated with Kerberos (Kerberos delegation, embedded credentials in some connections) 

- Content: about 1,500 workbooks and 100+ data sources; many workbooks are extract-based and some extracts are 50-100 GB 

- 10 TB overall data 

GOAL 

The Hive source is moving to a new server in a different Kerberos realm. Every connection needs to point to the new Hive host and use the new Kerberos details: 

- Server / port: old host -> <new-hive-host>:10000 

- Kerberos realm: <OLD_REALM> -> <NEW_REALM> 

- Kerberos host FQDN: <old-hive-host-fqdn> -> <new-hive-host-fqdn> 

- Kerberos service name: Hive -> hive 

I'd like to do this in bulk and, if possible, without downloading and republishing the full-size workbooks, because of the extract sizes and the time that would take. 

Any experience with a similar migration, or pointers to documentation, would be very much appreciated. 

Best Regards, 

Rami Reddy Jaggavarapu, 

Tableau Server administrator. 

I am experiencing an issue where I cannot permanently delete a specific user from our Tableau Server environment. 

Below are the steps I have taken so far: 

1. Attempted to delete the user via the Tableau Server web interface (Users page). 

2. The deletion failed with the following error message, and the user was changed to an "Unlicensed" status: "User '[Username]' could not be deleted because they own content. '[Username]' has been unlicensed."  

3. To resolve this, I navigated through the server and deleted all related content owned by this user (including workbooks, data sources, and any associated trash). 

4. Attempted to delete the user again. 

5. The deletion still fails, and the user remains locked in the "Unlicensed" state. 

Currently, the user appears to own zero content in the UI, but the system still prevents complete deletion. 

Could you please advise on how to completely and permanently remove this user rather than leaving them in an "Unlicensed" state? If there are any hidden dependencies (such as custom views, subscriptions, personal spaces) or TSM maintenance commands required to clean up orphan metadata, please let me know. 

Best regards, 

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