KNOWLEDGE BASE

Re-indexing Search Server Did Not Resolve Issues with Viewing Projects, Workbooks, and/or Views


Published: 16 Mar 2020
Last Modified Date: 24 Mar 2020

Issue

Projects, Workbooks, and/or Views are not visible in the Tableau Server UI, even after running a tsm maintenance reindex-search command

After attempting to reindex the search log lines similar to the below may appear:

Tabadmincontroller Logs

INFO com.tableausoftware.tabadmin.webapp.asyncjobs.JobStepRunner - Progress update for job RebuildSearchIndex, id: 806, step: RunIndexingOnVizportal, status: Running, message key: job.rebuild_search_index.step.run_indexing_on_vizportal, message data: ,
2020-03-12 20:02:42.494 -0500 pool-14-thread-1 : ERROR com.tableausoftware.tabadmin.webapp.init.RebuildSearchIndex - Failed to rebuild search index. Please check whether a valid Tableau Server license is present and check the vizportal logs.

VizPortal Logs
2020-03-12 20:02:42.492 -0500 (,,,,) VizportalMaintenanceServiceThread : ERROR com.tableausoftware.domain.solr.SearchService - Failed to gather solr stats
com.tableausoftware.domain.exceptions.SearchServiceException: Error from server at https://localhost:8191/solr/view: Expected mime type application/octet-stream but got application/json. {
"error":{
"metadata":[
"error-class","org.apache.solr.core.SolrCoreInitializationException",
"root-error-class","org.apache.lucene.index.CorruptIndexException"],
"msg":"SolrCore 'view' is not available due to init failure: Error opening new searcher",
"trace":"org.apache.solr.core.SolrCoreInitializationException: SolrCore 'view' is not available due to init failure: Error opening new searcher\r\n\tat

 

Environment

  • Tableau Server

Resolution

  1. Gather licensing information from the server to verify no issues with licensing. If there are issues, those will need to be dealt with first (https://kb.tableau.com/articles/howto/providing-license-data-to-tableau-support)
  2. If there are no broken fulfillments or other licensing issues, follow the below process to have Tableau Server confirm its licensing status and completely restart and rebuild the search index:
    1. Remotely connect to the machine hosting Tableau Server
    2. Open a Command Prompt as Administrator
    3. Run tsm stop
    4. Once Tableau Server is fully stopped, you may wish to take a backup. While we don't expect anything we do here to cause issues for the system, it may be worthwhile just to have.
      1. To take a backup, perform the following steps. It will also be worthwhile to read our documentation on taking a full backup, which goes over considerations on space needs and when using the below process is the best option (https://help.tableau.com/current/server/en-us/backup_restore.htm)
        1. First, to back up the settings and configuration for Tableau Server, enter: tsm settings export -f <filename>.json
        2. Next, to backup the repository and filestore information, enter: tsm maintenance backup -f <filename>.tsbak -d
        3. By default, these files will be saved to C:\ProgramData\Tableau\Tableau Server\data\tabsvc\files\backups\ . For more information on that, go here (tsm File Paths)
    5. After taking a backup if desired, change the directory to the Tableau Server directory in order to run the lmreread command
      1. Assuming a standard install location, the directory can be reached by entering cd C:\Program Files\Tableau\Tableau Server\packages\bin.<version_code> 
    6. Once we're in the Tableau Server directory enter the command lmreread
      1. This command has Tableau Server's licensing manager re-read all the information we previously gathered in the licensing results file, and verify it against Tableau's licensing servers. If the licensing information was verified by Tableau Support previously, there should be no issues here.
    7. Once the lmreread command has been run, we'll want to reset the search server by running: tsm maintenance reset-searchserver
    8. After that command finishes, we'll want to bring the server back up with tsm start

Cause

This issue appears to occur because of a corruption to the underlying searchserver index. This can occur during an unexpected reboot, after system upgrades, etc. The tsm maintenance reset-searchserver command gets rid of the old index and completely rebuilds it. 
Did this article resolve the issue?