Forum Discussion

tmcdevitt's avatar
tmcdevitt
Advocate II
7 years ago

Direct Query connectivity issues with Redshift in the last few days; Production reports won't load

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 ...
Need Help
Anonymous's avatar
Anonymous
Not applicable
7 years ago

Hi tmcdevitt,

 

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.

 

Regards,
Xiaoxin Sheng

  • Anonymous's avatar
    Anonymous
    Not applicable
    7 years ago

    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?