"No Tableau Server user found." is odd
Have you tried republished the offending workbooks with the same version of Desktop (10.2)?
1 of 1 people found this helpful
Have you checked the knowledge library - there's a couple of articles that reference this error, but they may not be relevant but worth double checking the articles anyway.
I tried what was recommended in the articles. Still no luck. Case has already been registered with support. Awaiting their response.
Thanks for the update Vamsi - be sure to update this thread with whatever Support respond to you, so others can be helped too.
We are experiencing this same/similar issue. Has this issue been resolved for you? Did you open a case? Any progress? We opened our case in mid June have made little to no progress. We recently upgraded Tableau Server from version 9.2.6 to 10.1.7. This is happening intermittently for several users including us as system admins. Has happened to about 10 workbooks. The server in which the error is reporting as occurring on (Unable to connect to the server xxx.xxx.xxx.xxx) is our dedicated backgrounder server that only has Cluster Controller, Cache Server and Backgrounder processes configured to run. Given this configuration, for the error msg to reference this server makes no sense. Why is it even trying to go to this Worker since this server is used exclusively for backgrounder tasks. NO Data Engine or Data Server processes are running on this Worker – so what part of the process flow to fulfill a viz rendering using an extract data source would cause this worker (dedicated backgrounder) to be involved?
Vamsi, when you replaced node X with node Y, were these worker servers dedicated as backgrounder servers? When you did the replacement, was node Y already part of your server cluster?
We're having this issue as well. Has anyone found the resolution?
This is a fairly generic error and there is not a "one-size-fits-all" solution. For that reason I would strongly recommend opening up a Technical Support case so that we can investigate your specific situation in depth.
Sorry for replying too lately. It has been identified as a bug and not sure if a fix for the same has been released.