Dataflows - Redshift Connector - "An exception occurred: 'ProviderName' is not a valid Amazon"...

[Anonymous]

Hi everyone!
Since yesterday we are having troubles to build up Dataflows from scratch.

If we want to create a new Dataflow connecting to Redshift, we have to re-use Dataflows because we get this message:

An exception occurred: 'ProviderName' is not a valid Amazon Redshift option. Valid options are: 'BatchSize, Role' (Session ID: *********************************, Region: europe)

Maybe the Redshift Connector is broken: It seems that it is sending 'ProviderName' instead 'BatchSize' or 'Role'.

Anyway, already created Dataflows are working, and we can create new ones just using another .json dataflow configuration, or just hard coding the queries without using the connector.

Have been changes recently made to the connector? 

Thanks in advance! Cheers!

[Anonymous · Accepted solution]

Connector has been updated and now is working fine. Thanks all!

[Anonymous]

I am having this same issue, how do you update the connector? Were you able to get it updated in the gateway machine?

[v-yalanwu-msft]

Hi, @Anonymous

What happens if you try and use an ODBC connection instead of the Amazon Redshift option and see if that works?

You can use the blog post here to show how to configure the ODBC connection: Using Azure Analysis Services to connect via an ODBC Source (Redshift) - Reporting/Analytics Made ea...

 

Best Regards,
Community Support Team_ Yalan Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi @v-yalanwu-msft , thank you for your response.

First of all, the connector is still failing when trying to build new DataFlows, but its working fine with already created ones. 

We have not access to the GateWay machine, so we cannot install the redshift driver -> we cannot use the ODBC connector with Redshift.

Anyway, from my point of view, using ODBC connector while having an official connector that we use everyday(Redshift) that is kind of broken is not a valid solution. 

I really don´t know yet if anything changed in the official Redshift connector, but seems so. Any clue?

Regards.