Thanks for sharing. The extreme lack of response to tickets and lack of any public messaging about the problem is a huge concern.
This appears to be fixed for us, since ~11:00 p.m. last night (Pacific). We've had 9 consecutive successful (hourly) refreshes since then.
Our dataset is in Premium capacity and its data source is Redshift. But our situation might be a bit different, in that our dataset is in Import mode, not Direct Query.
This seems to be fixed for us, too. However no one from Microsoft ever told us that it was fixed or told us to try again. Thanks to others here reporting success, I manually refreshed datasets and we re-embedded our Direct Query report and it is working as of right now. I hope others have success, too.
We ran into this issue again about an hour ago. Appears to be working now but we're skeptical that this is really fixed.
Can we please get some sort of response from @ms on this? If it's still in progress, let us know and we can at least set expectations with our users.
Getting this issue now for import mode models in in both
Credentials need to be entered now after this refresh was working earlier.
When I attempt to enter credentials, I get this error.
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.192_1912151804\ODBC Drivers\RS\AmazonRedshiftODBC_sb64.dll)
It’s time for another PBI Community recap!
Visit our Community Blog for articles, guides, and information created by fellow community members.
Need help with the Power BI Community? Our 'Using the Community' support articles are a great place to start.
Looking for inspiration on how to present your data? Need instructional videos? Check out our Galleries!