1 of 1 people found this helpful
Could you give us more information on how you installed? 32 bit or 64 bit Tableau Server 8.1? Single server or distributed install? Same box? Full uninstall and restore, or "light" uninstall (keeping data intact)?
I installed 64 bit Tableau Server 8.1. It was on a single server and I needed to keep the content, so I did the "light" uninstall.
I contacted support about it and they replied with a link to this upgrade kb article: Upgrading Tableau Server | Tableau Software
I did solve the problem by doing a complete uninstall by removing the ProgramData\Tableau and both the old Program Files (x86) and the new Program Files directories. Then I reinstalled the 64 bit version and restored from the backup I had made just prior to uninstalling 8.0.5.
I don't know if that was absolutely required or if there is some other best practice that would have kept me out of the weeds, but that solved it.
Hi Jonathan, we tested your solution on a different server and it didn't resolve anything. Will this solution only work if following this procedure on the exact same server? I know it's probably hard for you to tell, as you might not have tested this, but perhaps you see a good reason as to why it will only work on the exact same server.
I have no reason at all to think it would any differently restoring to a different server than the one the backup came from. My presumption was that the problem was a hangover from the previous install, so installing somewhere new and restoring should be the same thing as installing on a server that was wiped clean.
I don't know if this will make a difference, but it maybe useful to note that when I installed 8.1 the second time, I completely configured the installation on the server prior to restoring the content. When I restored, I restored content only:
tabadmin restore --no-config [backupfilename.tsbak]
Also, I got a reply yesterday from Tableau Support about it being a known issue that they are working on, so I would strongly encourage you to contact them if you have not already.
Thanks, good to know that it's a known issue. I wasn't able to get that answer from the Tableau Support. We tried exactly the same as you did, and no resolution unfortunately, so I guess we will wait for the version where this bug will be resolved.
We are having this issue as well and, like Jonathan Walder heard from Tableau Support that it was a known issue.
Jonathan, I'm having trouble finding details on what exactly is excluded when using the --no-config argument in a restore. If I do that, will I also need to reset permissions, schedules, and subscriptions?
Based on my experience, it restores all content, users, etc. but no server configurations like how many backgrounders, SMTP configurations etc.
From the Tabadmin Command Reference:
restore Usage: <script> restore <backup_filename>
Restore a backup of Tableau Server's data and configuration.
--password PWD Run-as user password for installation
--no-config Restore the service data, but not the configuration.
--overwrite Overwrite the current deploy directory (default is to rename it)
--no-recover Do not recover the current deploy directory on failure
-h, --help Display <script> help.
-c, --config CONFIG_NAME Use the specified service configuration.
The --no-config option ignores the server installation specific configuration, i.e. distributed workers, number of processes, etc. All of the Tableau entities, permissions, schedules, subscriptions and other things you configure within the Tableau environment are still restored as you would expect.
Not sure that I've seen a very definitive list of what exactly is included/excluded with --no-config either, but the general rule is that if you are restoring to the same server configuration, with no changes, this flag is optional and has no real effect (restore config over the same thing, or don't restore leaving it alone). But if you are restoring to a different server configuration, you need no-config so that it doesn't mess up your new configuration setup with the old configuration.
I am also having the same problem. Does anyone know doing a recover from the last backup will solve this problem?
Is there anyway to kill those hung tasks?
I am waiting for Tech Support to contact me but need to either try restoring the last backup or do a uninstall/install.
Need any advice on whatever workaround is available to get rid of these hung tasks.
II'm having the same issue and it is causing the backgrounder log to fill up until the hard drive is full. I have installed on a new server and restored my backup with no config from tabadmin but I get the same problem.
Looks like Tableau has posted this Knowledge Base Article about this problem.
I was able to fix mine by completely uninstalling and removing all the Tableau Folders under c:\Program Files and c:\ProgramData.
I then reinstalled 8.0.5, because that is what I had, and did a clean tabadmin stop then a Tabadmin cleanup. After the cleanup I did a Tabadmin backup tableau80 which placed the backup in the c:\program files (x86)\tabelau\tableau server\8.0\bin folder. I copied the file out to another location like my desktop and made an offsite copy for safe keeping. I then did another uninstall of 8.0 and removed all the Tableau related folders.
I then installed a fresh copy of 8.1 server 64bit on my server. Once that was running a went back and copied the tableau80.tsbak to c:\program files\tabelau\tableau server\8.1\bin and performed the tabadmin restore tableau80.tsbak. Once the restore was done everything finally checked out and all the Pending tasks were gone.
It looks like if you do not have a backup then you will need to contact Support to have them manually remove the pending tasks.
Moral of the Story is always have a good backup to fall back on.
I went the route of working with support to manually remove the invalid system task, and everything is back to normal. If you don't want to restore from a backup I'd recommend that as an option.
The person I worked with mentioned that they are implementing a code fix for this in the near future (couldn't quote a specific date) that will fix this issue, so another option is to just wait for that if the delay is acceptable.
Matthew, I did the same thing as you have done to roll get rid of the "extract hung" problem, but also found out there was a connect issue with Oracle on 8.1 so had no choice but to roll back to 8.0.
Tableau support is working with me on the Oracle connect issue.