Forum Discussion
Non-negative number required error while appending tables
Hi Anonymous,
Could you please show the Details message?
In addition, Please check if there is any negative number which is not expected in your value.
If you still need help, please share the dummy table structure of your tables, so that I could have test in my environment.
Best Regards,
Cherry
I am getting the same error.
I am running the exact same structure datasets (created duplicate and changed the date range in one of the datasets). When I refresh each of the datasets seperately, it refreshes with no issues, but when I am appending it, thats when I am coming across this issue. This is the first time I came across this. Does this have anything to do with the latest Power BI Desktop update?
Unexpected error: Non-negative number required.
Parameter name: value
Details:
Microsoft.Mashup.Evaluator.Interface.ErrorException: Non-negative number required.
Parameter name: value ---> System.ArgumentOutOfRangeException: Non-negative number required.
Parameter name: value ---> System.ArgumentOutOfRangeException: Non-negative number required.
Parameter name: value
at System.IO.FileStream.set_Position(Int64 value)
at Microsoft.Mashup.EngineHost.Services.StreamSharer.MoveTo(SubStream subStream, Int64 position)
at Microsoft.Mashup.EngineHost.Services.StreamSharer.ReadAt(SubStream subStream, Int64 position, Byte[] buffer, Int32 offset, Int32 count)
at Microsoft.Mashup.EngineHost.Services.StreamSharer.SubStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
at Microsoft.Mashup.EngineHost.Services.TransformingPagedStream.ReadPage(Int32 page, Byte[] buffer)
at Microsoft.Mashup.EngineHost.Services.PagedStream.SeekToPage(Int32 page)
at Microsoft.Mashup.EngineHost.Services.PagedStream.Write(Byte[] array, Int32 offset, Int32 count)
at Microsoft.Mashup.EngineHost.Services.WriteBehindPersistentCache.AsyncCommitStorage(String key, TemporaryStorage storage)
at Microsoft.Mashup.EngineHost.Services.WriteBehindPersistentCache.AsyncCommitStorage(Object obj)
at Microsoft.Mashup.Evaluator.EvaluatorThreadPool.EvaluatorThread(Object state)
at Microsoft.Mashup.Evaluator.SafeThread2.<>c__DisplayClass15.<CreateAction>b__14(Object o)
--- End of inner exception stack trace ---
at Microsoft.Mashup.Evaluator.EvaluationHost.<>c__DisplayClass7.<TryReportException>b__6()
at Microsoft.Mashup.Common.SafeExceptions.IgnoreSafeExceptions(IEngineHost host, IHostTrace trace, Action action)
at Microsoft.Mashup.Evaluator.EvaluationHost.TryReportException(IHostTrace trace, IEngineHost engineHost, IMessageChannel channel, Exception exception)
at Microsoft.Mashup.Evaluator.EvaluationHost.TryHandleException(Exception exception)
at Microsoft.Mashup.Evaluator.SafeThread2.HandleException(Exception e)
at Microsoft.Mashup.Evaluator.SafeThread2.<>c__DisplayClass15.<CreateAction>b__14(Object o)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)
--- End of inner exception stack trace ---
at Microsoft.Mashup.Evaluator.EvaluationHost.OnException(IEngineHost engineHost, IMessageChannel channel, ExceptionMessage message)
at Microsoft.Mashup.Evaluator.MessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.ChannelMessenger.ChannelMessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.ChannelMessenger.OnMessageWithUnknownChannel(IMessageChannel baseChannel, MessageWithUnknownChannel messageWithUnknownChannel)
at Microsoft.Mashup.Evaluator.MessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.ChannelMessenger.ChannelMessageHandlers.TryDispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.MessageHandlers.Dispatch(IMessageChannel channel, Message message)
at Microsoft.Mashup.Evaluator.Interface.IMessageChannelExtensions.WaitFor[T](IMessageChannel channel)
at Microsoft.Mashup.Evaluator.RemotePreviewValueSource.PreviewValueSource.WaitFor(Func`1 condition, Boolean disposing)
at Microsoft.Mashup.Evaluator.RemotePreviewValueSource.PreviewValueSource.get_SmallValue()
at Microsoft.Mashup.Evaluator.Interface.TracingPreviewValueSource.get_SmallValue()
at Microsoft.Mashup.Host.Document.Analysis.PackageDocumentAnalysisInfo.PackagePartitionAnalysisInfo.SetPreviewValue(EvaluationResult2`1 result, Func`1 getStaleSince, Func`1 getSampled)
Would anybody know how to resolve this issue?
I am experiencing the same error when refreshing my dataset, however this dataset has been refreshing without issue for over a year. I just updated to the August PowerBI yesterday and this is the first time I've tried refreshing it with the new update (I was using the July 2018 version previously).
I'm also running into a further issue where I can't select the window after the failure and have to kill the task in task manager. It's acting as though there is an extra window open when the failure occurs while I don't have the query editor open, but I can't actually see any extra windows and tabbing between available windows does not show any options available ot me.
If I trigger the failure while query editor is open I get the large failure block that looks very similar if not the same to the one pasted in the comments above.
