topic Re: Dataflow refresh issue with Odata feed connection in Developer

Dataflow refresh issue with Odata feed connection

Banka_Venkates — Mon, 22 Jul 2024 17:48:38 GMT

Power BI Dataflow refresh is continously failing with the below error.

We are taking data from Jira or JSM application through odata connection to the dataflow

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. ()

Does anyone have any idea on how to resolve the issue?

Many thanks,

Venkatesh

Re: Dataflow refresh issue with Odata feed connection

Anonymous — Tue, 23 Jul 2024 05:35:20 GMT

Hi @Banka_Venkates ,

The 500 Internal Server Error typically indicates an issue on the server side, often related to server-side problems or configuration issues. Could you please check and confirm the following information?

Verify that the OData URL being used in the connection is correct.
Ensure that the credentials and authentication method used to access the OData feed are correct and have sufficient permissions.
Confirm that the server hosting the OData service is up and running.
If you have access to server logs, please review them for any relevant errors or issues.
Test if the data can be successfully loaded from the Jira or JSM application through the OData connection in Power BI Desktop.
Was the connection working previously, or is this a new issue?

Best Regards

Re: Dataflow refresh issue with Odata feed connection

Banka_Venkates — Tue, 23 Jul 2024 10:10:25 GMT

Thanks for the information @Anonymous.

Verified the Odata feed URL and it looks like the power bi connector for jira plugIn license has expired. So, We could not refresh the data in the Power BI Desktop.

Error Message: Power BI Connector for Jira license has expired. Please contact your Jira Administrator.

Best Regards,

Venkatesh