Nov Release Power Bi Desktop

Hi there,

I have the same issue with the November update.   Any help would be appreciated.

Seems to be on "imported data" rather than "direct query" for me.

Thanks

Richard

FYI: I have a backup copy of the October PowerBI Desktop file that I am restoring until the bug is addressed.

What a nightmare! Or it would be if I have slept last night.

Spent all night fixing crashes with the Nov release and desperately looking for the Oct release file.

And my server is unable to send emails, so no detailed report to their team. Very frustrating.

Hello,

Same issue here - upgraded to November release. Then got the Parameter Name: Key value cannot be null error.

I am having the same issue since installing the November update, but not with all .pbix files.

Getting the same issue on an imported model. Worked fine in October release now getting error:

Release:
November 2017

Product Version:
2.52.4921.461 (PBIDesktop) (x64)

Error Message:
Value cannot be null.
Parameter name: key

Stack Trace:
System.ArgumentNullException: Value cannot be null.
Parameter name: key

I am also getting the same error:

Feedback Type:
Frown (Error)

Timestamp:
2017-11-08T20:49:57.5695574Z

Local Time:
2017-11-08T12:49:57.5695574-08:00

Release:
November 2017

Product Version:
2.52.4921.461 (PBIDesktop) (x64)

Error Message:
Value cannot be null.
Parameter name: key

Stack Trace:
System.ArgumentNullException: Value cannot be null.
Parameter name: key

Server stack trace:
at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
at System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)
at Microsoft.PowerBI.Client.Windows.Modeling.PowerQueryToModelSchemaSynchronizer.EditTableInfoVisitor.<GenerateTableDefinitionChanges>d__9e.MoveNext()
at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection)
at Microsoft.PowerBI.Client.Windows.Modeling.PowerQueryToModelSchemaSynchronizer.EditExistingTable(ITableInput loadInput, EditTableInfo editTableInfo, FinalNameResults finalNamesResult)
at Microsoft.PowerBI.Client.Windows.Modeling.PowerQueryToModelSchemaSynchronizer.ApplyQuerySchemaToModel(IModelInput modelInput, IExtendedModelChangeScope modelChangeScope)
at Microsoft.PowerBI.Client.Windows.Modeling.PowerQueryToModelLoader.ApplyQueriesToModel(IAnalysisServicesLoadContext loadContext, IExtendedModelChangeScope modelChangeScope, Boolean& runRelationshipDetection, List`1& newTableColumnPairs)
at Microsoft.PowerBI.Client.Windows.Modeling.PowerQueryToModelLoader.ProcessLoadInputs(IExtendedModelChangeScope modelChangeScope, Action relationshipAutodetectStartCallback)
at Microsoft.PowerBI.Client.Windows.Modeling.PowerQueryToModelLoader.<>c__DisplayClass9.<PerformLoadInternal>b__7(IExtendedModelChangeScope modelChangeScope)
at Microsoft.PowerBI.Client.Windows.Modeling.AsyncModelAuthoringService.<>c__DisplayClassf.<RunExtendedModelChangeAsync>b__e()
at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
at System.Threading.Tasks.Task.Execute()

Exception rethrown at [0]:
at Microsoft.PowerBI.Client.Windows.Utilities.TaskExtensions.WaitAndUnpackException(Task task)
at Microsoft.PowerBI.Client.Windows.Modeling.PowerQueryToModelLoader.PerformLoadInternal(Action relationshipAutodetectStartCallback)
at Microsoft.PowerBI.Client.Windows.Modeling.PowerQueryToModelLoader.PerformLoad(Action relationshipAutodetectStartCallback)
at Microsoft.PowerBI.Client.Windows.Modeling.PowerQueryToModelLoader.<>c__DisplayClass1.<LoadTablesAsync>b__0(Object state)
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

OS Version:
Microsoft Windows NT 10.0.15063.0 (x64 en-US)

CLR Version:
4.7 or later [Release Number = 460798]

Peak Virtual Memory:
33.8 GB

Private Memory:
415 MB

Peak Working Set:
545 MB

IE Version:
11.674.15063.0

Workbook Package Info:
1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False.

Telemetry Enabled:
True

Model Default Mode:
Import

I'm getting the same issue.

I'm able to refresh individual data tables/queries , however while refreshing all the queries in the dataset show the same error message.

I'm able to refresh the dataset from PowerBI service as well, hence not a bigger bottleneck for me, however is quite an annoying bug, as I need to refresh quite a few queries.

Everyone is facing this issue after the NOV release update. Can anyone tell when this could be resolved..?

Regards,

PXG08680

Hi there

Same issue here - upgraded to November release. Then got the Parameter Name: Key value cannot be null error. Cannot refresh my reports.