I experienced this myself last week. I needed to run some updates on our server, so of course a reboot was needed. I noticed the issue when trying to connect to our Tableau page, and had to go back to re-enter the server key and everything.
have you opened a support case?
Is this a virtual machine and has it migrated hosts?
I upgraded our QA Server from 9.0.4 to 9.1.1 and now my server is down due to some licensing issue. Spent yesterday with Tableau support and a Tableau developer and the issue hasn't been resolved yet
Toby -- Please keep us updated on the solution. I'm really curious about this issue.
I have faced this issue in past. It had issue the Tableau server activation. once we activated the server, everything was working properly.
Is it possible you to share below mentioned logs ?
Thanks a lot
Atul Vitthal Yadav.
This is possible, I need to check with our IT group. I was told a couple weeks ago that they were planning to migrate hosts, and in theory I should have been told about it.
My situation was remedied yesterday and it was my fault. Our IT pushed some server OS patches and one of the WMI files was corrupted. They fixed the file, rebooted the server, and everything went back to normal. The good thing about this is that:
- It was the Tableau install process that found this issue -- which makes me a bit disappointed with my IT team that I had to be the one to catch it but after 2.5 years of patches this is the first issue I've had so that's not too big of a deal
- Tableau Support is great! Thanks to Matteo (Ireland), Ethan (Seattle), and Jason (developer) for diving in and working diligently to figure things out.
John, case #01712593 if you're curious.
I'm not sure how your IT were moving hosts but if they used VM snapshots then it will break Tableau Server's licensing technology. I just mentioned this to another post:
FlexNet licensing service that is employed by Tableau links itself to the physical hardware of the machine on which Tableau Server license key is activated. It is therefore impossible to take a snapshot of a server containing an activated copy of Tableau Server and move it to a different VM location. Such an action will break FlexNet's licensing trust, and the Server instance will fail its next licensing check.
You can contact Tech Support for help on how to restore your server properly Submit a case to our support team | Tableau Software
I have a follow up question on your response. If a VM image hotswaps over to a different host due to restricted resources on the initial host, will this also break the FlexNet licensing?
If hotswapping breaks Flexnet's licensing trust, does it apply to all servers, or are servers running only gateway and search exempt from this?
I am really interested in how they fix the problem in the FLEXnet case.
I had restarted my tableau server 9.0 installed on a VM. After that, I have the license problem: sometimes when I log into server with "admin", it says: tableau server not licensed!
I went to system application logs and found some confusing logs about FLEXnet that I put in attachments.
ERROR requestId=Vk2F6wrl9DIAAE4oBJMAAAJs: wgsessionId=- com.tableausoftware.api.webclient.remoting.
RemoteCallHandler - Exception raised by call target: FlexNet Library could not be initialized, error code 21.
FLEXnet Licensing Service is not started.
Could you please tell me how I can go rid of this situation? Re-activate tableau server?
Thanks a lot!
A customer of me had the same issue.
After running his normal Windows updates the license was not found by Flexnet.
He upgraded from 9.0 to 9.1 but no succes. He had to re-license his TS.
Further on he noticed that 60 seconds after applying the newest VMtools, Tableau cluster controller messages appeared in the windows eventlog. I will check with him which Hypervisor platform he is using.
Hope this helps.
Edited: friday, 22:26
I called him today. He is using VMware. And he said some licensing dll got corrupted. Sounds like the error message CHEN reported.
@toby, i can't look into the case#. So please, post which patch was bad and how you were able to fix it. TIA.
Did you execute the restart using Tabadmin from the primary machine? You must execute all Tabadmin commands from the primary machine. Also, make sure you run the command prompt as an administrator. Let me know if that resolves the issue.
One more thing: Double-check your "Run as" account permissions. Read this article and check everything mentioned in the subheadings, too. http://onlinehelp.tableau.com/current/server/en-us/help.htm#runas.htm