Can you attach logs? All of the backgrounder/tabprotosrv logs under tabsvc/logs/backgrounder or tabsvc/backgrounder/logs
Did you find an answer to this? I am getting the same error when publishing the report.
Greg at Tableau Support helped us through this problem. The main issue was with the permissions between Tableau server and data server.
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.
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.
- 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
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?
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)
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)
On Thu, Apr 7, 2016 at 11:55 AM, Luke Brady <firstname.lastname@example.org>