KNOWLEDGE BASE

Error "Tableau Data Engine Error: 4: Invalid Command: database: Path does not exist" Publishing with Tabcmd


Published: 08 Aug 2013
Last Modified Date: 08 Sep 2016

Issue

When using tabcmd to publish a workbook with references to a Tableau Data Extract (.tde) file, the following error might occur:

Tableau Data Engine Error: 4: Invalid Command: database: Path does not exist.
Unable to connect to the file "C:\ProgramData\Tableau\Tableau Server\data\tabsvc\file_uploads\uploads_###\{DataSourceFile.tde}". Check that the file exists and that you have sufficient access privileges for it.

Environment

Tableau Server 

Resolution

1. Publish the local .tde file to Tableau Server
2. Open the workbook in Tableau Desktop
3. Replace the local data sources with the published data sources
4. Publish .twb via tabcmd

OR

1. Open the workbook in Tableau Desktop
2. Save the workbook as a .twbx
3. Publish the .twb via tabcmd

Additional Information

When you publish a workbook to Tableau Online or Tableau Server, Tableau needs to be able to find the data in order to render the view. So there are a few different ways you can publish:

1. If all of the data source connections used in the workbook are live connections, you can publish as a .twb and Tableau will use the connection metadata in that file to maintain a connection to the data sources in the published version.

2. If any of the data source connections used in the workbook are extracts, then it needs to be published as a .twbx in order to include a copy of the extract. Without a copy of the extract, the published view wouldn't render.

3. The exception to 2 is if, prior to publishing the workbook, you separately publish the data sources themselves. When publishing the data source, a copy of that extract is posted separately to Tableau Server or Tableau Online, and then you can publish using a .twb because Tableau will use the metadata included in that file to maintain a connection to the published data source. Even if the published data source is an extract, Tableau is maintaining a live connection to that published extract, so another copy of the extract doesn't need to be included during publishing of the workbook.

Did this article resolve the issue?