Publish to Tableau Server, Error after upgrade to Tableau Server 9.2

This morning, we updated our Tableau Server to 9.2 and now each time I attempt to run my workflow, i get an error message on that tool. Nothing has changed in the workflow itself, although I had noticed that, prior to the update, the workflow appeared to complete successfully but I was unable to locate the .tde files on the server. So, I guess I have two issues for which I am hoping someone can assist:

1. When successfully running a workflow including the Publish to Tableau Server tool, where do I find the .tde files that I thought would be created? I can't repoint my Tableau viz to that datasource without being able to locate it.

2. What has changed with the update to Tableau Server 9.2 that prevents my workflow from now completing? This is the error returned:

TableauServer.Log in: Tool #4 Tableau Server API Request (Sign-in) Error Code 400000: Bad Request -- Payload is either malformed XML or incomplete.

Publish

Tableau

Accepted answers

gene_denny

FYI--This turned out to be an issue with the Publish to Tableau Server tool. At the same time we upgraded to Tableau Server 9.2, we were required to update our Active Directory passwords to include non alpha numeric symbols. The Publish to Tableau Server tool was not prepared to handle symbols. Alteryx was all over this issue for me and has updated the tool for all. They sent the installer directly to me and works like a charm. Shoutout to Alteryx support on this one! Kept me in the loop the entire time.

All comments

dataMack

Do you still have a Tableau Server running on 9.0 or 9.1 in a different environment that you could test your workflow against? That should help narrow down the issue to being either on the Tableau side or the Alteryx side - I'm assuming its the former, but I don't have any environments on 9.2 yet so cant test.

gene_denny

Thanks for the response, Jason. I only have the 9.2 environment. Of course, Tableau is stating that they feel this is on the Alteryx side. All I know is that it was fine before the update, and now is not.

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15867

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703