The remote server returned an error: (500) Internal server error - when refreshing using JIRA C

[Anonymous]

Hi, 

Since last week (19th June) all my reports have been failing to refresh with an internal service error. I reveived an email saying it is a transient issue and to try again later, but after waiting over the weekend and this far into the week, I don't see it getting fixed. 

I am connected to JIRA data using the OData data connector with the AIO Power BI JIRA data connector

The Odata url connects to a number of tables in JIRA, which I then merge together using the query editor in PBI desktop. The queries seem to load fine when they are independent of each other. But when I merge them together I get the above error. 

Nothing has changed in the query since it last ran successfully. 

I have also tried to reduce the size of the data returned, with no luck. 

Has anyone else come across an issue like this? Would greatly appreciate any insight anyone could offer. 

Thanks, 

Lee

[Afreen_Ejyle]

@Anonymous did you ever figure this out? We are having the same issue. 

[v-xicai]

Hi @Anonymous ,

There are similar case1 and case2 you may refer to:

1 - Open the report(s) in PBI Desktop and clear the cache (file...options and settings... options)

2 - Refresh the data in the desktop and save.

3 - Open PBI Online and remove the associated dataset(s). Note - you'll need to remove the reports from any content packs before you can remove the reports and data from the online service. Also you might want to make a note of the (failed) refresh schedule you had before doing this so you can recreate it exactly.

4 - Hop back to PBI Desktop and publish the report from PBI Desktop to Online

5 - Hop back to PBI Online and set the refresh schedule back up

6 - Add the reports back into any apps or content packs.

Or you may try to upgrade the gateway to the latest version.

If you still have this issue for Power BI, you'd better create a support ticket in Power BI Support , Scroll down and click "CREATE SUPPORT TICKET", or go to Issue forum  to get further help.

Best Regards,

Amy 

Community Support Team _ Amy

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

@v-xicai  thanks for your reply. 

Unfortunately I already tried that! Once I clear the cache and try to refresh the data source, I get the same error as above.

[v-xicai]

Hi @Anonymous ,

If you still have this issue for Power BI, you'd better create a support ticket in Power BI Support , Scroll down and click "CREATE SUPPORT TICKET", or go to Issue forum  to get further help.

Best Regards,

Amy 

[GilbertQ]

Hi there

You could look at increasing the timeout on the data source?

Also if you could ensure that your gateway is running the latest version of the gateway?

[Anonymous]

@GilbertQ thanks for your reply. 

I had a look, and there doesn;t seem to be the option to increase timeout when connected to an OData feed, even in the advanced editor. Unless I am missing something?

the source is cloud based and so doesn't use a gateway. 

[todfox1]

@Anonymous did you ever figure this out? We are having the same issue. 

[eldie]

Did you find a solution to this problem? Facing the same issue currently