This page has an error. You might just need to refresh it.
Unable to find an action for 851;a: {"id":"851;a","state":"SUCCESS","returnValue":{"isChatterEnabled":true,"contextUser":{"id":"0054T000001NHMqQAO","userType":"Guest","photo":{"smallPhotoUrl":"https://community.tableau.com/img/userprofile/default_profile_45_v2.png"},"displayName":"Tableau Community Forums Site Guest User"},"showAnnouncement":false},"error":[]}
Failing descriptor: {forceCommunity:tabset}
Tableau server version 2024.2.5 details and performance!!!
Hi Community Team,
I want to know the working of the server version 2024.2.5 latest patch release like stable performance and not having any issues in filter selection and resource utilization issue faced in earlier releases.
we are now in 2024.2.3 and facing many issues like disk space increase, subscription issues, and some other.
If anyone went to this version, let us know the working so that we will get into it... but don't want to face the issues like previously.
Tableau Server 2019.1 Connector for AWS Athena Installation Help
I'm trying to connect Tableeau Server 2019.1 on AWS Linux 2 to AWS Athena.
I've searched for a good bit on to find installation instructions and have put together that the JAR file needs to be in the /opt/tableau/tableau_driver/jdbc directory.
I'm not sure if Open JDK 8 works or not so I switched to Oracale JAVA 8 64-bit just in case.
I have the server working on an automated install from CloudFormation complete with copying the Athena JAR file AthenaJDBC42_2.0.7.jar to the .../jdbc directory.
I restarted Tableau Server and even after all that if I create a new project and goto connections I can't seem to get the Athena connector to show up.
Does anyone have suggestions or a link to where there are instructions on how to do all these steps to get Tableau Server 2019 to connect with AWS Athena?
An error occurred on the server generating the backup. This job failed due to unexpected error: 'BackupRestoreWarning' BackupRestoreWarning(message:java.lang.RuntimeException: net.jodah.failsafe.FailsafeException: org.apache.thrift.TApplicationException: Internal error processing completeStartDatabase)
If they reboot the server then the backup starts working again for 2-3 days before failing again.
We have an existing case with Tableau Technical Support, however if the community has any more ideas or has any notes about the checks we've run through so far we'd be happy to hear them!
Here's everything we've run through so far.
0) Confirmed that the required accounts have the correct permissions on the Server and the backup location.
Before backing up Tableau Server, verify that permissions are configured correctly for the following scenarios:
Tableau Server installed on non-default drive: If you have installed Tableau Server on a non-default drive or folder, then you will need to manually configure permissions for the Network Service account. You may also need to configure additional permissions for the Run As service account. See Installing in a non-default location.
When backing up Tableau Server on Windows to a network drive, the Machine account must have write access to the network share where the backup files are written (this is not normally the case and you are responsible for configuring this if you want to back the server up to a network share).
Sometimes it appears like there aren't any disk space issues.
However, this can be a hidden problem as Tableau quickly cleans up the temporary files so it looks like disk space usage never gets very high. Their backup is about 15GB and they don't appear to have any disk space issues.
The -k skips a database integrity check. Using this parameter allows the backup to succeed however it isn't a long term solution and it's not clear why a reboot fixes things for a couple of days.
Whilst why this works isn't well documented, it has been recorded that sometimes changing the backup location resolves this even if you then return the backup location to its original path afterwards.
After checking the previous points, could you try changing the Path and execute backup again.
Set the new location using:
tsm configuration set -k basefilepath.backuprestore -v "<drive>:\new\directory\path"
After you change a default file location you need to do the following:
Apply pending changes:
tsm pending-changes apply
Stop Tableau Server:
tsm stop
Restart the TSM Controller:
net stop tabadmincontroller_0
net start tabadmincontroller_0
Wait several minutes for the controller to restart. You can confirm the controller has restarted with this command:
tsm status -v
When you can run that command and the Tableau Server Administration Controller is listed as 'running' the controller has restarted.
Start Tableau Server:
tsm start
This was reported to us as not resolving the issue.
I'm afraid that the last I heard was that they were still restarting the Tableau Server regularly as a workaround.
However, the last advice from Tableau Support was to change permissions of Network Service account to full control on <INSTALL DRIVE>:\Program Files\Tableau\Tableau Server which the customer was waiting on change approval to enact, but no update was provided after this.
The connection to sapbw had a fatal error and was disconnected. ExternalProtocol::PipeMessageSource::ReadBytes: Communication with the Tableau Protocol Server
When we are trying to connect to BW getting below error in desktop and server. It was working till yesterday in both desktop and server. Please let me know your thoughts on this issue.
An error occurred while communicating with the data source
The connection to the data source might have been lost.
Error Code: 38348CCE
The connection to sapbw had a fatal error and was disconnected.
ExternalProtocol::PipeMessageSource::ReadBytes: Communication with the Tableau Protocol Server process was lost. Tableau Protocol Server process might be terminated, possibly due to system resource constraints or another external source
Nightly Backup file size increasing after upgrade to 2024.2.3
Sonce upgrading to 2024.2.3 we have noticed the file size of our nightly backups in increasing each night even with running maintenance cleanup while the server is running.
How can i diagnose what the problem is, and how to fix it as this increase is not sustainable
How do I find out the last usage for all Login Based Licenses?
Goal
I used up all my creator/Login Based seats so trying to see who have not used it or not used it in awhile so I can give that seat to someone else
Tried
I tried the "Login-based License Usage" admin view's "Which creator seats have not been used in the last __days?" but either the view is wrong or not right in a useful practical way
There is actually no LBLM state (like inactive, active ...) , stored. It is a calculated field depending on transactional activity timestamps.
You can enable the readonly access and audit the table yourself so server_user_name and date_last_used column primarly. But information is not very reliable as it is at the site level and also depends on signals being sent by Tableau Desktop (LBLM reporting events) when Tableau Desktop is started with a valid sign-in token (not sure if there is a scheduler as well).
You might want to create your own governance audit by querying table http_requests activity for http_user_agent Tableau Desktop as well as historical_events table for publish action type.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.