Invalid mashup connection string

[sabake]

Hello

After uploading new version of the model with RangeStart and RangeEnd parameters set to enable incremental loading data update in PowerBI Service fails instantly with:

Something went wrong
An error occurred while processing the data in the dataset.
Please try again later, or contact support for the following details.
Data source error: {"error": {"code": "DM_GWPipeline_Gateway_InvalidMashupConnectionString", "pbi.error": {"code": "DM_GWPipeline_Gateway_InvalidMashupConnectionString", "parameters": {}, "exception": "exception": 1}}}
Cluster URI: WABI-WEST-EUROPE-B-PRIMARY-redirect.analysis.windows.net
Activity ID: 099f5a37-7f6d-45eb-8e62-3c471f541172
Query ID: 04dae897-de4f-54a2-b358-686d1c18e8ea
Time: 2020-07-01 20: 09: 49Z

From forum this exact wording seems to be the first such reported case..

[sabake]

a late notice, but the issue was resolved with august update of powerbi. Unfortunately all models had to be re-created from scratch to enable incremental loading.

[shachar]

Hi,I am facing same issue.I tried restarting the gateway.Could you please let me know the solution for this?

[anthonyloh]

I started getting this error right after we updated our On Premsis gateway to the latest version. Any one else seeing the same thing?

[v-alq-msft]

Hi, @sabake 

I wonder what data sources you are conncectint to. Based on error message, it seems like there are something wrong with your datasource connection and parameters.

I'd like to suggest you to refer to the following links. If it still doesn't work, you may open a support ticket here .

Using the Power BI Service Parameters to change connection strings 

Troubleshooting refresh scenarios 

Troubleshoot gateways - Power BI 

Best Regards

Allan

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[sabake]

Opened the ticket a none of the pages describe the issue encountered.

Interesting is, that dataset management page does not detect the rangestart and rangeend parameters, but the parameters are visible in the data model..

[sabake]

Case is still open, but for others who have encountered similar - PowerBI Desktop and PowerBI Service do data queries a bit differently, so successful data load in desktop do not mean successful data load in the service. Diligently following that native query is shown (and makes sense) in the desktop for all source (loaded from external DB) tables is the way to avoid surprises from the service.

I still have issues on service data load, but after ensuring all source db queries are correct the mashup connection string dissapeared - was replaces with various timeout errors. As I'm actually loading fact and dimension tables transformed from the source tables then issue is probably with the transformation methods.

[GilbertQ]

Hi there

Can you confirm you have the latest version of the Power BI Gateway installed?

[sabake]

Yes, update was installed couple of days ago. 

[sabake]

Just for case the query widely used in the model is:

Source = Value.NativeQuery(PostgreSQL.Database("xxxx.rds.amazonaws.com", "xxx", [CommandTimeout=#duration(0, 4, 0, 0), ConnectionTimeout=#duration(0,4,0,0)]), "select * from xx.xxx", null, [EnableFolding=true]),
#"Filtered rows" = Table.SelectRows(Source, each [created] > #datetime(2019, 6, 1, 0, 0, 0) and [created] >= RangeStart and [created] < RangeEnd),

...

This works as intended in the desktop and I can upload model into Power BI service without errors.

[Anonymous]

Also, my issue is only with a PostGres database. Just a hint that this may be part of the issue.