Ask Data Enable Failed Error State

Published: 12 Nov 2019
Last Modified Date: 08 Jul 2022


Ask data feature is not working for any data source and displays this error:

"Ask data not available".


ERROR com.tableausoftware.tabadmin.agent.state.AgentServiceStateMachine - Exception while trying to enable elasticserver_0.20191.19.0417.1429
java.lang.RuntimeException: Failed to enable service elasticserver_0.20191.19.0417.1429, result code 1.


received shard failed for shard id 
Caused by: org.elasticsearch.index.shard.IndexShardRecoveryException: failed to recover from gateway
Caused by: org.elasticsearch.index.engine.EngineCreationFailureException: failed to create engine
Caused by: org.apache.lucene.index.CorruptIndexException: misplaced codec footer 


  • Tableau Server


Follow these steps to resolve the issue with the index:
  1. Stop Elasticserver
    • First stop tabadminagent
    • Then call C:\ProgramData\Tableau\Tableau Server\data\tabsvc\services\elasticserver*\disable.cmd for the Elasticserver service.
  2. Go to the host with the elasticserver service. On Tableau 2019.2 or higher, you may have multiple hosts; if so, do steps 3-5 on each
  3. Navigate to C:\ProgramData\Tableau\Tableau Server\data\tabsvc\elasticserver\0\nodes\0
  4. Rename the indices/ folder to a different name (within the same directory is fine).
  5. Enable the Elasticserver service:
    •  C:\ProgramData\Tableau\Tableau Server\data\tabsvc\services\elasticserver*\enable.cmd
    •  C:\ProgramData\Tableau\Tableau Server\data\tabsvc\services\elasticserver*\data\run-sgadmin.cmd
  6. Start tabadminagent.
  7. Go to the TSM Admin Web GUI, check if all NLP services are ACTIVE and HEALTHY.
    • If any of the nlp services does not have status ACTIVE and HEALTHY, go to the corresponding node and kill the service in the Process Manager. Then tabsvc will automatically restart the terminated NLP service.


The index is corrupted on elasticsearch. This may occur when a vm snapshot is restored from backup.

Additional Information

Steps for 2021 and later:
When elastic server is removed from a node, indices folder remains in that node. If indices had issue, reverting the elastic server to the original node does not recover the corrupted indices. Remove indices from node that previously had elastic server but now the service is moved to another node follow these steps. After following below steps, if elastic server is re-added to the original node, new indices folder will be generated: 
  1. Stop tabadminagent:  net stop tabadminagent_0
  2. Navigate to C:\ProgramData\Tableau\Tableau Server\data\tabsvc\elasticserver\0\nodes\0
  3. Move the indices folder to a different location .
  4. Start tabadminagent  net start tabadminagent_0
  5. Go to the TSM Admin Web GUI, check if all NLP services are ACTIVE and HEALTHY.
Did this article resolve the issue?