We've got a few Direct Query reports pointing at a Redshift cluster. This has worked great the last few weeks but over the last two or three days, we're getting schema load errors when attempting to render these reports.
When we attempt to refresh the data, we're seeing that there's an issue loading the Redshift ODBC driver (see below).
@Microsoft - Is this a known issue? Is it possibly related to a recent PBI release?
At this point, we're dead in the water with these reports and really need this to be working again.
Here's the detailed error:
Something went wrong There was an error when processing the data in the dataset. Please try again later or contact support. If you contact support, please provide these details. Data source error: 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\analysisserver.backendapptype_App5741\analysisserver.backend.servicepackage.Code.2018.11.4.37\workloads\AS.2018.11.4.204\MDataEngine\ODBC Drivers\Simba Amazon Redshift ODBC Driver\AmazonRedshiftODBC_sb64.dll).. The exception was raised by the IDbCommand interface. Table: opp_dim_npi. Cluster URI: WABI-US-EAST2-redirect.analysis.windows.net Activity ID: 1111043c-4262-4aaa-a740-5b19114b17ba Request ID: c88b2953-366e-81db-61ce-35cedefa04ce Time: 2018-12-03 03:45:19Z
Same here 😞 Really hurting us in prodution. We use PowerBI Azure Dedicated Capacity. Works fine in App Workspaces without dedicated capacity.
We have the same problems with updating dataset when it is comming from Redshift.
Problem ocurrs only when datasets are stored on Premium Capacity instances.
I check you request id and found the trace log mentioned:
Processing for d736c535-0ea6-4671-b2ce-6718e5bb4d3d failed due to managed provider error Failed to save modifications to the server.
Processing for database d736c535-0ea6-4671-b2ce-6718e5bb4d3d with max parallelism 6 failed because of amo exception Microsoft.AnalysisServices.OperationException: Failed to save modifications to the server.
It seems like something wrong with with operation with save changes, maybe you can open a support ticket for this.
But: Direct Query doesn't save changes. The failed save operation must be in the PowerBI stack. I've tested this with a fresh and small PowerBI report using Redshift in Direct Query mode. Same error. This means to me that Redshift atm doesn't work at all when using dedicated capacity. This is really hurting anyone who made a decision to use PowerBI in production mode with Redshift as database. Of course I also opened a support ticket.
We have applications in production and paying customers. How is this happenning and why is nobody at Microsoft taking care of this?
This is just silly. We're paying for premium capacity and, as a result, we're dead in the water on this issue with little to no response from Microsoft support.
Can we please get some sort of official response from MS on this? Their service status page is reporting that all is good... 😞
Same here! Some acknowledgement of the issue and timeline to fix it would be great -- we are also dead in the water, with business processes depending on these reports!!
I've got confirmation that this a problem with the current premium/embedded release build. No ETA for a fix though... Will get an update later today (CET).
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!