We recently lost our head IT person who did all the backend of Tessiture, and alas, I am slowly starting to learn more and more. Around New Years though, our Analytics started throwing this error. Has anyone seen this before and if so, is there an easy fix? (We do have a ticket in for this as well, but I figured perhaps the Tess Hive Mind might be able to help as well!).
Isn't this the cutest error message?
Try restarting the following services on your Analytics Server and restart your cubes.
Sisense.CLRConnectorsContainer
Sisense.Oxygen
ElastiCubeManagementService
Thanks Emily! We are trying this now
Unfortunately, no luck with the restarts. Same error. Hopefully I will get a response in the ticket soon, and if I do, I will add it here (also open to any ideas others might have!).
Hmm... what's your email? I'll forward you what I have from our ticket - have your contact(s) reference ticket 78283. At some point they had me reinstall our TessituraProcessingService (be mindful of the .ini file!), and two months later, they had me reinstall the Analytics Cuber server... What version of Tessitura are you on? I'm assuming you're self-hosted since you had access to restart the services?
Here are some other things to try:
If you have the ability to make these changes, I was told to setup the Analytics services to restart on the following schedule. We set ours to Automatic (Delayed Start) so they don't try to start before the server is fully operational.
The services which should be set to auto-start are the following:
ElastiCubeManagementServiceSisense.CLRConnectorsContainerSisense.DiscoverySisense.ECMLogsPersistenceServiceSisense.HouseKeeperSisense.JVMConnectorsContainerSisense.OrchestratorSisense.OxygenSisense.PulseSisense.Repository Services that need to be disabled:Sisense.CollectorSisense Shipper
Derrek,
I think you might have the same issue as us. If I log into https://my.sisense.com/account/packages using my Sisense login supplied by Tessitura then I see no subscriptions.
I emailed John Jakovich yesterday and he replied: We recently extended our contract with Sisense and it appears that your Sisense instance is not recognizing the new contract expiration, which is Dec 2022. I haven’t seen this behavior before. I know Chris Wallingford is investigating. I’ll follow-up with him to see if I can help.
Regards,Alex
Interesting! Out of curiousity, are you self-hosted? And is it an offline instance of Analytics?
Thanks Emily! It seems like there might be a bigger underlying issue, but I will keep these things on my back pocket if we are still stuck.
Yes we are self-hosted. Not sure what you mean by an offline instance. I did install Sisense seperately (i.e. offline) but it has been working fine until our license expired on 27th Dec. Alex
Got it, that's what I meant! Looks like we are likely having the same problem. So hopefully there is a full solution soon.
So I think Tessitura have sorted out our Sisense license. I went into SiSense Server console yesterday afternoon and saw a different message. It prompted me to login using my Sisense login provided by Tessitura. It gave me key which I copied and pasted into https://my.sisense.com/account/packages - get license key. This then returned a license code which I pasted back onto my server and restarted it. Now when I log into Analytics I can see I now have a license valid until 01/01/2023. Problem solved. Hopefully you can do the same on your server.
Thanks Alex!! We ended up jumping on a call with Tessitura Support as we were having some issues getting it to work...but overall, the solution your proposed is the core of what we had to do. Thanks again for your help!! Thankfully this won't be a problem for another couple years again ;) haha