SSAS Connection String for Tabular From Desktop is Formatted Incorrectly

[Anonymous]

Power BI Desktop version: Version: 2.71.5523.941 64-bit (July 2019)

Tabular connections (live connection) are now being created as Server\\tabular in the desktop when publishing a report.

When trying to use the dataset from the report, we are now getting a message "There is no gateway to access the data source XXX"

The gateway is configured correctly with Server\tabular and the test connection continues to work as expected. We also tried adding the Server\\Tabular but then it wouldn't connect - just to prove that the connection string should be this way.

Is this is known bug? Is there a fix or workarond?  Thanks!

[dax]

Hi dataguy,

When you use premise datasource, you need to set gatewy way for this. If you didn't set gateway for this datasource, you might will get below error

Then when you click to "add to gateway", it will show like below(it will automatically change to server\instance)

Then you will get result like below

By thw way, to make refresh or get data correctly, you also need to make sure your effective name's mapping correctly

 You could refer to Manage your data source - Analysis Services for details.

Best Regards,
Zoe Zhi

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

[Anonymous]

We have the definition in the gateway just fine. This has worked for us for over a year. 

Recently new published reports cannot access the dataset.

If you go into the Settings for the Dataset, it shows the list of possible Gateways.

Then when you expand one to see why it is not working, it shows - AnalyServices{"server":"myserver\\tabular","database":"MyDatabase"}  Add to Gateway

So as you can see it thinks the connection string needs a \\ which is incorrect. The connection string exists on a gateway and has for over a year as myserver\tabular and has been working.

So any more thoughts?

[dax · Accepted solution]

Hi dataguy

As you could see above, in my image, the datasource information will be server\\instance, but this will show correctly in gateway

So I think your problem should be that not mapping to correct gateway.If you have same datasource connection string which exist in gateway, you could map this to corresponding datasource in gateway, like my above image(I map this to tabular). You could try this to see whether it work or not.

Best Regards,
Zoe Zhi

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

[Anonymous]

Thank you!