could it be that there is an authentication issue? What id is being passed into the Rserve? Maybe is it the Tableau Server runas account, or is it the individual user id, or is it the id that was used to generate the trusted ticket?
Are you're embedding a Tableau visualization hosted on a Tableau Server in a page hosted on another server? In that case this should just work because Tableau server will call Rserve directly. Or is it a different setup?
It is a stab in the dark but you may want to give a shot to setting remote enable in Rserve config file if you haven't already.
Thanks for the reply Jeff. RServe does not require a username and that is how things are set up between Tableau Server and RServe. Users authenticate to the portal with Active Directory credentials which are in turn used to request trusted tickets to execute a visualization. Obviously since the visualization runs fine in Desktop and when accessed through Tableau Server, there is some disconnect between the portal and accessing the RServe box. When I remove the R-specific piece of this dashboard, the rest of the dashboard runs fine..... Kind of stumped.
Hi Bora and thanks for the input. Yes, your description of the embedding of a visualization is correct. And I too thought it should just work, particularly since it works fine in Tableau Server's interface.
I double-checked and RServe is running with remote enable (set up in config file and RServe started using that config file). I understand that the portal/ticket set up may not be typical though. It just seemed like it should work when all else seems to be working. As I mentioned in the earlier post to Jeff, when I remove the R code from the visualization, the rest of it shows as expected so it is surely appears to be an issue of the web server running the portal talking to the RServe interface. I was expecting that Tableau Server would do the heavy lifting and just send data back to the client but maybe that is not how it works...
Tableau server communicates directly with Rserve and serves the results. It doesn't act as a bridge to connect client to Rserve. It also doesn't use the user's credentials to connect to Rserve, it connects to Rserve based on credentials defined using tabadmin regardless of user's credentials. So there is something else going on here.
Is there any more detail you can share on the error message? E.g. if you modified your R code and inserted code to try catch errors and write to csv it may help understand what the error is.
The error message is pretty non-descript (see below). Obviously resetting the view does not help. I will try to modify the R code to simply return something basic and not run the K Means Cluster algorithm so see if that makes a difference. Then I will know if it is indeed a connection issue or whether something more abstract happening. Thanks for the suggestion.