Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago

RESOLVED SharePoint gateway issue OData Version: 3 and 4, Error: The remote server returned an error

As of July 1, 2020 the dataflows that connected to on-prem SharePoint 2010 lists through a gateway were no longer working for our company.
 
I thought it might have been a username/password issue but that did not help.
 
The error that occurs everytime our scheduled refresh runs is:
 
An exception occurred: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed: 
OData Version: 3 and 4, Error: The remote server returned an error: (404) Not Found. (NOT FOUND)
OData Version: 4, Error: The remote server returned an error: (404) Not Found. (NOT FOUND)
OData Version: 3, Error: The remote server returned an error: (404) Not Found. (NOT FOUND) (Session ID: 6c8dbed0-ba7d-4c87-9c92-736bbd4d0193)
 
I updated the gateway software to the latest version and that still did not help!!
 
solution:
 
Finally, I decided to test a connection to SharePoint from Power BI desktop and it worked.  I noticed that the connection worked but looked a little different than the connection on Power BI Online when viewed using Advanced Editor
 
It looks like the initial connection in power query was somehow updated from version 14 to version 15:
 
Source = SharePoint.Tables("http://sharepointroot/mysubsite", [ApiVersion = 15])
 
After I changed the 15 back to 14 everything started working again.
 
If you are experiencing the same problem, double-check your ApiVersion and make sure it hasn't been updated.

7 Replies

  • v-alq-msft's avatar
    v-alq-msft
    Icon for Community Support rankCommunity Support

    Hi, Anonymous 

     

    I wonder which connector you are using to connect to sharepoint sites. Sharepoint is a cloud service which you don't need a gateway to connect to. The on-premises data gateway acts as a bridge. It provides quick and secure data transfer between on-premises data, which is data that isn't in the cloud, and several Microsoft cloud services. 

     

     

    I tested with 'sharepoint folder'

     

     

     

    It works properly. My [ApiVersion] is 15. If the issue still exist, you may create a support ticket here .

     

    Best Regards

    Allan

     

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

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi!

    Switching API to 14 helped with removing the OData errors.

    But now I have this error instead.. 

     

    What would the solution be for this? 

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi 

     

    I am getting the same error - is there any resolution ? My URL works fine if I click on it. I am trying to connect to a folder in Sharepoint to pick up a file 

     

    Details:Unexpected exception in query "<pi>Query</pi>", Message: <pi>DataSource.Error: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed: OData Version: 3 and 4, Error: The remote server returned an error: (404) Not Found. (Not Found) OData Version: 4, Error: The remote server returned an error: (404) Not Found. (Not Found) OData Version: 3, Error: The remote server returned an error: (404) Not Found. (Not Found)</pi>

     

    Thanks

     

     

  • Spanish

     

    Hola, tuve el mismo error, lo resolvi de la siguiente forma como una solucion temporal, no es una solucion tecnica:

     

    1- Descargue de la ruta sharepoint una copia del archivo a mi disco duro, y conecte el documento a Power BI de forma local.

    2- Una vez conectado el archivo de forma local, procedi a cambiar el origen de los datos desde Power Query pero esta vez pegando la ruta del archivo que esta en sharepoint, la cual estaba generando el problema con el conector de "Carpeta Sharepoint".

     

     

    y listo, cierro y actualizo y el archivo queda conectado al origen de datos desde sharepoint

  • There may be another problem related to authorization on a SharePoint folder or file.
    I had this problem when I changed the rights for the member group from RW to R. When I restored the rights to RW, this error disappeared.