topic Re: BigQuery Input/Output Connector on Server in Alteryx Server Discussions

BigQuery Input/Output Connector on Server

RColwell — Tue, 15 Jan 2019 21:48:37 GMT

I have downloaded and implemented the Google BigQuery Input and Output connector that are now available via the Gallery. I would like to publish the workflow to our server so that I can schedule the job to run on a daily basis. I have configured the BigQuery Input connector to use the "Service-to-Service" connection which uses a json file to get the service account account and key. When I attempt to run on the server the workflow fails because it is looking for the JSON file. Is there a way I can configure the server so that it will use the file?

Alteryx Designer and Server versions are 2018.4

Error text:

The job Non Search Test did not complete successfully and resulted in the following errors:

· Failed to decrypt value for serviceCredsJSONStr! (Tool Id: 18)

· Service account JSON not provided. Please specify a path to your service account file. (Tool Id: 18)

· Failed to decrypt value for serviceCredsJSONStr! (Tool Id: 31)

· Service account JSON not provided. Please specify a path to your service account file. (Tool Id: 31)

· Failed to decrypt value for serviceCredsJSONStr! (Tool Id: 40)

· Service account JSON not provided. Please specify a path to your service account file. (Tool Id: 40)

Re: BigQuery Input/Output Connector on Server

EricWe — Mon, 04 Feb 2019 17:32:20 GMT

Hi @RColwell

The JSON file should be in a location accessible by the Gallery. Can you put the file on the Gallery server or a shared drive that is accessible by the server? Also, when publishing the workflow to the Gallery be sure to select the option to Manage workflow assests in the Save Workflow menu. Then you can ensure that everything needed to run the workflow is included.

For details about these tools and links to Google documentation, please see this Community article: Goggle Big Query Tools.

Re: BigQuery Input/Output Connector on Server

ronniet7626 — Wed, 14 Aug 2019 14:09:33 GMT

I am facing the same issue, I have created the workflow on a different server but I have used a credentials json file on my Gallery server to run the workflow. The workflow runs fine as I have mapped a drive to the Gallery server where the json file is located, however when I try to save the workflow to Gallery I receive the error

There is no option to specify the path to the json file when saving the workflow to Gallery.

I am currently running

Re: BigQuery Input/Output Connector on Server

SophiaF — Thu, 15 Aug 2019 13:21:11 GMT

Hi all - we are very sorry to see you are running into this issue. This is tied to a current defect our development team is diligently working on (DE17386). While I do not have an ETA on when a fix will be out, we will be sure to update this post when a release with the fix is available!

Our apologies for any inconvenience caused!

Re: BigQuery Input/Output Connector on Server

TylerB — Fri, 13 Sep 2019 19:34:04 GMT

Hi Sophia - any update on this defect or a location where we can track it. I ran into a simliar error issue with the Power BI Output Tool (v2.1.2) and this community thread was the only thing that came up via search that seemed to be similar.

Re: BigQuery Input/Output Connector on Server

eric_strein — Tue, 17 Sep 2019 15:10:50 GMT

We're experiencing the same issue with BigQuery output credentials on our schedule server.

We need to remain in BigQuery for the speed it provides, has anyone discovered a workaround for this?

Re: BigQuery Input/Output Connector on Server

SophiaF — Mon, 30 Sep 2019 08:34:59 GMT

@eric_strein @TylerB - we have a fix. Please reach out to Customer Support referencing the defect DE17386 and we will be happy to provide it!

Re: BigQuery Input/Output Connector on Server

michaelhakansson — Mon, 18 Nov 2019 15:15:35 GMT

Could you share the fix for defect DE17386 here?

Re: BigQuery Input/Output Connector on Server

SophiaF — Mon, 18 Nov 2019 15:29:09 GMT

@michaelhakansson there are a few steps to configure on both the Server and the local machines, so we ask that you reach out to Support so they can walk you through it for your specific environment. Thank you!

Re: BigQuery Input/Output Connector on Server

michaelhakansson — Tue, 19 Nov 2019 11:28:45 GMT

I thought it would be good to share the resolution for me:

Pre-work: Upgrade to Server 2019.3

After the designer/server upgrade the following needs to be performed on each machine that will upload BigQuery workflows to the Gallery:

Create key on local machines
Administrators will need to create a new string value PythonAllowHideEncryption under the Alteryx Registry Key:

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SRC\Alteryx
Value Name: PythonAllowHideEncryption
Value Data: true
Note: This key must be set on each user’s machine as well as on all Worker nodes.

Steps to create the new key:
Type regedit in Windows Start Menu
Browse to the folder location: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SRC\Alteryx
Right-click and select New > String Value

Set the KeyName to PythonAllowHideEncryption and the Value to true

Effects in the Gallery
The below descriptions assume that all users interacting with the Gallery have the registry key set to true.

a. Uploading to Gallery:

Encrypted values for the supported Python tools (such as the BigQuery tool) will be updated to hide encryption once you publish it to the Gallery.

b. Running on Gallery:

Only workflows that originated from machines with the registry key set will be able to run successfully in the Gallery. The worker nodes must also have the registry key set and the respective Python tools (such as the BigQuery tool) installed.

c. Opening from Gallery:

The original encryption method will be restored. These Python-based tools (such as the BigQuery tool) might need to be reconfigured in order for the workflow to run.

Re: BigQuery Input/Output Connector on Server

PhilBalderson — Wed, 05 Feb 2020 10:48:34 GMT

Any update on this, or do we still reach out to support?

Re: BigQuery Input/Output Connector on Server

michaelhakansson — Thu, 06 Feb 2020 10:31:34 GMT

The solution in my previous post was based on the information I got when I contacted support. Adding the registry entry mentioned and disabling local validation when uploading the workflow to the Gallery should do the trick.

Re: BigQuery Input/Output Connector on Server

priyank31 — Mon, 24 Jul 2023 02:14:36 GMT

We are also using this solution in our environment for Salesforce Input tool v4.2.4.

Server Version: 2022.1.1.42636

The steps for key creation will be similar to what michaelhakansson has mentioned in the above post.

Re: BigQuery Input/Output Connector on Server

NatalieWagner — Wed, 03 Jan 2024 20:06:17 GMT

Hi Michael,

My team and I are running into the same exact issue with the BigQuery Connectors.
Our key file is stored on a shared drive that we all have access to, however if, for example, I was the last person to connect to the BQ inputs and outputs to the key file in our shared drive and saved it, then another team member opened the workflow, they will see the error "Invalid service account keyfile. Check that you specified a valid JSON keyfile" despite having the same shared drive mapped to their network.

Based on this thread we all followed the instructions laid out for adding a registry key to the Alteryx folder (attached) and even restarted Alteryx and our machines. But we still run into the same error. Do you have any insight on what we might be doing wrong?

We are all using Alteryx version 2021.4

Thanks!

Re: BigQuery Input/Output Connector on Server

m_v — Wed, 10 Apr 2024 13:53:35 GMT

Hi all, getting the same error and the proposed solution does not work. My registry looks like this: