Forum Discussion
on-premise Error for Redshift sources
Hello everyone,
I have 2 VMs with on-premises clustered in Azure: these two gateways allow me to retrieve several data sources (SQL/Redshift/PostgreSQL).
Since last week I can't retrieve Redshift sources: both gateways are partially online with a DLL error on GW number 2.
I've updated, deleted and reinstalled the on-premise, tried to deactivate GW number 2 from the cluster but to no avail: the DLL indicated is indeed present in the right place on the VM.
Azure Cloud 2: Received error payload from gateway service with ID 344420: ODBC: <ccon>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 New, C:\Program Files\On-premises data gateway\m\ODBC Drivers\New\AmazonRedshift\AmazonRedshiftODBC_sb64.dll).</ccon>.
The last solution would be to remove the GWs and reinstall an older version of on-premise, or to completely reinstall the VMs, but cel ame seems extreme.
If you have any ideas, thank you.
In the end, I uninstalled the on-premise on the GW 2, which was no longer in the original cluster, and installed an older version of on-premise: I can now create sources to AWS again without error.
From what I understand, the cluster kept the ODBC error even if I installed an old version of on-premise: I had to create a new gateway for the BI services portal with the old on-premise version for it to work again.
3 Replies
I just removed my second VM from my cluster and installed a new on-premise version on it. I can see my new gateway outside of my cluster (completely new for Power BI Services).
I created a new Redshift data source on it (the one that works perfectly from my VM), and I'm still getting the same error message.
It's driving me crazy.
In the end, I uninstalled the on-premise on the GW 2, which was no longer in the original cluster, and installed an older version of on-premise: I can now create sources to AWS again without error.
From what I understand, the cluster kept the ODBC error even if I installed an old version of on-premise: I had to create a new gateway for the BI services portal with the old on-premise version for it to work again.
Hi, Sebastien_G
Thank you for sharing your solution. If you have any new questions in the future, you can always ask them in the forum.
Best Regards
Jianpeng Li
