none
I'm getting DataSource.NotFound: OData: Request failed (404) error when open connection RRS feed

  • Question

  • Hi,

    I have a simple OData service running in a server. When I try to call him in a browser all works fine. But in Excel Power Query, after the user authentication step, I get this error in Query editor

    DataSource.NotFound: OData: Request failed (404): The remote server returned an error: (404) Not Found.
    Details:
        http://<URL>/GIPJAM/$metadata

    The service is configured in a server and he his public. The URL (working in browser) http://<URL>:91/GIPJAM/

    This may be a port (91) problem? My application runs in port 80. This 91 port is to guarantee that the server is public. For exemple, if I run in my home network, using the name of the machine in the URL (like; http://quiron.blabla.net/GIPJAM/) all works in browser and in Excel PQ.

    I've made every test I can remember but i'm newbie in OData services and server, IIS and network configurations. 

    Anyone can help me?

    Regards,

    Filipe Almeida

    EDIT: I have this workaround implemented: https://social.technet.microsoft.com/Forums/en-US/dc0ca6ff-6583-4373-a31f-acb95e8046ef/connecting-to-odata-feed-using-powerquery-216-results-in-404-error?forum=powerquery

    I'm using Power Query 2.16 and Excel 2013, with a Odata V4 Service in Web .NET API 2.2

    • Edited by Milheiros Thursday, January 15, 2015 2:42 PM
    Thursday, January 15, 2015 2:41 PM

Answers

  • It looks like your service probably supports V3 and V4 or you'd be getting a different error message. What I suspect is happening is that the service doesn't know that it's listening on port 91 and so it's returning URLs embedded in your result -- either the xml:base on an XML body or the metadata link in a JSON body -- which don't reflect the port number. You can easily verify this by using Fiddler to look at the results. If any of them have an URL that's missing the ":91", that's an indication that you'll need to fix this on the service side.
    Thursday, January 15, 2015 3:51 PM

All replies

  • Unfortunately Power Query doesn't support OData v4.0 yet. It is planned to be supported this year. Read more at the bottom of this post.

    Thursday, January 15, 2015 3:31 PM
  • It looks like your service probably supports V3 and V4 or you'd be getting a different error message. What I suspect is happening is that the service doesn't know that it's listening on port 91 and so it's returning URLs embedded in your result -- either the xml:base on an XML body or the metadata link in a JSON body -- which don't reflect the port number. You can easily verify this by using Fiddler to look at the results. If any of them have an URL that's missing the ":91", that's an indication that you'll need to fix this on the service side.
    Thursday, January 15, 2015 3:51 PM
  • Hi Gil,

    My mistake. My service is using OData v3.0. That's why I can feed my PQ when connecting with the private URL of the same server or calling the service in that same machine. 

    My problem is with the public URL.

    Thanks,

    Filipe

    Thursday, January 15, 2015 4:52 PM
  • Filipe,

    Is this still an issue?

    Thanks!


    Ed Price, Azure & Power BI Customer Program Manager (Blog, Small Basic, Wiki Ninjas, Wiki)

    Answer an interesting question? Create a wiki article about it!

    Monday, February 9, 2015 8:58 PM
    Owner
  • Hi Ed,

    No, is not. Thanks.

    Filipe

    Tuesday, March 17, 2015 9:24 AM