Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Get Fabric certified for FREE! Don't miss your chance! Learn more

Goofr

Power BI Dataflow refresh fail

Submitted by Advocate IV on ‎09-18-2019 12:21 AM

Hi,

 

Since this morning GMT time our dataflows don't get refreshed anymore.

No scheduled or manual refresh possible.

 

Internal error Request ID: 52ff8d68-06f2-b9af-c457-7c8d24ec5af1 Activity ID: 69c0d3af-4b0b-472a-8ece-11e8dcbdc30f

 

Any ideas?

Thanks

Frank

Status: New
See more ideas labeled with:
15 Comments (15 New)
Comments
theeri01
New Member
‎09-18-2019 10:15 AM

Hi

 

Same issue here.  My setup is on-premise data gateway on windows 2012 r2. This issue appears with latest windows update. I remove all update previously instaled and my on premisse gateway was able to communicate outside. 

(KB4019213)
(KB4498963)
(KB4503290)
(KB4507422)
(KB4507457)
(KB4511872)
(KB4512488)
(KB4512489)
(KB4012213)
(KB3092601)
(KB3048043)
(KB3132080)

 

the on-premisse data gateway is version 3000.8.452.

 

Hope someone found something, dont like to keep my server with security issue !

 

Eric

v-qiuyu-msft
Community Support
Community Support
‎09-18-2019 08:23 PM

Hi all, 

 

Is there any error message occurs when you refresh dataflows? Please go to Refresh History and provide detail information for us. 

 

Best Regards,
Qiuyun Yu 

mpe
Frequent Visitor
‎09-19-2019 01:21 PM

I have the same issues. The dataflow stops after a few seconds with refreshing.

v-qiuyu-msft
Community Support
Community Support
‎09-19-2019 11:24 PM

@DebbieE It seems your issue is related to a dataset refresh rather than dataflow refresh. Please create a new thread with detail information provided. 

 

@mpe What's the error message pops out? Please share detail error information with us. 

 

Best Regards,
Qiuyun Yu 

mpe
Frequent Visitor
‎09-20-2019 04:49 AM

These are the messages from two dataflows. The first one was updated on 18-9, but failed to update since then. The second one failed on 18/9 in the morning, but was able to update again in the evening of 18/9. It has worked since then.

Invalid date,Verdi Data Phalaenopsis,Mislukt,Verdi Basispool,20/09/2019 13:00:01,20/09/2019 13:00:35,Mislukt,Error: The key didn't match any rows in the table. Request ID: d9ba3168-59fd-470a-9cb7-7fe6f9a0eb76 Activity ID: 8a23b58a-bdeb-42bc-b52d-741adee67ce5

 

Invalid date,tabellen PhalBreed,Mislukt,TrialData,18/09/2019 11:10:24,18/09/2019 11:10:25,Mislukt,Error: Internal error Request ID: 89f25160-f236-98f1-2f4e-4ce3c78056f8 Activity ID: cc6d0ca5-a9cb-44d6-bd18-5e1d33cbbefc
Invalid date,tabellen PhalBreed,Mislukt,Jobs,18/09/2019 11:10:25,18/09/2019 11:10:26,Mislukt,Error: Internal error Request ID: 89f25160-f236-98f1-2f4e-4ce3c78056f8 Activity ID: 75e74ec1-7dc4-4673-afd8-3f7c5c57d79e
Invalid date,tabellen PhalBreed,Mislukt,Items,18/09/2019 11:10:26,18/09/2019 11:10:27,Mislukt,Error: Internal error Request ID: 89f25160-f236-98f1-2f4e-4ce3c78056f8 Activity ID: 326ced92-1a1e-4dd6-8248-923b7a95805e
Invalid date,tabellen PhalBreed,Mislukt,Properties Progeno,18/09/2019 11:10:27,18/09/2019 11:10:29,Mislukt,Error: Internal error Request ID: 89f25160-f236-98f1-2f4e-4ce3c78056f8 Activity ID: a51778be-f310-454a-bd20-a835cae1df11
Invalid date,tabellen PhalBreed,Mislukt,Hybrid table Crossings,18/09/2019 11:10:29,18/09/2019 11:10:30,Mislukt,Error: Internal error Request ID: 89f25160-f236-98f1-2f4e-4ce3c78056f8 Activity ID: 69232659-fb49-406e-a620-dea5eb9635fc
Invalid date,tabellen PhalBreed,Mislukt,Nakomelingen,18/09/2019 11:10:30,18/09/2019 11:10:31,Mislukt,Error: Internal error Request ID: 89f25160-f236-98f1-2f4e-4ce3c78056f8 Activity ID: 17c64840-c0c3-43dd-a9f0-53c252a33997
Invalid date,tabellen PhalBreed,Mislukt,Crossings,18/09/2019 11:10:31,18/09/2019 11:10:32,Mislukt,Error: Internal error Request ID: 89f25160-f236-98f1-2f4e-4ce3c78056f8 Activity ID: 1a2b6c31-edd8-446f-acf9-2bf749f181b7
Invalid date,tabellen PhalBreed,Mislukt,Seedling pop,18/09/2019 11:10:32,18/09/2019 11:10:33,Mislukt,Error: Internal error Request ID: 89f25160-f236-98f1-2f4e-4ce3c78056f8 Activity ID: 92ad95e7-c92f-4efa-b155-6aafb5ab7396
Invalid date,tabellen PhalBreed,Mislukt,Jobs in lab,18/09/2019 11:10:33,18/09/2019 11:10:34,Mislukt,Error: Internal error Request ID: 89f25160-f236-98f1-2f4e-4ce3c78056f8 Activity ID: 9056f5e6-2abf-4484-bf5d-3a3f8b16f643
Invalid date,tabellen PhalBreed,Mislukt,Properties AW Item,18/09/2019 11:10:34,18/09/2019 11:10:35,Mislukt,Error: Internal error Request ID: 89f25160-f236-98f1-2f4e-4ce3c78056f8 Activity ID: ac2e78cb-78f7-44d1-83c5-6abb500e4513
Goofr
Advocate IV
Advocate IV
‎09-20-2019 06:24 AM

Hi,

 

I had the same error.

Ended up recreating all dataflows (copy paste form the broken one) and updating all my reports.
One day of work..

 

BI-Geniuz
Advocate I
Advocate I
‎09-23-2019 02:16 AM

any updates on this matter? I'm experiencing the same issue since 19-09-2019 as well.

mpe
Frequent Visitor
‎09-23-2019 02:38 AM

I did some rework on one of the dataflows. It concerned an ODBC data source. After changing the code (shortening) it workes again.

 

Has there been an update in the dataflows on working with ODBC data sources?

BI-Geniuz
Advocate I
Advocate I
‎09-23-2019 03:11 AM

Hi,

 

@mpe thanks for your response. I'm working with ODBC as well. Can you show some of the modding you've done in the syntax ?

mpe
Frequent Visitor
‎09-23-2019 05:25 AM

@BI-Geniuz There were three lines describing which table I needed from the ODBC source.

 

let
Source = Odbc.DataSource("dsn=xxx"),
v_ant_anth_prd_Database = Source{[Name = "xx", Kind = "Database"]}[Data],
informix_Schema = v_ant_anth_prd_Database{[Name = "x", Kind = "Schema"]}[Data],
basispool_Table = informix_Schema{[Name = "xxxx", Kind = "Table"]}[Data]
 
I have changed it to one line
 
let
Source = Odbc.DataSource("dsn=xxx"),
Navigate = Source{[Item = "xxxx", Schema = "x", Catalog = "xx"]}[Data],
Idea Statuses