I have a fairly big data source that I have published to Tableau server and use this data set for a bunch of my reports. In the last 2 weeks or so I have been constantly getting this error unless I filter my data set down. This is what is shown when I click Details on the Reconnect to 'data source' error. I can click yes all day long and nothing will happen. I have to click No and then after a couple of cancels I will then get out of it.
Mar 26, 2018 9:19 PM
Hello Jeremy,
What version of Tableau Server is this occurring and is this data source an extract? Are there any LOD calculations in use?
Cheers,
Byrne, Patrick
Tableau Server 10.5.0
Yes to Extract and no to LOD. I have a case opened up with Tableau and they are trying to figure it out.
Mar 28, 2018 7:07 AM
Excellent! Our Technical Support Engineers are excellent and will be able to assist porperly assessing the issue and coordination of any Developer resources if needed.
Happy to see the case is in queue and will be picked up by the next Engineer as soon as possible.
Cheers,
Byrne, Patrick
They have been kinda slow on responses.
The main errors lately have been
Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 7483? Could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 7483?
All of my research so far is pointing to a PostgreSQL error but don't know where to go from there.
Aug 20, 2018 11:03 AM
I'm getting this error as well (TS 10.5.2). I'm opening a case with Tableau Support. No info at this time.
Hi Toby
Did you get a response from support? I'm running 10.5.2 and started getting the same errors recently. Using Postgres as well.
Thanks,
Jason
Sep 26, 2018 6:30 AM
Thanks for the reminder
I'm not sure if I can help The good news is that there were some Windows OS patches pushed to the company's servers and the issues stopped. Was this the fix? It appears to be so but I won't guarantee it.
Side note: A couple weeks later we upgraded to 2018.1.4 so we're no longer in version 10.
We have a case open with support. Trying to understand exactly what the problem is and what is causing it before we consider upgrading. Going to look at the windows patches to see if that makes a difference.
jason jones - Did you find the root cause yet? I am running into same issues. thanks.
We added 2 server processes earlier, before we had these errors. Those 2 processes made it so we kept on running out of memory which was the root cause of all of my issues. We upped the memory on my production server and have been running fine since.