Each data refresh gives different data results

[Anonymous]

Hello,

I created a .PBIX file with a model and it has been working correctly for 3 months. Data sources are SQL Server 2014 and some Excel worksheets.

After updating Power BI Desktop to the latest version, everytime I refresh the data it gives different results and they are always wrong.

I have checked all the queries and the relations between tables and there have been no changes. I have also carried out tests on the data sources with SQL Management Studio and everything is correct.

Everything would suggest that Power BI imports a different number of rows at each refresh (even when I press the refresh button every few seconds), but the table contains always the same (correct) number of rows. It seems that the error is an issue that involves only the Reports.

What could be the reason?

Thank you for any help.

[InaNortje]

Hi @lizrowden, @Anonymous

Below is a link describing the full details of the issue that I had, and how I finally resolved it. 

The conditions under which it occurred are:

 - High volume source data 

 - Subsequent merge

(note: the query doesn't neccessarily have to return high volume data.  It's the source table size that seems to determine this)

https://community.powerbi.com/t5/Issues/Power-Query-Merge-yields-inconsistent-results/idi-p/119485

The easiest fix was to add an explicit "order by" clause to my source query.

Hope this helps

Ina

[Anonymous]

@v-micsh-msft Yes, I have installed the 2.38.4491.282 version.

I have enabled the trace and I have refreshed the data, in the traces I found these 3 Errors:

Error 1: EvaluationContainerMain/ExceptionHandler/HandleException,"Exception:
ExceptionType: System.Threading.AbandonedMutexException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message: The wait completed due to an abandoned mutex.
StackTrace:
at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
at Microsoft.Mashup.Container.EvaluationContainerMain.WaitForParentExitThread(Object state)
at Microsoft.Mashup.Evaluator.SafeThread2.<>c__DisplayClass15.<CreateAction>b__14(Object o)"

Error 2: EvaluationContainerMain/ExceptionHandler/HandleException,"Exception:
ExceptionType: System.IO.EndOfStreamException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message: Unable to read beyond the end of the stream.
StackTrace:
at System.IO.BinaryReader.FillBuffer(Int32 numBytes)
at System.IO.BinaryReader.ReadInt32()
at Microsoft.Mashup.Evaluator.StreamMessenger.Read()
at Microsoft.Mashup.Evaluator.ChannelMessenger.Read(MessageChannel channel)
at Microsoft.Mashup.Evaluator.ChannelMessenger.MessageChannel.Read()
at Microsoft.Mashup.Evaluator.Interface.IMessengerExtensions.WaitFor[T](IMessenger messenger, Action`2 handler)
at Microsoft.Mashup.Evaluator.RemoteServiceEnvironment.CreateServiceProxies(IMessenger messenger, IRemoteServiceProxy[]& services)
at Microsoft.Mashup.Evaluator.EvaluationHost.Run()
at Microsoft.Mashup.Container.EvaluationContainerMain.Run(Object args)
at Microsoft.Mashup.Evaluator.SafeThread2.<>c__DisplayClass15.<CreateAction>b__14(Object o)"

Error 3: EvaluationContainerMain/ExceptionHandler/HandleException,"Exception:
ExceptionType: System.Threading.AbandonedMutexException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message: The wait completed due to an abandoned mutex.
StackTrace:
at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
at Microsoft.Mashup.Container.EvaluationContainerMain.WaitForParentExitThread(Object state)
at Microsoft.Mashup.Evaluator.SafeThread2.<>c__DisplayClass15.<CreateAction>b__14(Object o)"

Anyone has any suggestions? Thank you

[v-micsh-msft]

Hi zikas,

mscorlib is one of the conponment of .Net Framework, any changes has been made regarding .Net framework? Take a repair or a re-install of .Net Framework on your system.

In addition, could you please share the full log here?

Regards

[BhaveshPatel]

I would suggest you to use older versions of PowerBI and see if the issue persists. 

You can also send the snapshots of your data to microsoft for further analysis.