Forum Discussion

vcmoffatt's avatar
vcmoffatt
Frequent Visitor
9 years ago

DataSource.NotFound: OData: Request failed (404): The remote server returned an error

I have a few reports where I have hooked into Microsoft Dynamics CRM 2016 and all were working well. But now gradually for no apparent reason on various different pbix files the data source appears t...
vcmoffatt's avatar
vcmoffatt
Frequent Visitor
9 years ago

Hi,

 

Yes I am able to connect to the content pack.

 

I have now go another issue, I can't even pull anything from MS Dynamics 365 - I get the following error now:

 

Details: "OData: The given URL neither points to an OData service or a feed: 'https://login.microsoftonline.com/dbb06ee2-1005-4b2e-a774-132be0888ef8/wsfed?wa=wsignin1.0&wtrealm=https://xxx.api.crm4.dynamics.com/&wctx=pr=wsfederation&rm=https%253a%252f%252fxxx.api.crm4.dynamics.com%252f&ry=https%253a%252f%252fxxx.api.crm4.dynamics.com%252fXRMServices%252f2011%252fOrganizationData.svc&wct=2016-12-08T15:18:03Z&wreply=https://cloudredirector.crm4.dynamics.com:443/G/AuthRedirect/Index.aspx?RedirectTo=https%253a%252f%252fxxx.api.crm4.dynamics.com%252fXRMServices%252f2011%252fOrganizationData.svc&Popupui=1'."

 

Any ideas on this?

 

thanks in advance

Victoria

vcmoffatt's avatar
vcmoffatt
Frequent Visitor
9 years ago

Ignore, the last post, I've realised what the problem was, it was to do with my credentials.

  • Anonymous's avatar
    Anonymous
    Not applicable
    9 years ago

    Hi vcmoffatt,

    It seems that you have resolved this issue. You can accept helpful replies as solution, that way, other community members would benefit from your solution.

    Thanks,
    Lydia Zhang

    • vcmoffatt's avatar
      vcmoffatt
      Frequent Visitor
      9 years ago

      Hi, no i didn't solve the original issue. I solved the issue from last thursday but not what I originally posted about.

      • BenHoward's avatar
        BenHoward
        Icon for Helper I rankHelper I
        9 years ago

        I found this error both in Excel and PowerBI Desktop.  The issue was too many columns, and removing some of them in PQ immediately after connecting to the source resolved the issue in both products.  For me it was failing in Project Server 2016 (PWA) on premise application when connecting to http://<site>/pwa/_api/ProjectData