Publish to Tableau - Connection Issues

dlund2010

Hi all, I have a query I am pulling from a SQL Server DB and trying to push into Tableau. I am using a personal token to connect to Tableau, and I am successfully connected in the left pane.

However, when I run the workflow, I get the error "Connection to platform was not successful".

Any insights?

Tableau

Accepted answers

All comments

gyang3

Hey @dlund2010

Have you checked whether you have permission to write to the specified data source in Tableau Server? You should either be the owner of that data source or have been given permission by the owner. If you're able to connect to Tableau initially but received a connection error when running that workflow, this could be the reason why it's not able to connect.

Let me know if that helps. If so, please mark as solution!

dlund2010

Thanks! I am the owner of that data source, but not the administrator on the server.

gyang3

@dlund2010seems like it could be a proxy issue then. Check out this article that provides a solution to your issue.

https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/Connection-Errors-with-Python-based-Connector-Tools-when-running/ta-p/460217

If this helps, please mark as solution so others can utilize it as well.

PCFennessey

I am getting the same error message, I also get "Failed to append." sometimes even though the tool is set to overwrite. I am the admin no for the tableau project and I write to the same location but different extracts in the same workflow.

albert_alaluf

Please check this. It didn't fix our problem, but it may fix yours.

https://knowledge.alteryx.com/index/s/article/Download-Tool-SSL-Connect-Error

datadetangler

I just keep getting the same error for both the Tableau Input and OUtput tools " Connection to platform was not successful" and even though I have tried everything from ensuring the correct certificates are installed and I used the "PeervalidationBypass.txt" cannot get the tools to work. Even Alteryx support is struggling to assist mw with this one. Any additional input will be appreciated

runpal

The tool is notoriously unreliable. Never the less I managed to fix a similar issue (Connection to platform was not successful) by putting in some Block Until Done Tools and enable AMP engine compability mode. It was a case with several Tableau Output tools.

albert_alaluf

Hi @datadetangler @runpal

Our issue is still in work with Alteryx tech support. I'm a little bit confident to tall that this is not tool related issue. It's totally with the network and policies on your computer.

Let me explain why?

In our organization we have several, domains, Alteryx and Tableau servers and different version of Alteryx, Alteryx servers and Tableau servers. No need to say depending on the requirements, some servers have exceptions. We have an issue with both Alteryx in local and server to publish to Tableau server, however another part of organization are good. Our sandbox Alteryx server is running well, but not the production server. I was able to publish to another Tableau server from my desktop, but not to my department's Tableau server. The latest version of the output tool (1.4.0) I found a defect and was being replicated and accepted by Alteryx. I can say too much things about the tool. But one thing is independent from the tool. When I tried to connect Tableau server thru an API, it didn't work either for my department, but it worked with other server which was working fine with the tool. All depends on proxy, security, policies, open ports and certificates installed on your computer and server. W are still working to fix. Interim solution is to use tabcmd tool which it's working. I hope this helps both.

Albert

csh8428

See my fix here.

Please like and select as solution if this works for you.

-Craig

aoxomoxoa

if you are using more than one Tableau Output tool,

you should create a separate token for each one, with the appropriate keys.

it seems the macros get conflicted if you session uses the same token

it is simple to create multiple tokens, just keep them straight

I struggled with this for a very long time, but that solved it.

Nothing to do with access etc.

I even tried timing the output with StopUntilDone and eventually control containers, to no avail.

good luck/

Using the PAT authentication option with more than one Tableau Output tool causes concurrent session issues; only one session can be open at a time.

Resolve by switching to the user name and password authentication method works best for us!

You could also use Control Containers to have only one sessions at a time OR by writing a single Tableau Output tool with multiple connections going into it can produce 1 Tableau Datasource with multiple "tables" but this requires a TDS file.

Quick Links

This months top contributors

SophiaF 432

AkimasaKajitani 390

mceleavey 388

mbarone 337

michael_weaver 335