Internal Server error (500) contact supplier with itgenclr008 and 382152

Questions
, , ,
1

So I have a gen 1 data flow that I run on the cloud environment of Power BI and I keep on getting this error everytime I try to refresh the dataflow. Any idea on what could be wrong ?

OData Version: 3
Error:
The remote server returned an error: (500)
Internal Server Error.
(An internal error of type ‘382152’ occurred. Please contact your supplier. (itgenclr008 ) "

When I tried to add a new table to the dataflow from OData, at first it gave the same error of 500. However, on the second try it did log me in and i was able to see the tables. Nonetheless, the refresh is still failing, how can I fix this?

2

Please verify whether this is a duplicate of Itgenclr008 error on download into Power BI, which should alrady have been resolved.

If not, please add a (anonymized) screenshot of the request details in Invantive Bridge Online Monitoring as described in More insight with new Bridge Online Monitoring?

Details can be found by clicking on the download request which represents the issue discussed in this topic.

Please leave at least the following data visible:

  • the title bar with the request ID,
  • the status code, network size and times in the left column,
  • the error code and error message at the very bottom of the left column,
  • the entire right column.
4

Sorry for the inconvenience, but it seems like the dataflow wont refresh with a new error of “An existing connection was forcibly closed by the remote host”.

Attached are screenshots for extra information.

image
image1748×775 54.2 KB

image
image1016×450 24.7 KB

5

The screenshots are from the /setup page, which isn’t an actual OData download. Can you share the request that is failing?

The fields “Message Code” and “Exception” should contain a text when the failing request is selected.

6

I tried to get the error registered via the monitoring of invantive.

However, I don’t get any logs when I try to refresh the data using the Gen 1 data flow of PowerBI, but I do get the error as follow within powerBI:

"Requested on,Dataflow name,Dataflow refresh status,Table name,Partition name,Refresh status,Start time,End time,Duration,Rows processed,Bytes processed (KB),Max commit (KB),Processor Time,Wait time,Compute engine,Error,
2024-08-08 09:39:37,Autotask,Failed,AT Companies,Part001,Completed,2024-08-08 09:39:37,2024-08-08 09:39:45,00:00:07.9220,NA,60,74108,00:00:02.6090,00:00:00.6080,Not used,NA
2024-08-08 09:39:37,Autotask,Failed,AT Contracts,Part001,Completed,2024-08-08 09:39:37,2024-08-08 09:39:46,00:00:08.4220,NA,395,75124,00:00:02.9060,00:00:00.5420,Not used,NA
2024-08-08 09:39:37,Autotask,Failed,AT Resources,Part001,Completed,2024-08-08 09:39:37,2024-08-08 09:39:45,00:00:08.3590,NA,16,79404,00:00:02.2970,00:00:00.0260,Not used,NA
2024-08-08 09:39:37,Autotask,Failed,AT Services,Part001,Completed,2024-08-08 09:39:37,2024-08-08 09:39:45,00:00:08.2810,NA,97,78044,00:00:02.4840,00:00:00.1040,Not used,NA
2024-08-08 09:39:37,Autotask,Failed,AT Tasks,Part001,Completed,2024-08-08 09:39:37,2024-08-08 09:39:47,00:00:09.9530,NA,1151,75308,00:00:03.5630,00:00:00.3390,Not used,NA
2024-08-08 09:39:37,Autotask,Failed,AT TicketCategories,Part001,Completed,2024-08-08 09:39:37,2024-08-08 09:39:46,00:00:08.8590,NA,1,76244,00:00:02.2970,00:00:00.3390,Not used,NA
2024-08-08 09:39:37,Autotask,Failed,AT TimeEntries,NA,Failed,2024-08-08 09:39:37,2024-08-08 09:44:54,00:05:17.1070,NA,NA,NA,NA,NA,NA,Error: The current operation was canceled because one or more operations failed… Request ID: 79d66fb6-27c3-9d1b-0f74-762e74e95a62.
2024-08-08 09:39:37,Autotask,Failed,AT Tickets,NA,Failed,2024-08-08 09:39:37,2024-08-08 09:44:53,00:05:16.0430,NA,NA,NA,NA,NA,NA,Error: Data Source Error : DataSource.Error: OData: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. DataSourceKind = OData DataSourcePath = RootActivityId = 9d86c812-2161-402e-832a-6da4d5508a59.Param1 = DataSource.Error: OData: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. DataSourceKind = OData DataSourcePath = Request ID: 79d66fb6-27c3-9d1b-0f74-762e74e95a62.
2024-08-08 09:39:37,Autotask,Failed,AT Invoices,Part001,Completed,2024-08-08 09:39:37,2024-08-08 09:39:46,00:00:09.1410,NA,375,74136,00:00:03.4530,00:00:00.1910,Not used,NA
2024-08-08 09:39:37,Autotask,Failed,AT Projects,Part001,Completed,2024-08-08 09:39:37,2024-08-08 09:39:46,00:00:08.9840,NA,333,78656,00:00:02.7660,00:00:00.3980,Not used,NA
"

It is like as if that the dataflow does not send any requests.

7

Are you sure you are looking at the requests for the user that is used on the report? I do see some requests on other users within your organization.

8

We checked the log with both users but don’t see any difference in the log.

9

As what my colleague said, we cant see any difference in the logs for both users from our side. Nonetheless, the dataflow is still failing and we are not getting any new data.

Could you please advise ?

10

In order to diagnose any problems we do need some information about the endpoint called, the time the request has been made, etc. If you can supply that information we can analyse the issue.

As stated in a previous comment, it would be very helpful to get the failing request information from Bridge Online monitoring. From the monitoring I can only see requests failing due to a timeout, which probably means some settings could be added to the report to prevent that from happening. More on possible solutions fixing timout issues can be found here: Avoid timeout error on Power BI OData download.

11

I just got this from the system messages:

afbeelding
afbeelding1719×792 130 KB

itgenboe147
Non-displayed Bridge Online HTTP 500 server error. The data download was cancelled after 9 minutes, 51 seconds, probably due to a missing or incorrectly configured timeout in the Power BI or Power Query query.
Make sure to manually configure a sufficiently high timeout on the OData-feed as described on Avoid timeout error on Power BI OData download - invantive.
Please optimize your query as described on Overview of Power BI Performance and Download Size Improvement Techniques - invantive.
Then re-run the query.

URL: */odata4/Autotask.Tickets.Tickets@at?$select=...

Additionally, it is one table that causes the timeout the ticket table. We also collect this table using the method recommended by you.

 Bron = OData.Feed("https://bridge-online.cloud/3279/odata4/", null, [Implementation="2.0", Timeout=#duration(0,4,0,0)]),
12

Yet, it still does the timeout for the “Ticket” table after applying what was recommended.

13

It looks like Power BI doesn’t abide the timeout provided to the report, something we have seen more recently. We are not sure what the reason is. Since the Tickets table can be huge, it may take some time to download all data.

How many rows do you expect the query to return?

If possible, apply filtering to the table so the download runs quicker. Even with the timeout not being applied, a few runs might fill up the cache enough to make it within the 10 minutes.

Meanwhile we will try to see if we can find anything on this subject.

14

Please note that it is recommended to also make some additional changes to the OData-download to reduce traffic using null-compression as shown in:

15

This question was automatically closed after at least 1 week of inactivity after a possible solution was provided. The last answer given has been marked as a solution.

Please ask a new question via a separate topic if the problem occurs again. Please include a link to this topic in the new question by pasting its URL into the text.

16

Dit topic is 3 dagen na het laatste antwoord automatisch gesloten. Nieuwe antwoorden zijn niet meer toegestaan.