Show Table of Contents
This topic describes errors you can receive when Tableau is connected to an external service.
Note: Tableau technical support cannot assist with writing, troubleshooting, or debugging external scripts.
Errors That Can Occur When Communicating with Any External Service
Errors that Can Occur Only with an Rserve Server
|Unsupported type passed as an argument to SCRIPT function.||
Tableau can only export the following Tableau data types to R:
|Unexpected number of results returned by SCRIPT function. Function expected %2 values; %1 values were returned.||The script result must be either a scalar or vector of length one that is replicated for all rows, or a vector of length equal to the number of rows in the Tableau result table.|
|The result returned by the SCRIPT function is of an unexpected type.||
Occurs when an invalid data type is received. Tableau can only import the following data types from an Rserve server:
For TabPy, Tableau can import the following data types:
This error is also reported if the result is null or if there was a script execution error for which Tableau could not collect an explanation from the external server.
|This worksheet contains external service scripts, which are not supported on the target platform.||This error is reported when you attempt to publish a worksheet containing an external service call to a Tableau server that does not allow external scripts because
|This worksheet contains external service scripts, which cannot be viewed on the target platform until the administrator configures an external service connection.||
This error is reported when the server is configured to prevent Desktop from publishing worksheets with external service scripts because
|An error occurred while communicating with the external service.||Tableau runs all external scripts inside of the "try" external function. This error is displayed along with an external-service-generated error message when the “try” function traps an evaluation error.|
|This external service connection does not support authentication. Try connecting without specifying a password.|
|Authentication failed. Please provide a valid external service username and password.|
|An unsupported authentication type is enabled in the external service.||Either disable external service authentication or change to plaintext password authentication.|
|No external service connection configured. Specify a server name and try again.||See Pass Expressions to External Services.|
|The calculation '%1' contains a SCRIPT_ function that requires an internal service connection. Configure your external service connection to enable custom scripts.||See Pass Expressions to External Services.|
|The workbook you are attempting to publish contains SCRIPT_ functions that require an external service connection. Custom scripts are not allowed in public workbooks.||You cannot publish workbooks containing external service scripts to Tableau Public.|
|Tableau Public does not support running custom scripts that require external services. To take advantage of external services, upgrade to Tableau Desktop Professional Edition.||The "Tableau Public" in this error refers to Tableau Desktop Public.|
|Tableau Reader does not support running custom scripts that require external services. To take advantage of external services, upgrade to Tableau Desktop Professional Edition.||You cannot view workbooks containing external service scripts in Tableau Reader.|
|The external service is busy or not responding.||
Tableau has timed out a read pending on connection to Rserve – the default timeout is 250ms. An IPC connection Read of the Rserve protocol header has thrown an exception.
A tabadmin set setting, vizqlserver.esxtsvc.connect_timeout_ms, is available for extending the timeout value, in milliseconds, for connections to Microsoft’s RServer. Raise the value of this setting if Tableau is timing out before the server can respond. For more information, see tabadmin set options in the Tableau Server help.
|Unrecognized Rserve signature.||The Rserve header signature must be "Rsrv".|
|Unrecognized Rserve version.||The Rserve header version must be "0103".|
|Unrecognized Rserve protocol.||The Rserve header protocol must be "QAP1".|
|Authentication failure when connecting to R.||Tableau attempted and failed to authenticate with Rserve. Verify that you entered a valid password.|
|Incorrect number of bytes in parameter/body.|
|The length of data which Tableau read does not equal the length promised by the header.|
|Unrecognized response type.||The transport protocol type when reading a result was not SEXP as expected.|
|Excessively long <type>vector.||Unreasonably large number measuring the length of data sent to or from Rserve possibly indicating a corrupt protocol header.|
|Invalid Rserve command.||Tableau may have improperly implemented the Rserve protocol.|
|Response from server was Error " << (uint32_t)status << ". See Rsrv.h for details.||Various error conditions are documented in the comments in Rsrv.h.|
|Excessively long header offset.||This may be due to a garbled header with an unreasonable offset to response data.|
|Rserve socket failed.||A login, script evaluation, read pending check, result read, or Tableau field to R script argument assignment threw a non-standard exception.|
A function that sends an expression to a running external service instance will be executed even when it is within a logical statement that would otherwise prevent it from being executed. This is true for logical functions such as IF, IIF, and CASE. For example:
IF 1==0 THEN
[[R script code]]
"1 does not equal 0"