Forum Discussion
Error about Data source credeintials
From Sydney/Australia,
Experiencing the same issue, only way to get around this is to open the .pbix file, hit refresh and then publish to workspace.
Failed to update data source credentials: 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, D:\SvcFab\_App\ASAzureApp_App1\DataMovementMetadataServicePackage.DataMovementMetadataService.Code.Main_13.0.11747.237_1912180731\ODBC Drivers\RS\AmazonRedshiftODBC_sb64.dll).
Activity ID: a360c5d6-71b2-48c5-97e7-d9f7d76e99e8
Request ID: 139f80f6-04e0-7d7f-43c7-083ca3c08272
Status code: 400
Time: Fri Dec 20 2019 09:53:01 GMT+1100 (Australian Eastern Daylight Time)
Service version: 13.0.11747.247
Client version: 1912.2.028
Cluster URI: https://wabi-south-east-asia-redirect.analysis.windows.net/
Hi Anonymous , AS_0001 , gbc_batman , melo-loadsmart , Anonymous , Anonymous
Unfortunately, Amazon Redshift connector having issues with manual fresh and updating credentials currently. As a workaround, we can install Gateway and configure their Redshift data source to go through it.
Hi Anonymous , Sorry for that, but we cannot configure a on premise gateway on an Apple machine
Apology again for the inconvenience caused by this issue.
Best regards,
- AS_00016 years agoHelper I
Thank you for your workaround.
Unfortunately our environment cannot set onpremise data gateway. Is there any workaround? If we configure ODBC in AWS, does it work? I hope Microsoft resolve this issue as soon as possible.
It was really heavy workload to download many PBIX files and refresh and publish it every day.
- gbc_batman6 years agoFrequent Visitor
Today it started working again, the credentials error was fixed. It looks like it is an itermittent issue.
Thanks
- AS_00016 years agoHelper I
Microsoft support desk sent the email to us that the issue was resolved thanks to update Dec.18 and 19. We confirmed the issue was resolved.
- muneern5 years agoFrequent VisitorThe forum post indicates this problem was resolved in December last year, but this error started occurring for me early this morning. There were no other changes to the Data Gateway server that I am aware of.
Please respond if you have any suggestions or are experiencing the same.