I am facing the same issue as well for the past couple days, trying to publish a datasource to Tableau Online server from Desktop 9.3.
Anyone know when Tableau Online was upgraded to 10.0?
They upgraded Tableau Online to 10.0 last Wednesday which is when I started having the issue. I'm surprised nobody else is commenting here. I would assume that a lot of people are having the same problem. Hopefully someone will figure out what's going on. I opened a case with technical support but they tend to take forever so I'm hoping someone here could shed some light on the issue.
I too am having the exact same problem. However, it is not will all workbooks.
Were are experiencing same issue on some SQL Server data source.
we have a case open and we are working with tableau on this case.
not all ou SQL server data sources are experiencing the same issue.
Thanks Benjamin. I seem to be having issues with SQL server as well. Still haven't heard back from Tableau on my open case.
Tableau was able to reproduce with an extract and logs we provided to them.
will see if anything comes from that....by the way there is a maitenance schedule maybe it will fix the problem.
We are having the same problem too. It would be nice to hear some feedback from Tableau directly.
Thank you all for bringing this to our attention. Our development team is actively working on this issue. We'll let you know as soon as we have an update.
I'm glad your development team is working on this issue, but I need and we all deserve a greater level of detail and transparency about this issue.
We can't get new data sources published because of this problem. That means my team can't get work done. That means that I am getting questions by our executive team regarding why they aren't getting the new and updated dashboards that I promised them. At the moment I can only tell them "Tableau knows about the problem and they're working actively on it". An answer which neither they or I am satisfied with. They have then replied with "How much does Tableau cost us per year? Are there better alternatives we can use instead?"
I want a better response than "Yeah, we're working on it". I want to know
1. Do you know what the problem is yet or are you still trying to figure that out?
1b. If so, can we provide you with any additional information to help track that down?
2. Do you have an estimate about when this functionality will be working properly again?
2b. What is your confidence in this estimate?
2c. What are the unknowns that could affect your estimated time line?
These are the kinds of simple questions I would ask anyone working for me when they encounter a significant impasse.
2 of 2 people found this helpful
Thank you again for helping bring this to our attention and for helping us understand the severity of the issue. We apologize for the inconvenience this has caused.
We have identified the issue and it occurs for some large extracts published to Tableau Online. In order to mitigate this issue, we will be making a configuration change to better handle these large extracts on our servers. We anticipate this change will go out today.
Meanwhile, if you have received this specific error - “Internet communication error: Failure when receiving data form the peer” - it is not an indication that your publish has failed, and there is a good chance your publish will ultimately be successful.
While we do not have a workaround until the fix goes out today, here are best practices on reducing the sizes of your extracts:
We will update you this afternoon as soon as the change goes out.
1 of 1 people found this helpful
This is taking longer than anticipated and we will have the next update for you on Monday.
If you continue to experience the issue, please contact support via our web form at tableau.com/support/request and include the following information:
- The text of your error message
- The size of your extract
- Connection type (Excel, SQL Server, etc)
- What you published from (Desktop, tabcmd, REST API, etc) and the version
This morning refresh did work without any changes on our side !
do you have the same experience today ?
Glad to hear Benjamin!
We were able to ship a configuration change that should help mitigate the issue, and again if you do have issues with publishing please submit a support case here: