Forum Discussion
Power BI Desktop: Query Not Fully Loading
I am currently using the latest Power BI Desktop verison (July-2018) and noticed something odd. I am importing from a table from SQL and then using the power query editor to clean my data. Once the data is cleaned is shows about 400 records. I then proceed to Close and Load data and then only 13 records are available in table. When I refresh and flip back and forth between the query editor and the table in data view the number of records dont match.
I noticed this the other day with another report and after closing desktop and refreshing data a few times it just seemed to fix itself.
Anyone else notice this? I am concerned as my report that end users are using is not showing all records. Strangely the report has been refreshing daily without issue.
Could this be a bug with the July version?
All, after installing August desktop app AND August on-premises gateway, no more issues for me.
33 Replies
I stumbled upon this issue as well. It happened to me in two reports (identical in all aspects but some source tables for the data), one with ~25m records and the other with ~48m. Both reports import their data from SQL Server.
In an effort to find out what's causing it, I activated the tracing & crash dump logging options in the diagnostics settings, and came up with the following:
1. The source for the problem seems to be an issue with Microsoft.Mashup.Container.NetFX40 and/or Microsoft.Mashup.OleDbProvider.
2. When the issue occures, it is also logged to the windows application log. Some entries mentioned "OLE DB or ODBC error: Exception from HRESULT: 0x80040E4E", suggesting the connection to the server was cancelled.
3, Initially, I encountered some entries in one of the logs of which the specified action was "Engine/IO/Db/Microsoft SQL/ReportFoldingFailure".
4. Failing to find any useful info on the web, I decided it would not hurt to check if the issue was related to query folding. I therefore modified my queries so that query folding would not occur. It resulted in the issue being resolved in the smaller report, and replaced with new error in the larger one, with the following error message:
"Non-negative number required.
Parameter name: value"5. Inspecting the logs generated from the larger report, I found thousands of entries referring to a "FileSystemAccessHelper/TryIgnoringAccessExceptions" action. Most of the exceptions were of type System.IO.EndOfStreamException, but a few were of type System.IO.IOException, specifying some cached files could not be accesses because they're open by another process.
6. Realizing this problem is bigger than me, I decided to try and get around it by creating the final form of the data table on the SQL Server side, thus removing the heavy workload (Which was mostly merge operations) from the mashup engine. This resulted in a successful report refresh.
Basically, it seems like we got a faulty mashup engine with the July 2018 release.
itayrom, great minds think alike... I too, am "doing it on the database". Still, this issue is obviously not normal. Will post here if support comes up with a resolution.
Found an interesting tidbit while trying to see if the issue was somehow caused by me.
First thing I noticed is the number rows appended is equal to 5000 which I found weird.
I didn't pay much attention to it, but to make a long story short, I am appending 5 tables and thought maybe it only loads the first 1000.
I tested it and it does only pick up the first 1000 rows of each table.
Maybe someone more advanced can shed some light on why that is, I am just a beginner when it comes to this.
Thanks
My table-in-question is also loading exactly 1,000 rows... I notified the support contact I was working with and am awaiting a response.
I am experiencing this as well... I also have a query to load from SQL server and when refreshing from Desktop, only a few rows (from January 2016) are loaded. Went to query editor to troubleshoot, refreshed preview, and things seemed to go awry during a split column step. Refreshing preview while selecting this step loads random other dates. Weird.
Just thought to check O365 admin portal and found this... seems it's been an issue for several weeks:
Status:Service degradationUser impact:Users may see missing or incomplete data when refreshing reports, viewing reports or dashboards.Latest message:Title: Incomplete or missing data User Impact: Users may see missing or incomplete data when refreshing reports, viewing reports or dashboards. More info: Customers utilizing specific connectors when refreshing datasets without using native SQL queries, pulling SQL data that does not include a SQL primary key column in the final result, and doing Append or Merge operations may experience this issue. The following is a list of connectors impacted: SQL Server, Oracle, PostgreSQL, MySQL, Teradata, Sybase, Informix, DB2 or Access. Current status: We've initiated the deployment of the fix to the affected environment. We anticipate the deployment process completing by the end of this week. Scope of impact: Impact is specific to a subset of users who are served through the affected infrastructure. Start time: Friday, July 13, 2018, at 10:08 PM UTC Preliminary root cause: A recent update to the Power BI services resulted in missing or incomplete data when refreshing reports, viewing reports or dashboards in some scenarios. Next update by: Friday, August 3, 2018, at 7:00 PM UTCAny thoughts on a work-around for this issue. Like I mentioned in my post above, from Query Editor I should have around 400 transactions, but after Close & Applied I am left with only 13-14 transactions. Very strange. Not sure how to proceed at this point either.
