Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
logiman
New Member

Unexpected Error - ModelManager is not running an expected transaction

I receive the above error message when trying to import a model built in Excel 2010.  I have the latest versions of power query and powerpivot.

 

The model has about 40 measures created with DAX formulas.

 

Prior to upgrading to this latest version of PBID, I successfully imported an earlier version of my model.  I am now unable to import that earlier version with this newest PBID.  For that matter, I'm not able to import any Excel 2010 model.

 

I have uninstalled and re-installed PBID and get the same error.

 

Any suggestions would be greatly appreciated.

 

Thanks!  Nick

1 ACCEPTED SOLUTION
foodd
Super User
Super User

As your last visit to the Community Forum was on 12/21/2015, and this post was added on 12-18-2015 12:04 PM, and there has been no additional feedback or interaction, the issue has been otherwise resolved, and this post may be closed.

View solution in original post

6 REPLIES 6
foodd
Super User
Super User

As your last visit to the Community Forum was on 12/21/2015, and this post was added on 12-18-2015 12:04 PM, and there has been no additional feedback or interaction, the issue has been otherwise resolved, and this post may be closed.

pqian
Microsoft Employee
Microsoft Employee

Can you send a frown from the unexpected error dialog, we can follow up from there. Thanks!

Yes.  I sent a frown when I received the initial error.

 

As info, the error detail is below.  Thanks!!!!

 

Error Message:

ModelManager is not running an expected transaction.

Stack Trace:

System.InvalidOperationException: ModelManager is not running an expected transaction.
at Microsoft.PowerBI.Modeler.Relationships.DeleteRelationshipCore(SingleColumnRelationship relationship)
at Microsoft.PowerBI.Modeler.Relationships.DeleteRelationship(SingleColumnRelationship relationship)
at System.Collections.Generic.List`1.ForEach(Action`1 action)
at Microsoft.PowerBI.Modeler.Relationships.RemoveIf(Predicate`1 predicate)
at Microsoft.PowerBI.Modeler.TableSubsystem.DeleteTable(Table table, PartitionSubsystem partitionSubsystem)
at Microsoft.PowerBI.Modeler.ModelManager.DeleteTable(Table table)
at Microsoft.PowerBI.Client.Windows.Storage.BIPackageCreatorExcel.ConvertNonMQueries(List`1 listNonMQueries, AnalysisServicesLoadContextFactory analysisServicesLoadContextFactory, String newDatabaseName, BIPackage newBIPackage, Boolean maintainLinks, ImportFromExcelSummary resultSummary, CancellationToken cancellationToken, HashSet`1 outOfSyncQueries)
at Microsoft.PowerBI.Client.Windows.Storage.BIPackageCreatorExcel.TryCreateBIPackage(CancellationToken cancellationToken, IProgress`1 progressHandler, ZipPackageFileInfo fileInfo, Dictionary`2 linkedTableMapping, IImportFromExcelHost host, Dictionary`2 sharedStrings, BIPackage& newBIPackage, ImportFromExcelError& error, ImportFromExcelSummary& resultSummary, PackageValidationResult& validationResult, Boolean& tryImportEmbedded)
at Microsoft.PowerBI.Client.Windows.Storage.BIPackageCreatorExcel.<>c__DisplayClass1.<CreateBIPackageAsync>b__0()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Microsoft.PowerBI.Client.Windows.FloatingDialog.ImportFromExcelDialog.<<StartImport>b__6>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAsyncExceptions>d__0.MoveNext()

Invocation Stack Trace:

at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()
at Microsoft.Mashup.Client.ClientShared.StackTraceInfo..ctor(String exceptionStackTrace, String invocationStackTrace)
at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.<>c__DisplayClass1.<HandleException>b__0()
at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.HandleException(Exception e)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAsyncExceptions>d__0.MoveNext()
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.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
at System.Threading.Tasks.AwaitTaskContinuation.RunCallback(ContextCallback callback, Object state, Task& currentTask)
at System.Threading.Tasks.Task.FinishContinuations()
at System.Threading.Tasks.Task.Finish(Boolean bUserDelegateExecuted)
at System.Threading.Tasks.Task`1.TrySetException(Object exceptionObject)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.SetException(Exception exception)
at Microsoft.PowerBI.Client.Windows.FloatingDialog.ImportFromExcelDialog.<<StartImport>b__6>d__7.MoveNext()
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.Runtime.CompilerServices.AsyncMethodBuilderCore.MoveNextRunner.Run()
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
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.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at Microsoft.PowerBI.Client.Windows.MainWindow.ImportFromExcelFile(String filePath)
at Microsoft.Mashup.Client.Windows.Ribbon.RibbonCommandHandler.Execute(UInt32 commandId, CommandExecutionVerb verb, PropertyKeyRef keyRef, PropVariantRef currentValue, IUISimplePropertySet commandExecutionProperties)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at Microsoft.Mashup.Client.ClientShared.WindowManager.ShowDialog[T](T form, IWin32Window owner)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClassb.<Main>b__0()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.Main(String[] args)

 

pqian
Microsoft Employee
Microsoft Employee

Thanks, I'm looking.

 

When you said the latest version of Desktop, you mean the PBI Desktop December release right?

 

(http://blogs.msdn.com/b/powerbi/archive/2015/12/16/more-power-bi-feature-updates-power-bi-desktop-de...

 

Regards,

PQ

pqian
Microsoft Employee
Microsoft Employee

Hmmm...looks like a bug on our end 😞

 

We will track this and get it fixed. Thanks for reporting!

Yes.  PBI Desktop December release.  Thanks for researching!

Helpful resources

Announcements
July 2024 Power BI Update

Power BI Monthly Update - July 2024

Check out the July 2024 Power BI update to learn about new features.

July Newsletter

Fabric Community Update - July 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors