Within Power BI (On cloud) console, the datasets screen is showng errors in form of alert icon, in detail the error for all of them is :
Something went wrong
Unable to connect to the data source undefined.
Please try again later or contact support. If you contact support, please provide these details.
Underlying error code: -2147467259 Table: <TABLE_NAME>.
Underlying error message: AnalysisServices: The following system error occurred:
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.DataSourceKind: AnalysisServices
Microsoft.Data.Mashup.ValueError.DataSourcePath: <path1>;<path2>
Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error
Cluster URI: WABI-SOUTH-CENTRAL-US-redirect.analysis.windows.net
Activity ID: 259c4fc7-dde9-449b-b108-9498b001ea25
Request ID: 56d4ee25-b539-4c05-8cd4-24b894507475
Time: 2019-06-13 12:12:51Z
I already reviewed gateway/ Analysis services but seems to be OK, Any idea what additional to review?
You may check the different privacy level settings in Power BI Desktop and Power BI Service. Make sure you have the same privacy level security.
Check Power BI gateway logs. For example, I received the same error message. Log information showed connectivity issue to SQL. I checked the server, and named pipes was disabled in client protocols. Since the report data source was configured by server name, connectivity could not work. Enabling it resolved the issue.
Related
im getting a error to refresh mi report in Power BI Service. Currently I can refresh the report locally however when I publish the report and then want to sync it to a gateway I get the following error:
I have this configuration in the new data source:
Finally i have this configuration in ODBC ( 64x):
Sometimes i get error of credentials but its impossible because y refresh the data with these credentials locally.
Thanks!
I try using different gateways, changue the configuration of the ODBC and Power BI Report. I have synchronized another report with the same gateway and it works correctly. Now when I try to link a second report to this same gateway I get the error.
My problem is very easy: I'm retrieving all stocks about lithium on the ASX market from this web page.
I created a Power BI dashboard that you can visualize here.
As the source is Web I would like to refresh it every day using the Gateway connection, so I have successfully installed it on my computer that I turn on every day:
The problem is that instead of a successful daily refresh I have a daily error:
Failed to test the connection to your data source. Please retry your credentials.
Some credentials aren't validated as they are set to skip test connection.
If I enter in the Edit credentials I see the error:
Failed to update data source credentials: The credentials provided for the Web source are invalid. (Source at https://www.marketindex.com.au/commodities/lithium.)Show details
This because I'm using Authentication method: Anonymous and Privacy level setting for this data source: Public. But this is exactly what I'm using on Power BI desktop and it's working!
What am I doing wrong here?
Why the same connection is working fine on Power BI Desktop but not the same dashboard uploaded online?
EDIT: the On-premises data gateway looks installed without problems
It seems like the issues you're experiencing may be caused by the link you're using (https://www.marketindex.com.au/commodities/lithium), although I'm not sure exactly why.
For example, as has been mentioned in the Do I Need a Gateway for Web post, one can use Web.Contents instead of Web.BrowserContents in the raw M code in the Power Query Editor to avoid using a gateway. However, when I test this implementation using the link that you provide, I get an error when refreshing from Power BI online.
If I test this implementation using an HTML table from the https://tradingeconomics.com/commodity/lithium website, though, and set the data source credentials as follows, then I am able to successfully refresh the dataset from Power BI online.
I tested this with another HTML table from a random webpage and an online refresh worked as well. So it seems like there is something odd about how Power BI online interacts with the Market Index website and this is causing your issue. Potentially because of some authentication configuration on the Market Index side of things? I'm not able to help with looking further into why this is occurring, though.
Would you be able to use a different website with similar information as a data source for your report? If so, you could avoid the issues you're experiencing and avoid using a gateway in general if you wanted.
If you go this route, it seems like using the included "Scheduled refresh" setup in Power BI online works, but I will include the Power Automate scheduled refresh setup below in case this is desired instead.
Power Automate Scheduled Refresh
One can use Power Automate to "schedule" dataset refreshes instead of the included "Scheduled refresh" functionality in Power BI online. The steps are a little too long to include here, but the Refresh your Power BI dataset using Microsoft Flow article outlines the process on setting this up. There are various triggers that you can use to trigger your flow. The linked article uses one that triggers based on a SharePoint action, but there is a Recurrence trigger that can be used to trigger your flow at regular intervals/times.
Just set up your flow, make sure that it is "turned on", and your dataset will refresh at regular intervals from the cloud.
I have made a Power BI Dashboard with Analysis Services (Live Connection). I have full access to the database and in Power Bi Desktop everything works (all data is visible and updated).
Then, when I publish the dashboard, and go to app.powerbi.com to open the DB, it gives me the error message that it cannot access the data source. "This report could not access its data source. please contact , the author, to have it fixed." However, the gateway is set correctly and also connected to the corresponding dataset. I've already delete and re-create the role in the database. What is noticeable is that the update date right after the publishing says: 1.1.53, 00:53:28. After the first gateway update it shows the correct date and time. Can anyone help me to fix the problem? Thank you very much!
You need to assign all of the end users read/write roles on the Tabular model.
I am trying to refresh the power bi report from power bi service by changing the gate way. i was hitting the below error. The source file is Access DB file.
Cannot connect to the mashup data source. See error details for more information.
Please try again later or contact support. If you contact support, please provide these details.
Underlying error code-2147467259 Table: tbl_ManagerPOC.
Underlying error messageUnspecified error
DM_ErrorDetailNameCode_UnderlyingHResult-2147467259
Microsoft.Data.Mashup.ValueError.ReasonDataFormat.Error
Cluster URIWABI-US-NORTH-CENTRAL-redirect.analysis.windows.net
Activity ID643f0e00-2c0a-4f45-8fb4-2043dc59d3eb
Request IDf615a46a-beac-4036-8d62-d6e56b1add08
Time2018-12-20 16:42:30Z
I have one Tabular SSAS project & I have deployed it on SQL Server Analysis Service 2012.
Then I have created a BISM connection to that deployed project as in following way.
Then I have created one PowerPivot excel report out of that BISM workbook using its connection string & it is working correctly in Excel.
But when I upload it to the SharePoint, it give me following error while refreshing the Data from BISM workbook.
this error is observed only when I open it on browser i.e. Excel Web Access.
but the same error is not observed when I refresh the report in Microsoft Excel 2013.
why is it giving error on only SharePoint i.e. Excel Services. due to this I am not able to change Slicer's either.
One of the solution I found was to use some Hot Fix of SQL Server. but I haven't tried this. Plz refer the below link Hot Fix for SQl Service Pack 1 Update
Please help!
Thanks in advance.
This refresh should be possible, assuming permissions are set up correctly. You should post ULS logs for the time period of the refresh.
Does this same thing happen if you do a scheduled refresh (and choose refresh now)?