Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago
Solved

On-Premise Data Gateway error for Web Data Source - underlying error: (404): File Not Found

I have a Power BI Desktop file published in the Power BI Service that uses 3 different data sources, however these all point to lists in the same SharePoint 2013 (on-premise) site. I have found that ...
Need Help
  • v-kelly-msft's avatar
    v-kelly-msft
    6 years ago

    Hi Anonymous ,

     

    Try to add the following query into query editor:

     

     let 
Source = Web.Contents("http://<ServerName>.com/<SitePath>/<SiteName>",[RelativePath = "/_vti_bin/owssvr.dll?XMLDATA=1&List={<ListID>}&View={<ViewID>}&RowLimit=0&RootFolder=%2f<SitePath>%2f<SiteName>%2fLists%2f<ListName>Selection={<ItemID>}-{<ItemID>}EditWebPage=Formatting=NonePreFormattedTextToColumns=TrueConsecutiveDelimitersAsOne=TrueSingleBlockTextImport=FalseDisableDateRecognition=FalseDisableRedirections=FalseSharePointApplication=http://<ServerName>.com/<SitePath>/<SiteName>/_vti_binSharePointListView={<ViewID>}SharePointListName={<ListID>}RootFolder=/<SitePath>/<SiteName>/Lists/<ListName>&IncludeVersions=TRUE"])
in
Source

     

     

    if it's okay,then publish the .pbix file to service,and then configure the data source to see whether there's an error.

     


    Best Regards,
    Kelly

     

     

v-kelly-msft's avatar
v-kelly-msft
Community Support
6 years ago

Hi Anonymous ，

The 400 ERROR means a bad http request. Please updata on-premise gateway to the lastest version. If you already have updated the gateway to the latest version, then you can refer to steps below for troubleshooting.

 

1. Check if the server is using a proxy and the proxy. Some proxies restrict traffic to only ports 80 and 443. By default, communication to Azure Service Bus will occur on ports other than 443.

2. You can force the gateway to communicate with Azure Service Bus using HTTPS instead of direct TCP. You will need to modify the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. Change the value from AutoDetect to Https. This file is located, by default, at C:\Program Files\On-premises data gateway.

3. Restart the gateway and check if the issue persists. 

  • To stop the service, run this command:

    ''' net stop PBIEgwService '''

  • To start the service, run this command:

    ''' net start PBIEgwService '''

4. You may export the data gateway log by selecting Diagnostics and then selecting the Export logs link near the bottom of the page. Reference: https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem-tshoot#tools-for-troubleshooting.

 

Hope this would help.

 

Best Regards,

Kelly

 

Anonymous's avatar
Anonymous
Not applicable
6 years ago

Hi v-kelly-msft 

 

Thanks for your reply, we have the latest version of the software and have completed the checks you suggested:

  1. Port 80 is being used.
  2. On this version of SharePoint, we don't use https. Is that an issue? Like I said I have successfully configured the other data sources which query this same site. 
  3. My colleague restarted the gateway and I am still seeing this error.
  4. We have exported the data gateway log, should I send this to you directly to help further? 

 

Many thanks,

Olivia

  • v-kelly-msft's avatar
    v-kelly-msft
    Community Support
    6 years ago

    Hi Anonymous ，

     

    If so ,pls try to shift to  HTTPS instead of direct TCP,then restart the gateway  and see if the error still occurs.

     

    Best Regards,

    Kelly

     

    • Anonymous's avatar
      Anonymous
      Not applicable
      6 years ago

      Hi v-kelly-msft 

       

      I have checked and HTTPS was already enabled. Is there anything else we can do?

       

      Thanks

      Olivia

      • v-kelly-msft's avatar
        v-kelly-msft
        Community Support
        6 years ago

        Hi Anonymous ，

         

        Try to use an empty .pbix file to connect with the following URL using a web connector(shown as below):

        http://<ServerName>.com/<SitePath>/<SiteName>/_vti_bin/owssvr.dll

        Don't write any parameters inside,then publish to service to check whether it can configure the  datasource from sharepoint.

        Sometimes it may happen when the gateway machine cant visit the datasource, using the above steps to rule out the factor.

         

        Best Regards,

        Kelly