Need help on Odata feed

[Ajay_nyc]

When loading ODATA via Powerbi Power Query, via DataSource.Error: OData: Request failed: The remote server returned an error: (500) Internal Server Error. (An error has occurred.)

But if I try to load the same ODATA using excel Power Query, it works fine, can someone help me here, I am not able to understand the issue. Why is power query failing in PowerBI.

[rubayatyasmin]

Hi, @Ajay_nyc 

The error message you're receiving is a 500 Internal Server Error, which is a general HTTP status code meaning that something has gone wrong on the server, but the server could not be more specific on what the exact problem is.

Here are some steps that could potentially resolve your issue:

1. Server Side Issue: The server returning a 500 Internal Server Error can be the cause of the problem and not your PowerBI setup. It is possible that the server handles the requests differently based on the client (Excel vs PowerBI in this case) and that leads to the error. So, the first step would be to check with the administrator of the server or the provider of the OData feed and ask them to look into the server logs for more specific error messages.

2. Re-Enter Credentials: If the issue is not with the server, try re-entering your credentials. If it's a credential issue and they got corrupted somehow or not properly stored, it can cause a 500 Internal Server Error. So, remove the data source in PowerBI and add it again.

3. Privacy Level Settings: Privacy level settings in PowerBI may cause a similar issue. In Power Query within PowerBI, under 'File' -> 'Options and settings' -> 'Privacy', set the privacy level to Ignore the Privacy Levels and potentially improve performance.

4. Timeouts: Sometimes, the server may take too long to respond, and PowerBI's default timeout setting may be less than what's required. Increasing the timeout can be helpful in this scenario. You can modify the timeout duration under 'Options' -> 'Query Options' -> 'Diagnostics' -> Enable Custom Diagnostic Settings -> Increase the HTTP timeout in seconds.

5. Update PowerBI: Make sure your PowerBI desktop is updated to the latest version. Updating can fix potential bugs or compatibility issues that may be causing the error.