Forum Discussion
Gateway Performance Monitoring PBIT Dataformat error
Just upgraded to the latest version of the Enterprise gateway across our cluster and pulled up the GatewayPerformanceMonitoring.pbit that we've used previously in the past. All of a sudden now when it attempts to read two of the tables QueryExecutionReport and DataError we get an error stating:
I've experienced the same - I believe this is a regression in the April 2020 version of Power BI Desktop not the Gateway. You'll find it works ok with March 2020. I've reported it here - https://community.powerbi.com/t5/Issues/April-2020-throwing-DataFormat-Error-when-using-Gateway/idi-p/1080336
8 Replies
I've experienced the same - I believe this is a regression in the April 2020 version of Power BI Desktop not the Gateway. You'll find it works ok with March 2020. I've reported it here - https://community.powerbi.com/t5/Issues/April-2020-throwing-DataFormat-Error-when-using-Gateway/idi-p/1080336
Hey Anonymous It looks as though the May 2020 release fixed the issue.
I'm having the same issue and I'm running the May 2020 update of Power BI desktop.
Looking at the log files produced by the latest version of the gateway (3000.40.15 (May 2020)) I can see that entries with QueryType equal to "Refresh" often have one or two extra values between the "DataReadingAndSerializationDuration(ms)" and "DataProcessingEndTimeUTC" columns.
Below is a screenshot of a QueryExecutionReport log file pulled into Excel. I performed a Text to Data operation using a comma as the delimiter. Manual inspection of the log file also shows that these rows have more columns than they should.
Looks like the logging of Refresh queries in this version of the gateway is not performing to spec.
Unfortunately, the same error is showing up now. We updated the gateway to the version from October 2021 and now, after connecting to the generated logs, the following error appears: DataFormat.Error: There were more columns in the result than expected.
