Forum Discussion
SharePoint: Request failed: Unable to connect to the remote server
I have a Dashboard with 2 DataSource 1. SQL Server and Sharepoint Online (List or Folder or Both)
Dashboard refreshes in Power BI Desktop but fails in BI Service intermittently.
Whenever it fails, I get the error "SharePoint: Request failed: Unable to connect to the remote server"
{"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":"<ccon>SharePoint: Request failed: Unable to connect to the remote server</ccon>"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"SharePoint"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"<ccon>%SharepointLink%</ccon>"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: %Table Name%
Table name keeps on changing pointing to different tables. The issue started after 20th June and it was working for 1+ years.
Currently, i see other dashboards are getting impacted as well. There are merge in the table and that are needed so
Steps Taken:
1. Cleared all Global connections in the file and logged in with credentials in the Power BI desktop
2. Logged in with credentials in BI Services.
3. Tried changing the direct SQL connection through dataflow, same issue.
4. Tried with different power BI version released after April 2023, same issue
5. Changed the Large data format settings to on as well as query cache, Same issue
Please help
4 Replies
- lbendlin
Super User
You can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues . If you have a Pro license you can consider raising a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Hi we are facing the exact same behavior. A dataset using both sharepoint + on prem datasource was working fine. Since 3 days, it stoppped working without any action on our side.
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":"SharePoint: Request failed: The remote name could not be resolved: 'XXX.sharepoint.com'"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"SharePoint"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"XX"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: XX (Sharepoint).
Cluster URI: WABI-EUROPE-NORTH-B-redirect.analysis.windows.net
Time: 2023-07-27 07:59:30Zregards.
I am having the same issue since Aug 30th, I raised a ticket with Microsoft. They did a discovery call but no solution yet
{"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":"SharePoint: Request failed: Unable to connect to the remote server"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"SharePoint"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail Pessoal, alguém conseguiu resolver? Me encontro com o mesmo problema em Janeiro-2024.
