KNOWLEDGE BASE

Errors: "TableauException" or "Could not find sheet with name: <SHEET>[0]" When Publishing a Workbook to Tableau Server or/and Tableau Online


Published: 28 Jul 2017
Last Modified Date: 22 Feb 2018

Issue

After publishing a workbook, one of the following errors might occur:
 
Unknown server error
An unexpected error occurred. If you continue to receive this error please contact your Tableau Server Administrator. Session ID ... 
Would you like to reset the view?


or

Session Ended by Server: An unexpected error occurred. If you continue to receive this error please contact your Tableau Server Administrator. Session ID: SESSION <HTML> <HEAD> <TITLE> Service Unavailable </TITLE> </HEAD> <BODY> <H1> Service Unavailable - Zero size object

or
 
Uncaught Failed to re-initialize session
 
Additionally, you might experience one of the following errors: 

TableauException: Error finding command parameter: yqf

or
 
InvalidSheetIdException:​ Could not find sheet with name: <SHEET>[0]

Environment

  • Tableau Server
  • Tableau Desktop 10.2.2 - 10.2.4 and 10.3.1 - 10.3.2
  • Tableau Online
  • Custom SQL

Resolution

Follow the steps below:

Step 1

Upgrade to Tableau Desktop 10.2.5, 10.3.3 or a newer version. For more information, see Upgrading Tableau Desktop in Tableau Help.

Step 2

  1. Copy the original Custom SQL without the added special characters into a text editor such as Notepad. 
  2. Remove the Custom SQL from Data Source Tab in Tableau Desktop.
  3. Re-create Custom SQL in the Data Source Tab in Tableau Desktop with the text from step 1. 
  4. Re-do any field type conversions, such as a non-date to a date/datetime field .
  5. Create the worksheet and publish to Tableau Server.
For more information about changing the data type of the field, see Convert a Field to a Date Field in Tableau Help. 

Cause

When certain special characters, such as a “<” symbol, are used in Custom SQL, combined with a field data type change from a non-date to a date or datetime, extra line feed characters will be added at the beginning and end of the Custom SQL, as well as added after any other line feed characters that pre-existed.

This behavior is related to a known issue, ID: 659319, that has been fixed in a recent release of Tableau Desktop. 
Did this article resolve the issue?