Tableau Server | Salesforce Trailblazer Community

Hi all,

Over the past few months, we've been getting sporadic data server process crashes (requiring a tsm restart to fix). We run a single node with Ubuntu 22.04 with 70GB RAM. Online research seemed to suggest data heavy live connections at the same time could cause it, however all connections have been updated to data extracts - since this, the crashes have reduced but they still occur.

Any ideas on how to stop them? Logs seem to show they can reach like 22GB before they are killed.

Thanks

#Tableau Server

4 respuestas

Etsuro Tabata (CTC TECHNOLOGY Corporation)
Hoy, 13:35
@technical Department

Hi

The Tableau blog says vizqlserver.memory_limit_per_process_gb is an example of SRM memory settings. I think dataserver.memory_limit_per_process_gb works the same way.
https://www.tableau.com/blog/7-tips-adding-scalability-framework-your-tableau-deployment-66391
It can prevent OOM kills, but in your case , SRM may restart the process very often instead.
As
@Emeric LE SAULNIER DE SAINT JOUAN said, 128GB RAM is the minimum recommended for a production environment .
https://help.tableau.com/current/server/en-us/server_hardware_min.htm

Agregar un comentario

Escribir una respuesta...

0/9000

Ayer, 12:01

Need Clarity About Tableau License

Hi Team ,

I am brand new to Tableau , looking for some assistance on license part. I have got Tableau creator license from my team and I am able to login Tableau online/Cloud. Now I am looking for Tableau server setup, So can we use the same license to setup server also?? is my ask.

Thank You

#Tableau Server

1 respuesta

DIEGO FERNANDO MARTINEZ RODRIGUEZ (Modux)
Hoy, 00:47
@Divya Jayachandra

Hi, when you initially buy a creator license, you should be asked if you are going to use Tableau Server or Tableau Cloud. A creator license can only be used for Tableau Server OR Tableau Cloud. It can't be used to activate at the same time Tableau Server and Tableau Cloud.

If you want to activate Tableau Server, you would need to buy another creator license, and therefore make sure to ask the Tableau Account Manager/Tableau-Salesforce partner it is a new install, and you need it for Tableau Server.

Once you have enabled Tableau Cloud or you have installed Tableau Server, you can activate Tableau Desktop and Tableau Prep Builder using LBLM
https://help.tableau.com/current/desktopdeploy/en-us/desktop_deploy_activate_license.htm

On the other hand, if you are looking for the tenant portal in Tableau Cloud (Tableau Cloud Manager), your user needs to be configured as a Cloud Administrator:
https://help.tableau.com/current/online/en-us/cloud_manager_intro.htm

https://help.tableau.com/current/online/en-us/cloud_manager_users.htm#manage-site-membership

If you are a Cloud administrator, once you have signed in into your Tableau Cloud site, you will find a site selector in the upper left corner, just below the tableau, and the option to sign into the Cloud Manager will be enabled.

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you.

Regards,

Diego Martinez
Tableau Visionary and Tableau Ambassador

Agregar un comentario

Escribir una respuesta...

0/9000

Ayer, 05:42

database restore fails during upgrade

i tried to upgrade our tableau server from release 2025.1.18 to 2026.2.1 , it fails on restore of the database...see log below..../opt/tableau/tableau_server/packages/scripts.20262.26.0708.1337/upgrade-tsm --accepteula

Upgrading Tableau Server to version 20262.26.0708.1337. See log file at /var/opt/tableau/tableau_server/logs/app-upgrade.log for progress.

Verifying that the upgrade script is running from the correct environment.

Validating Tableau Server version.

Verifying that the new packages have been installed on all cluster nodes.

Verifying Active Directory connection.

Verifying configuration is valid.

Performing preflight checks to ensure the server is in a good state to be upgraded.

Verifying access to backup file path.

Reconnecting to asynchronous job...

25% - Validating that Tableau Server Administration Controller has access to the backup file.Job id is '505', timeout is 60 minutes.

50% - Installing backup services.

75% - Validating that the Backup Restore Service has access to the backup file.

100% - Uninstalling backup services.

Stopping service...

This operation will stop the server. To start server, run 'tsm start' after the upgrade is completed. Do you want to continue?

(y/n): y

Reconnecting to asynchronous job...

Running - Disabling all services.Job id is '506', timeout is 30 minutes.

50% - Disabling all services.

100% - Waiting for the services to stop.

Verifying Tableau Server is stopped.

Verifying that there is only one deployed Tableau Server Coordination Service ensemble.

Verifying that Tableau Server has been initialized.

Verifying licensing state.

Backing up repository.

Reconnecting to asynchronous job...

Job id is '507', timeout is 1440 minutes.

8% - Starting the Active Repository instance, File Store, and Cluster Controller.

16% - Waiting for the Active Repository, File Store, and Cluster Controller to start.

25% - Installing backup services.

33% - Estimating required disk space.

41% - Gathering disk space information from all nodes.

50% - Analyzing disk space information.

58% - Checking if sufficient disk space is available on all nodes.

66% - Backing up database.

75% - Backing up configuration.

83% - Assembling the tsbak archive.

91% - Stopping the Active Repository if necessary.

100% - Waiting for the Active Repository to stop if necessary.

100% - Uninstalling backup services.

Reconnecting to asynchronous job...

Running - Disabling all services.Job id is '508', timeout is 30 minutes.

50% - Disabling all services.

100% - Waiting for the services to stop.

Making prerequisite configuration changes prior to upgrading TSM services.

Reconnecting to asynchronous job...

Job id is '509', timeout is 38 minutes.

11% - Retrieving the topology to deploy.

22% - Retrieving the configuration to deploy.

33% - Validating the new topology.

44% - Determining if server needs to be started.

55% - Updating nodes to new topology.

66% - Waiting for topology to be applied.

77% - Updating nodes to new configuration.

88% - Reconfiguring services.

100% - Waiting for services to reconfigure.

Upgrading TSM services.

Deploying new service packages.

Updating Tableau Server Coordination Service.

Updating Tableau Server Client File Service.

Adding Activation Service.

Updating configuration.

Reconnecting to asynchronous job...

Job id is '510', timeout is 60 minutes.

Generating new credentials.

Reconnecting to asynchronous job...

Job id is '511', timeout is 63 minutes.

7% - Generating passwords.

15% - Generating secret keys.

23% - Generating apigateway mutual SSL certificates.

30% - Generating Apache Gateway Internal mutual SSL certificates.

38% - Generating Unique Cluster Identifier.

46% - Generating Index And Search Server SSL certificate.

53% - Generating ActiveMQ Server SSL certificate.

61% - Generating internal Metadata API mutual SSL certificates.

69% - Generating key store.

76% - Generating Hyper SSL certificate.

84% - Generating TSIG logs service SSL certificate.

92% - Promoting configuration.

100% - Waiting for services to reconfigure.

Performing post-upgrade services and configuration operation.

Reconnecting to asynchronous job...

Job id is '512', timeout is 30 minutes.

50% - Disabling all services.

100% - Waiting for the services to stop.

Updating asset keys.

Reconnecting to asynchronous job...

Job id is '513', timeout is 2880 minutes.

100% - Migrating asset keys to configuration if needed.

Restoring repository.

Reconnecting to asynchronous job...

Job id is '514', timeout is 2880 minutes.

3% - Checking backup compatibility.

7% - Generating manifest.

11% - Disabling all services.

14% - Waiting for the services to stop.

18% - Installing restore services.

22% - Determining required files for individual nodes.

25% - Checking available disk space on all nodes.

29% - Validating that the Backup Restore Service has access to the backup file.

33% - Transferring required files to remote nodes.

40% - Restoring database failed.

44% - Rolling back database.

48% - Deleting temporary backup file.

52% - Cleaning up restore data on all nodes.

56% - Uninstalling restore services.

This job failed due to unexpected error: 'RuntimeException'

Running 'restore begin' failed

Repository restore failed.

This version of the upgrade-tsm script allows you to retry a failed upgrade from the last successful step. Retry the upgrade by rerunning the upgrade-tsm script.

Tableau Server Upgrade encountered an unexpected error.

Help us improve Tableau Server:

The upgrade encountered an unexpected error. To help us improve the product, you can send us select upgrade failure log files. If you choose to do this, it will include the domain and host names of the Tableau Server.

The logs may contain private information that is used only to help developers identify the issue and fix the error.

Sending the select logs does not open a support case. If you require immediate assistance, please open a standard support case.

For more information, see our privacy policy.

Send logs (y/n):

(y/n): n

Not sending error logs to Tableau.

An error occurred during installation.

An error occurred while restoring repository.

null

any suggestions ?

#Tableau Server

1 respuesta

Himanshu Shekhar (AQBEE Innovations Pvt. Ltd.)
11 ago, 21:32
Hi Richard — the "An error occurred while restoring repository. null" line is generic, so the real cause is only in the logs. A few things to check:

1) Get the real error: look in /var/opt/tableau/tableau_server/logs/app-upgrade.log and the controller log at .../data/tabsvc/logs/tabadmincontroller/tabadmincontroller.log. Search for ERROR / restore / pg_restore near where it stopped — that line names the actual cause (the console "null" won't).

2) Most likely causes for 2025.1 -> 2026.2 (both are post-2022, so legacy identity-mode isn't it):
- Disk space: repository restore needs substantially more free space than the backup size, on the data volume and temp. Low disk is the #1 cause of upgrade/restore failures.
- Backup file / Run As permissions: the Run As service account must be able to read and unzip the .tsbak. Validate with: tsm maintenance validate-backup-basefilepath
- Corrupt/incomplete backup: try restoring the pre-upgrade .tsbak manually to confirm it is good.

3) Recovery: don't just re-run — see Tableau's "Unable to Install, Upgrade, or Restart" KB; with your pre-upgrade .tsbak + old binaries you can roll back and retry after fixing the cause.

If you post the exact ERROR line from those logs, folks can pinpoint the fix.

Refs:
https://help.tableau.com/current/server/en-us/trouble_install_upgrade.htm

https://help.tableau.com/current/server/en-us/db_restore.htm

https://kb.tableau.com/articles/issue/unable-to-install-upgrade-or-restart-tableau-server

Agregar un comentario

Escribir una respuesta...

0/9000

10 ago, 14:29

Hey 🛑 Tableau #datafam#datafam and Salesforce #Tableau_next#Tableau_next

users -

Want to level-up your mapping game or not certain which chat type to use with your data? Help is on the way at our September 2nd virtual meeting - you just need to save a spot at

https://lnkd.in/gkb5kNXS

and we'll see you there --

All are welcome

#Tableau Cloud #Tableau Server #Tableau Public

Hey 🛑 Tableau and Salesforce users - Want to level-up your mapping game or not certain which chat type to use with your data?

Agregar un comentario

Escribir un comentario...

0/9000

6 ago, 14:32

Tableau Multi-Select Filter Search

Hi,

I'd like to raise a client feedback regarding Tableau's native multi-select filter behavior where user is expecting like Excel, where you can search for a value and immediately select it without having to deselect "All" first.

Scenario is In a Multi-Select Filter where all values are selected by default, when a user enters a keyword into the search box, for example "Ada", Tableau narrows the list of displayed values but retains the All selection state.

The user must then first deselect All before selecting the desired values.

The client's view is that the search box gives the impression that they are beginning a filtering action, similar to Excel. As a result, users expect to be able to search for a value and immediately select it.

We have given the client several options based on the current capability of tableau:

Wildcard filter
Single value dropdown
Multi-value custom list

All of which the client has said does not resolve his original concern.

I understand this appears to be Tableau's intended behavior rather than a defect, I'm unable to find any official Tableau documentation that explains the rationale behind it.

If anyone could share/advise any documented explanation or product guidance on:

Why the search box only narrows the displayed values rather than updating the selection itself
The design rationale behind requiring users to deselect All before selecting a subset of values

Thanks

#Tableau Desktop & Web Authoring #Tableau Server #Reports & Dashboards

3 respuestas

Don Wise (Tableau Community Ambassador)
6 ago, 17:19
I understand, so you could create an underlying text box that essentially says 'Start by filtering in the filter selection pane to the right' and/or have a distinct starting value that is always selected as a starting point.

We don't know what you're actually working with, but those would be some options to consider. If you have the link to the idea, could you post it in this thread so that others can upvote it?

If this response answered your question, please mark it as an Accepted Answer?
This way, others searching for similar solutions will find the answer faster in the future.

Best, Don Wise (Tableau Ambassador)

Agregar un comentario

Escribir una respuesta...

0/9000

13 jul, 02:06

Axis subtitle disappears when filters or RLS are applied.

I am using a dynamic axis title controlled by a parameter (e.g., QTD, YTD) along with a subtitle (e.g., Actual, Prior, Growth). While it displays correctly in the default, unfiltered view, an issue occurs after publishing to Tableau Server version 2026.2.2 (20262.26.0625.1400).

Specifically, the subtitle disappears under two conditions:

When a user applies a filter.

When a user with restricted access (Row-Level Security) views the dashboard.

Under these conditions, only the main axis title is visible, and the subtitle is entirely missing.

Axis subtitle disappears when filters or RLS are applied.

Filters or RLS applied.

Screenshot 2026-07-13 085908.png

I am utilizing the MIN(0) dual-axis workaround. Could this setup be causing the rendering bug?

#Tableau Server

1 respuesta

Ohyori Masanobu (株式会社NTTドコモ)
26 jul, 15:42
Hi Danh,

Good catch mentioning the MIN(0) workaround — that's likely the real cause here, not a Server bug.

Why it happens: With MIN(0), the subtitle is just a text label on a hidden dummy mark, not a true axis property. If a filter or RLS reduces the data for that pane to zero rows (or the underlying calc returns NULL), Tableau simply has nothing to plot — so the label silently disappears. Your main title stays because it's likely a straight parameter reference, not dependent on a mark being drawn.
Common triggers:
The subtitle calc (Actual/Prior/Growth) returns NULL once rows are filtered/RLS-restricted
RLS often behaves like a context filter, which can affect even FIXED LOD calcs
"Growth" especially needs a prior period — if that period gets filtered out, there's nothing to compare
How to confirm:
Reproduce the same filter/RLS condition in Desktop. If the subtitle disappears there too, it confirms it's a data issue, not a Server rendering bug.

Fixes to try:
Wrap the subtitle calc in ZN()/IFNULL() so it always returns a value
Check if your filters/RLS are set as context filters — this can break FIXED LOD assumptions
Make sure the field driving the MIN(0) mark always has at least one row, regardless of filter/RLS state
Alternatively, skip MIN(0) and insert the calculated field directly into the worksheet title — titles aren't tied to marks being drawn, so this failure mode goes away entirely
Try it in Desktop first — that'll tell you which fix is needed.

Agregar un comentario

Escribir una respuesta...

0/9000

5 ago, 18:13

Why is the view not a fixed size on the website, but it is on the server and desktop app?

My Tableau workbook is on a server embedded in our company website. On the website, one of my dashboard tabs shows as Automatic fit to the screen size. The other two dashboard tabs have a fixed desktop size. All three have a fixed size on the desktop file and on the server file. Why is it not a fixed size on the website?

#Tableau Desktop & Web Authoring #Tableau Server #Size Requirements #Trailhead

1 respuesta

DIEGO FERNANDO MARTINEZ RODRIGUEZ (Modux)
5 ago, 21:38
@Kelsie Jacob

I am confused. You said: " On the website, one of my dashboard tabs shows as Automatic fit to the screen size. The other two dashboard tabs have a fixed desktop size."

Then you say:
" All three have a fixed size on the desktop file and on the server file."

Thus my main question is what do you think "automatic fit" involves in the website. If you have your embed code, and explain which part of the code does the "automatic" fit.

Other questions:
a. I don't think it is possible to have automatic fit in website and fixed in server. There is only one fit, the one the workbook in Tableau Server/Tableau cloud is configured.

b. If your workbook has several dashboards, the iframe that the embed code uses will be set up to the maximum of the widths of the dashboards, and to the maximum of the height of the dashboards. This means, that the div/table parent container (the div-table should be big enough to handle the size of the children tableau-viz object)

c. If a dashboard is set to automatic, then in your website you need to create a parent div/table, and set the height and width of the element, so the children element (the tableau-viz component) fills the parent container.

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you.

Regards,

Diego Martinez
Tableau Visionary and Tableau Ambassador

Agregar un comentario

Escribir una respuesta...

0/9000

4 ago, 09:27

Very slow load time for first dashboard in workbook

Has anyone encountered a situation where a specific workbook loads very slowly on Tableau Server, but only on the initial (bootstrap) opening by each user?

Additional details:

First access to any dashboard in the workbook adds an initial time of 20-30 seconds. Any operation after that (filtering, switching dashboard, etc.) is OK, 10-15 seconds in total - which is good enough taking into account the volume and complexity of the data (multi-fact, >100 million records).
I can see in a Performance Recording that this time is spent sending 100+ queries to the metadata, nothing to the actual (published) data sources.
The same happens on Dev, Test and Prod servers (versions 2025.1, 2024.2).
There are 10 dashboards in the workbook. A different workbook with 18 dashboards (for example) loads within 2 seconds.
The uncompressed .twb file is 5Mb, so not too large.
Splitting the workbook into several smaller ones reduces the time, but it's still slow and really hurts the functionality (navigating between dashboards).

Any ideas? I'll open a support case anyway...

Thanks

Dan Chissick

Senior BI Consultant | Tableau Ambassador

#Tableau Server

3 respuestas

DIEGO FERNANDO MARTINEZ RODRIGUEZ (Modux)
4 ago, 13:38
@Dan Chissick

Hi, I am trying to give you my best advice of what might be happenning. I got a similar case in the past that I was able to solve following the advices I just gave to you.

It was a strange case, and metadata related. In the record performance I don't remember if the event was recorded as hundred or more parsing xml events, or simply was not recorded.

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you.

Regards,

Diego Martinez
Tableau Visionary and Tableau Ambassador

Agregar un comentario

Escribir una respuesta...

0/9000

3 ago, 13:32

Files and Folder Anti Virus scanning Exemptions

Does anyone know the which files / folders need exemptions from the Anti Virus scans. Deployments are on the D drive..

#Tableau Server #Security

1 respuesta

DIEGO FERNANDO MARTINEZ RODRIGUEZ (Modux)
3 ago, 15:08
@Patrick Chinery

You may take a look of:
https://help.salesforce.com/s/articleView?id=001466887&type=1

Basically, you need to add the complete folder (e.g.
D:\Tableau)
to the exceptions.

If this post resolves the question, would you be so kind to "Accept this Answer"?. This will help other users find the same answer/resolution and help community keep track of answered questions. Thank you.

Regards,

Diego Martinez
Tableau Visionary and Tableau Ambassador

Agregar un comentario

Escribir una respuesta...

0/9000

23 jun, 10:11

csv datasource with multiple files does not extract

On premise Tableau.

The scheduled extract runs but does not pick upp additional csv files.

I use desktop to point a datasource at a folder with csv files. The datasource is published and extract scheduled.

To update the datasource with new csv files I have to run an extract from desktop.

Should the scheduled extract pick upp new csv files?

#Tableau Server

12 respuestas

Arvid Carlander
3 ago, 13:13
Hi again Emeric,

Thank you for your suggestions earlier. I have now followed them and my system works better but one issue remains.

Current configuration:
1. Runas now uses a domain account "tableausa" with admin rights on the tableau server
2. The csv files are on the tableau server shared with
\\tableausa\folder
syntax. The tableausa account has permissions on the share.
3.
\\tableausa\folder\xxx
has been added to the allowlist

I created a new datasource using tableau desktop based on one of the csv files via the fileshare, and converted to a join with a wildcard with no filtering. This works fine and if I add/remove files this is reflected in desktop workbook and datasource.

I then published the datasource without attached files. When the published datasource is opened via browser the published files are found and can be refreshed.

Then my luck ran out. I created a workbook via browser based on the new datasource. It opens and finds the published files, but I can not get it to update when files change. It can see all the data and files in the datasource as published, but refreshing to show new data does not work - I have tried F5, menu option to refresh the datasource in "sheet 1" and in the Data Source tab, and opening a new browser.

My expectation was that when opened the workbook would retrieve data from the files currently in the folder, and that the workbook user could update using menus or F5 when new files were added, but that does not work.

Do I have the wrong expectations or am I making some mistake? Is it always necessary to edit the datasource when files are added to the wildcard folder?

-Arvid