Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.
Don't forget to submit your entry for the Excellence Awards by October 30! | Need more information about the program? Check out the blog here

Publishing to Google sheets failure

Highlighted
8 - Asteroid

I'll preface this an say I have a designer account and no access to our companies servers. The admin team has been in the midst of updating to the newest Alteryx Server they plan to support 2020.2, as well as migrate our servers to AWS. They have been unable to answer my problem. So I turn to this great community.

 

I have a several worklfows that write data to google sheets as the output but it seems this one is the only troublesome one.

 

It runs 4 times a day, output is small 160 columns and about 1300 rows. I get this error:

wmcclure_0-1595848179141.png

Tool #103: Tool #402: Error trying to publish spreadsheet: HTTP/1.1 400 Bad Request Vary: Origin Vary: X-Origin Vary: Referer Content-Type: application/json; charset=UTF-8 Content-Encoding: gzip Date: Fri, 24 Jul 2020 02:05:39 GMT Server: ESF Cache-Control: private X-XSS-Protection: 0 X-Frame-Options: SAMEORIGIN Alt-Svc: h3-29=":443"; ma=2592000,h3-27=":443"; ma=2592000,h3-25=":443"; ma=2592000,h3-T050=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43" Transfer-Encoding: chunked

 

There are two Sheets outputs; one overwrites (drop) and the other appends. The Append on is what fails. It is by far the simpler of the two; essentially outputting an update log. Four columns  and at most 15 rows.

 

When I run from my local, the workflow runs fine. But from Server, it has consistently failed.

Highlighted
Alteryx
Alteryx

if it runs on your own local Desktop but not on the server, you will unfortunately actually need help from the Server team to do the following:

1- RDP to the server box

2- Start Designer installed there

3- Open/download your workflow and try to run it on the Designer installed on Server. The message will be visual and more specific.

it could be that Google Sheet connector was not installed on the server or it is a different version of the tool than the one you used. Designer could also be a different version and that could in some cases explain why it behaves differently.

It could also be that the Run As user on the server (if it is used) doesn't have the required network access as well.