error with gateway connector to Amazon Redshift

[Miguel_Ramal]

from yesterday to today we are now experiencing an error with (previously working) Amazon Redshift gateway connectors

we noticed a new gateway software version was available today, redshift connectors started fail on 15 Oct 2020

any ideas what can i do?

error:

Unable to connect: We encountered an error while trying to connect to . Details: "We could not register this data source for any gateway instances within this cluster. Please find more details below about specific errors for each gateway instance."Hide details

Activity ID:	96516f1c-a75a-440c-9ff2-99abc10103f0
Request ID:	b91938a9-fe2a-74b0-e4b4-516b37a03261
Cluster URI:	https://wabi-australia-southeast-redirect.analysis.windows.net/
Status code:	400
Error Code:	DMTS_PublishDatasourceToClusterErrorCode
Time:	Fri Oct 16 2020 00:33:03 GMT+1100 (Australian Eastern Daylight Time)
Service version:	13.0.14437.75
Client version:	2009.4.03166-train

UTS-PowerBI-Gateway:	Unable to connect to the data source undefined.
Underlying error code:	-2147467259
Underlying error message:	ODBC: ERROR [IM003] Specified driver could not be loaded due to system error 126: The specified module could not be found. (Simba Amazon Redshift ODBC Driver, C:\Program Files\On-premises data gateway\m\ODBC Drivers\Simba Amazon Redshift ODBC Driver\AmazonRedshiftODBC_sb64.dll).
DM_ErrorDetailNameCode_UnderlyingHResult:	-2147467259
Microsoft.Data.Mashup.ValueError.DataSourceKind:	AmazonRedshift
Microsoft.Data.Mashup.ValueError.DataSourcePath:	xxx.ap-southeast-2.redshift.amazonaws.com;*db*
Microsoft.Data.Mashup.ValueError.OdbcErrors:	#table({"SQLState", "NativeError", "Message"}, {})
Microsoft.Data.Mashup.ValueError.Reason:	DataSource.Error

[v-lili6-msft]

hi @Miguel_Ramal 

Try to remove this datasource in Manage gateway list and then readd it and try it again.

Regards,

Lin

[mcgovey]

I don't know if you ever resolved this but in case someone comes across it, I had the same problem after the 10/12 update and was able to resolve by reinstalling the Redshift driver on the Gateway server.

[Miguel_Ramal]

Thank you @v-lili6-msft  and @mcgovey  we were able to resolve this also by re-installing redshift driver of our gateway server. It seems that is the way to go around it.

regards

miguel