Dynamics Community Forum Thread Details

Recent issues with GP OData Services (previously configured companies in same instance work, new ones don't)

So we have been meticulously using PowerBI to connect to the Odata services published by Dynamics GP (2018 R2, fully patched).

PowerBI is also fully updated on the desktop as a client.

We made a new company a month ago, however upon trying to connect to any of its Odata tables/views, we get the following error:

Unable to Connect

We have encountered an error while trying to connect.

Details: "Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed:
OData Version: 3 and 4, Error: The remote server returned an error: (500) Internal Server Error.
OData Version: 4, Error: The remote server returned an error: (500) Internal Server Error.
OData Version: 3, Error: The remote server returned an error: (500) Internal Server Error."

Google searches indicated a lot of results related to sharepoint but nothing related to GP. And the Odata tools in GP don't really give any confg abilities outside of publishing views, etc. There's only one server hosting this GP instance, there's no other gateway or anything. One company works but this one gives this error.

Thanks in advance.

Categories:

Reporting and BI

A lot of the time, the 500 Internal Server Errors in regards to OData can be seen when attempting to load a large amount of data, and even when limiting the search results via OData flags, the error will still show, though this was supposed to be fixed in Dynamics GP 2018 / OData:

community.dynamics.com/.../getting-started-with-power-bi-and-odata-in-dynamics-gp

docs.microsoft.com/.../supporting-odata-query-options

You mentioned Power BI, do you get this same error for this new company when attempting to access/view OData in Excel as well?

I have seen a couple cases with these errors for OData related to a permissions issue, and running a Fiddler trace helped identify that, which you can do via these steps:

a. On the server where you’re working with OData and Excel, browse to this URL and download Fiddler: http://fiddler2.com/home

b. In Start > All Programs, find Fiddler and launch it.

c. In Fiddler, click on File and remove the check-mark next to ‘Capture Traffic’.

d. Click on Tools > Fiddler Options…, then click on the ‘HTTPS’ tab. Here, make sure that both options for HTTPS are marked, and click OK.

e. With Excel open with a blank workbook, click on File and put a check-mark next to ‘Capture Traffic’ again in Fiddler.

f. In Excel, click on ‘Get Data’ > ‘From Other Sources’ > ‘From OData Feed’, enter the OData feed URL and credentials as needed, up to where the 500/Internal Server Error shows. Once the error shows, remove the check-mark in Fiddler from Capture Traffic.

g. Click on File > Save > All Sessions, and save the Fiddler log so you can look through it, specifically the https calls being sent for OData which should capture the 500 error message as well and give information on what is causing it, be it user credentials or something else.

I'd maybe start with that and see if that shows you anything. It is odd that OData works for the other GP companies and not this one new company.

Thanks

Quick Links

Leaderboard