Here are the details: We're nearly 100% certain there's another factor involved here, namely the caching settings on Tableau Server. There are three settings:
- Refresh Less Often
- Refresh More Often
See Configure Data Connections for details. Tableau's default is to Refresh Less Often.
What Shawn and I found was that on a server with the settings set to Refresh Less Often (at least, we're pretty sure that's what the were) when we followed the steps above to publish a TWB with an Excel-based live connection and then moved/deleted that refreshing the view on Tableau Server still worked (whether using Tableau's refresh button or the web browser's refresh button) but downloading the workbook led to a TWB that with a failure to open the data source***. I'd expect that if we'd waited long enough (for the cache to be cleared, whether by expiration or by other users) then we would have gotten the "Unknown Server Error" on Tableau Server as I'd seen. In my case because of users updating data in file-based sources that need to be viewed on Tableau Server right away I'd turned the cache settings to "Refresh More Often", so in my testing there were no Excel files in the cache and the error pops up immediately.
*** This is still different behavior than Kent's original description of downloading the workbook leading to a TWBX, I'm not sure what's going on there.
Thats intresting. Does cache option will lead to not updation of live data means when data changed in source file it will take longer time to refresh in server!! Just wondering!!
Yes, that’s an effect of caching since the goal of caching is to improve performance by not hitting the data source as much. If your Tableau Server is configured to use the Balanced or Refresh Less Often options there are two ways to get the live refresh. 1) using the Tableau refresh button or 2) adding :refresh=yes to the URL on Tableau Server.