2 Replies Latest reply on Apr 27, 2017 3:29 PM by Chris Crombie

    Complete uninstall of Tableau server

    Chris Crombie

      I'm trying to do a clean install on my backup primary because upgrading it stomps all over the worker nodes for some reason.  I've uninstalled the software from Control panel and deleted the directories in Program Files and Program Data as indicated in this article:


      Uninstalling Tableau Server | Tableau Software


      But when I go to do a clean install of the software it still shows the upgrade dialog.  What am I missing?





      I'm hesitant to proceed from here because of the grief this is causing my production environment and the considerable time I spent having to re-install my primary node after the backup primary upgrade hosed my existing installation on the other nodes.  I don't believe the article for upgrading distributed environments is quite accurate.


      Upgrade a Multi-Node (Distributed) Tableau Server


      If you follow these steps, I think it configures your worker nodes a second time, but I'm not sure since the actual process is not displayed during installation.



        • 1. Re: Complete uninstall of Tableau server
          Mark McGhee

          Wondering if it might be worth trying a restart of the computer since sometimes an uninstall isn't really complete until then.   Also, have different versions of Tableau Server been installed on there before?  


          After the restart I would check the directories once again just to be sure there wasn't something left over.  Though not 100% sure if we're looking for regkeys during install to see if we think Tableau Server is still installed.

          • 2. Re: Complete uninstall of Tableau server
            Chris Crombie

            Thanks for the reply Mark.  Yes, I did try that but no such luck.  I've deleted all traces of Tableau directories I could find.  Do I need to delete the postgres database separately? 


            I'll probably just shut down the workers altogether when I'm able to have our VM admins start them back up again (I don't have that access) so that the backup primary can't push anything out to them again.


            My goal is to do a clean single node install on the backup primary and then save that tabsvc.yml file separately for future upgrades.  We wrote an automatic failover script (because c'mon...manual failover is no failover at all IMO) and we do regular failover tests which replaces that tabsvc.yml file with the one from the primary.  Hopefully that will force the backup primary to leave the worker nodes out of it's upgrade since they were already done with the primary. 


            My hunch is that the upgrade article was written with the assumption that the backup primary is still configured as a single node because in theory it has never had a failover.  In any case, the upgrade process didn't work for me as advertised.  Just wanted to let folks know and see if anyone had any hints to share.