8 Replies Latest reply on Apr 7, 2016 11:58 AM by Stephen Hicks

DataSourceException Error for reports connected to extract

Mansi Parekh Sep 25, 2015 3:33 AM

Hi,

From last few days, Tableau server is showing error while opening the reports which are connected with Extracts. Getting the below error:

'DataSourceException: Tableau Data Engine Error: 8: An error has occurred in IPC_Socket::Recv(buffer length=16) An existing connection was forcibly closed by the remote host '.

Also, the Extracts refresh fails everytime, showing the same error.

Screenshots are attached.

i would really appreciate if someone can help me resolve the above issue.

Thanks in advance!

Mansi

BackGround Task.JPG 39.6 KB
Extract Report Error.JPG 47.2 KB

1. Re: DataSourceException Error for reports connected to extract

Jade Koskela Sep 25, 2015 9:50 AM (in response to Mansi Parekh)

Can you attach logs? All of the backgrounder/tabprotosrv logs under tabsvc/logs/backgrounder or tabsvc/backgrounder/logs
Like Show 0 Likes(0)

Actions
2. Re: DataSourceException Error for reports connected to extract

Vineeth Vasudevan Oct 15, 2015 6:46 AM (in response to Mansi Parekh)

Did you find an answer to this? I am getting the same error when publishing the report.
Like Show 0 Likes(0)

Actions
3. Re: DataSourceException Error for reports connected to extract

Mansi Parekh Oct 26, 2015 9:13 AM (in response to Vineeth Vasudevan)

Greg at Tableau Support helped us through this problem. The main issue was with the permissions between Tableau server and data server.
Like Show 0 Likes(0)

Actions
4. Re: DataSourceException Error for reports connected to extract

Luke Brady Jan 6, 2016 8:48 AM (in response to Mansi Parekh)

I am getting this error now. Tableau Server 9.2.
java.util.concurrent.ExecutionException: com.tableausoftware.nativeapi.dll.DataSourceException: Tableau Data Engine Error: 8: An error has occurred in IPC_Socket::Recv(buffer length=16)
An existing connection was forcibly closed by the remote host
If I make the Extract Live instead of Extract I can Publish. I get this error even when I am Publishing an Extract that is based off of a Text File. Additionally, none of my Extracts are able to be refreshed successfully. I believe the root cause is the same whatever it may be.
Like Show 0 Likes(0)

Actions
5. Re: DataSourceException Error for reports connected to extract

Luke Brady Jan 8, 2016 6:52 AM (in response to Luke Brady)
I was able to fix this issue. I believe our root cause was the Repository / Filestore and Active / Passive being switched from Worker 1 to Worker 2 when were testing High Availability in our environment and forceably brought down Worker 1 for the test.

Resolution:
Stop Tableau Server
Remove all services from Worker 2. Add all services to Primary
Start Tableau Server. Wait for services to sync
Stop Tableau Server
Remove all services from Primary except Gateway and Index Search. Add all services back to Worker 2.
Start Tableau Server. Wait for all services to sync
Like Show 0 Likes(0)

Actions
6. Re: DataSourceException Error for reports connected to extract

Stephen Hicks Apr 7, 2016 5:58 AM (in response to Mansi Parekh)

I'm getting this Forcibly Closed error with Tableau Online (where I have no control of the server side).
Any thoughts on what might cause it?
Like Show 0 Likes(0)

Actions
7. Re: DataSourceException Error for reports connected to extract

Luke Brady Apr 7, 2016 11:55 AM (in response to Stephen Hicks)

The error can only be fixed by a Server Administrator. I believe the root cause has something to do with the Server being ungracefully stopped by OS reboot or some other reason for the actual Box running the Server to go down. When it comes back up it does not sync correctly with the Active Repository and that somehow causes the issue. (This is just a guess)
Like Show 0 Likes(0)

Actions
8. Re: DataSourceException Error for reports connected to extract

Stephen Hicks Apr 7, 2016 11:58 AM (in response to Luke Brady)

Thanks Luke!
Problem is... I'm using tableau online exclusively in this situation, so if
the server's going down, it's on tableau's side. (which I kinda doubt, or
would worry me if true)
Hmmm....

On Thu, Apr 7, 2016 at 11:55 AM, Luke Brady <tableaucommunity@tableau.com>
Like Show 0 Likes(0)

Actions