Forum Discussion
DM_GWPipeline_Gateway_MashupDataAccessError On-Premises Data Gateway Error
Hello,
So I have a dataset published in the Service that has the following data sources:
- https://tenders.nsw.gov.au/
- https://www.tenders.act.gov.au/tender/search
- https://www.tenders.wa.gov.au/watenders/tender/search/tender-search.do
- a Microsoft Exchange inbox
In the desktop file, all privacy levels are set to Organizational. Everything refreshes fine.
But when published to the Service and connected to the On-Premises Gateway (Standard, March 2020 version), the refresh returns the following 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: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"An unknown error occurred when navigating to the web page."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"Web"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"https://www.tenders.act.gov.au/tender/search"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}},{"code":"Microsoft.Data.Mashup.ValueError.StatusCode","detail":{"type":1,"value":"-2146697205"}}],"exceptionCulprit":1}}} Table: ACT_UNSPSCReference.
Cluster URI: WABI-AUSTRALIA-EAST-A-PRIMARY-redirect.analysis.windows.net
Activity ID: 2b36d3b7-0e3b-409b-99a8-e8608e63df72
Request ID: 0ef64159-25bc-b3d8-2f28-3d990db753f4
Time: 2020-03-31 06:24:02Z
The "Table" that shows as the culprit changes everytime, so I'm pretty sure it's not specific to one table only.
The data sources are added in the gateway with an 'Anonymous' authentication and 'Organizational' privacy setting (except for the Exchange mailbox which does not need to be added to the gateway).
Another weird thing that has been boggling me is that I have a gateway installed in one laptop, which refreshes the dataset with no problems, but when the same gateway version is installed in another machine, it returns the error stated above. Unfortunately I cannot use the laptop in the production environment as it is a personal laptop, so I need to install a gateway in the production environment machine.
I have been working on this for weeks and I could not seem to make anything work. Would appreciate any insight anyone might have!
20 Replies
- GilbertQ
Super User
Hi there
If it was working fine on the laptop that might indicate to me that it could be a connectivity issue from where the gateway is now installed?
If you could see if it can access the same website where the gateway is installed? Hi Anonymous ，
Could you please complete the following steps first and check if it can solve the problem?
1. Uninstall the gateway which installed in production environment machine
2. Reinstall the latest version of the gateway and update the setting of Mashup engine by this link
In addition, as checked the posts from users who have encountered similar problems before, if both personal gateway and enterprise gateway running on the same machine at the same time, there seems to be a conflict. It is recommended to uninstall the one which is not currently using.
Best Regards
Rena
OBHelper II
This is to let everyone know that our issue stopped being an issue on September 1, 2020 when refreshes started working again without errors (almost a month after they first failed). However, if it helps anyone to troubleshoot in the future, we identified another workaround along the way.
- Our sources were SharePoint on-prem lists that were appended as part of the M query in Power BI.
- They were all in sub-sites of one parent site and there was one gateway connection to the parent site.
- After the report failed to refresh with Append, we tested that lists could still be refreshed individually (without appending) using the above gateway connection.
- The workaround, though, was to create a gateway connection per each sub-site/source (using the same account and password, so no change in SharePoint, only several new gateway connections created instead of one).
- Then each list was mapped to its own gateway connection and with that, the refresh of the report with appended lists worked - that was a more acceptable temp solution for us as it didn't require any changes inside the report.
Hi OB ,
It's glad to hear that the refresh start working. Thanks for your reply and sharing your solution. There are some threads about this type of problem which schedule refresh can't work properly due to the append query. There is no good solution yet. Your solution may help people who have similar problem. Could you please just mark your last post as Answered? It will help the others find your solution easily and fast. Thank you.
Best Regards
Rena
