Go have a look at task manager and look for a task called tabadmin or tabsvc. Also, have a look at the log (tabadmin.log). It's likely that as part of the uninstall, it's doing a full backup which is a built-in task. You can either wait for this to finish, or you can go kill the task and then do an uninstall again.
My understanding is that 2018.2 doesn't do a backup. You have to do it before that happens. Now I killed the batch job, uninstalled, and I am attempting to re-install again and I am getting the could not connect to TSM Controller error when attempting to follow the upgrade guide. I have checked the windows firewall and it is not blocking that port.
Gotta say, this is by far the worst tableau experience to date. The installation used to be flawless. If I didn't need the LDAP piece I wouldn't be bothering with this.
You may want to run the obliterate script before you try a fresh install but ONLY if you have backup.
C:\Program Files\Tableau\Tableau Server\packages\scripts.<version>\tableau-server-obliterate.cmd
That should wipe any remnants of the previous install.
I'm with you that this upgrade has been my least favorite. So much changed in this version I feel I'm relearning how Tableau Server behaves and the added complexity of install doesn't help.
For me it just sat there for a day and didn't really seem to be doing anything....so ended up aborting it.
As Gerardo said, I'll probably try the obliterate next (which is just about my favourite script on the Linux versions!)
We have the same problem here. Already opened a case for that.
- We had 2018.1.0.
- Tried to Upgrade
- Uninstalled 2018.1.0
- Upgraded 2018.2
- But it failed at 78% on "Ensuring Default Services Reach requested state"
- We tried to get back to 2018.1.0, but it doesnt work. We are stuck in the middle.
- Then we tried a clean fresh install. But after Uninstall and deleting the Folders, 2018.2 still wants to upgrade....
If you have any help, feel free to post it here
3 of 3 people found this helpful
I encountered the same problem. I waited over an hour before giving up. I killed the upgrade script, rebooted the Windows server, and re-ran the upgrade script. The second time the upgrade script ran to completion. My theory was that something had a lock on something the upgrade script needed to modify and that rebooting the server clear the lock.
Thank you, just ran into this myself and rebooting and rerunning the script did the trick!
So far on two different machines Windows Server 2008/2016 (Dev*/Test*) One worked when I reran the script "upgrade-tsm.cmd" and one ended up with a gateway stuck in a perpetual errored state. Both were running the same restored tsbak prior to the upgrade.
I'm currently running the obliterate script to try to get a fresh install on one of the machines... we'll hope for the best.
I'll update when/if the reinstall works otherwise, who else is hoping for 2018.2.1..?
1 of 1 people found this helpful
I also had the issue with gateway not starting and having a red exclamation mark on it. I ended up changing some settings in the configuration tab and applying the changes, I found in the logs that it was saying a configuration file was missing and doing this seemed to do the trick. Specifically I cleared our SSL settings and then had to reapply them when it came back up but all services were able to start.
1 of 1 people found this helpful
Rick Dorsey's response helped me remember all our config was broken. I completely forgot that I had to reconfigure all our SSL certs after this upgrade, things that are generally assumed to be setup already.
When my server launched I was in a similar state but forgot to choose the SSL certs in the config. After reconfiguring... everything it worked. Have you configured all your security, automatic sign ins... etc etc?
Have you tried connecting directly to the machine by the server name?
If we've used SSL in the past, I don't remember configuring it... but our Tableau Server is a single machine that I have more or less set-and-forget since ~2012. I've been the sole admin, so if that's the case, there's no one to blame but me.
The server is up and running, and VizAlerts had been sending emails... but after a server reboot, VizAlerts crapped out, saying it can't connect to the server.
To answer your questions:
I haven't configured anything outside Tableau. Short answer, I don't know how to.
I can connect to the server machine via Remote Desktop. From that machine, I can't connect to localhost, or the server name.
I opened a case with Tableau and will update here.
SSL Generally means you would be connecting with HTTPS instead of HTTP.
If you can't connect to anything via localhost thats very odd, since you're basically telling the machine to connect to itself, which even with non-working security works. (It may warn you and say "This connection is unsecure" or something to that effect if you were to be missing SSL configuration.)
You might be able to test certain pieces using the RESTAPI when the server is up, for example signing in or something. At the end of the day though the people on support will be your best bet since we're all only so familiar with the new version.
Best of luck Evan!
I went back today and uninstalled 2018.1, rebooted, and attempted the install again. It fails again, but this time with Could not load an existing application.properties of agent when it is tried from the setup window running the script automatically. When I attempt to do the script manually I get ERROR: Tableau Server environment variables not set. You must run this script from an existing Tableau Server node.
I tried running the refresh environment variables script, but that doesn't fix anything either.
tableau-server-obliterate.cmd -y -y -y -l results in yet another errorThis script must be run as Administrator. Cancelling. The command prompt is admin mode.
I have to say you really screwed this all up tableau; this is, bar-none, the absolute worst end user experience I have ever had. If we weren't so embedded in tableau I would be telling my org we are switching to Amazon quicksight.
Additionally, this is preventing about 50 desktop users from being able to update to 2018.2 desktop edition for using the new features. Sure they could downgrade the workbook on publish, but then you lose the features so it is pretty pointless to update.