none
Power Query is crashing Excel RRS feed

  • Question

  • I have reinstalled and repaired my office and power query several times now.   When ever I open a file that is using power query it crashes with no error message.  There are no messages in my event viewer either.  If I create a blank document and then try to import data from file using power query, excel crashes.    I did have PowerBI Designer installed, but it is now uninstalled.  Any idea as to what the issue can be?
    Monday, August 24, 2015 9:43 PM

Answers

  • Ok, lets see if PQ is starting up enough to get any tracing. Can you try this

    • Find this registry value: [HKEY_CURRENT_USER\Software\Microsoft\Microsoft Power Query for Excel]
    • Set TracingEnabled = 1 (REG_DWORD)
    • Note: Traces (log files) will be saved under the path %LOCALAPPDATA%\Microsoft\Power Query\Traces
    • Please remember to set TracingEnabled = 0 when you wish to disable traces

    Friday, September 4, 2015 4:10 PM
  • I had Malware on my machine, and after wiping my machine everything is working again.  However, I suspect the malware had infected SilverLight because Power Query apparently uses it.
    • Marked as answer by CWFCleber Monday, September 14, 2015 8:38 PM
    Monday, September 14, 2015 8:36 PM

All replies

  • What version and bitness (32bit or 64bit) of Office are you running?
    Tuesday, August 25, 2015 12:24 AM
  • I Have the same problem, I'm using 32bits version under windows 8.1 pro with 8GB RAM

    I get an error

    Error Message:

    Exception of type 'System.OutOfMemoryException' was thrown.

    Stack Trace:

    System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
       at System.Text.StringBuilder.ExpandByABlock(Int32 minBlockCharCount)
       at System.Text.StringBuilder.Append(Char* value, Int32 valueCount)
       at System.Text.StringBuilder.Append(String value, Int32 startIndex, Int32 count)
       at Microsoft.Mashup.Evaluator.Package.ApplyEdits(String source, IEnumerable`1 orderedEdits)
       at Microsoft.Mashup.Evaluator.EditsPackageSection.get_Text()
       at Microsoft.Mashup.Evaluator.TranslateSourceLocationPackageSection.get_Text()
       at Microsoft.Mashup.Evaluator.IPackageSerializationExtensions.WriteIPackageSection(BinaryWriter writer, IPackageSection section)
       at Microsoft.Mashup.Evaluator.IPackageSerializationExtensions.WriteIPackage(BinaryWriter writer, IPackage package)
       at Microsoft.Mashup.Evaluator.RemoteDocumentEvaluator.BeginGetResultMessage.Serialize(BinaryWriter writer)
       at Microsoft.Mashup.Evaluator.BinarySerializer.Serialize(Action`1 serializer)
       at Microsoft.Mashup.Evaluator.Interface.BufferedMessage.Prepare()
       at Microsoft.Mashup.Evaluator.ChannelMessenger.Post(MessageChannel channel, Message message)
       at Microsoft.Mashup.Evaluator.ChannelMessenger.MessageChannel.Post(Message message)
       at Microsoft.Mashup.Evaluator.RemoteDocumentEvaluator.PreviewValueSourceRemoteEvaluation.GetResult(Boolean enableFirewall)
       at Microsoft.Mashup.Evaluator.RemoteDocumentEvaluator.EvaluationThread(Object state)
       at Microsoft.Mashup.Evaluator.GlobalizedThreadPool.<>c__DisplayClass1.<QueueUserWorkItem>b__0(Object s)
       at Microsoft.Mashup.Evaluator.SafeThread2.<>c__DisplayClassa.<CreateWaitCallback>b__8(Object o)
       at Microsoft.Mashup.Evaluator.SafeThread2.<>c__DisplayClass15.<CreateAction>b__14(Object o)

    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.ErrorDetails..ctor(String message, Nullable`1 errorCode, String requestId, Exception exception)
       at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.<>c__DisplayClass1.<HandleException>b__0()
       at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
       at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.<>c__DisplayClass9.<Send>b__7(Object null)
       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.Reflection.RuntimeMethodInfo.UnsafeInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       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.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.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.Application.ThreadContext.LocalModalMessageLoop(Form form)
       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.Application.RunDialog(Form form)
       at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
       at System.Windows.Forms.Form.ShowDialog()
       at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
       at Microsoft.Mashup.Client.ClientShared.BasicExceptionHandler.HandleException(Exception e)
       at Microsoft.Mashup.Client.ClientShared.PluggableProtocolManager.PluggableProtocol.Read(IntPtr pv, UInt32 cb, UInt32& pcbRead)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
       at System.Windows.Forms.Application.ThreadContext.LocalModalMessageLoop(Form form)
       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.Application.RunDialog(Form form)
       at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
       at Microsoft.Mashup.Client.ClientShared.WindowManager.ShowDialog[T](T form, IWin32Window owner)
       at Microsoft.Mashup.Client.ClientShared.Ux.FloatingDialog.SimpleDialog.UnexpectedErrorDialog.Show(IWin32Window owner, WindowsHost windowsHost, ErrorDetails errorDetails, PackageReference sourcePackageReference, Boolean displayOnTop)
       at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.<>c__DisplayClass1.<HandleException>b__0()
       at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.Send(SynchronizationContext context, IExceptionHandler exceptionHandler, Action callback)
       at Microsoft.Mashup.Client.ClientShared.UnexpectedExceptionHandler.HandleException(Exception e)
       at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
       at Microsoft.Mashup.Client.Excel.FillManager.OnFillUpdateTimerTick(Object sender, EventArgs eventArgs)
       at System.Windows.Forms.Timer.OnTick(EventArgs e)
       at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    Tuesday, August 25, 2015 2:34 AM
  • This is a bit of a different issue. The issue is caused by the data no fitting into the process memory of the 32bit process. If you can change to use the 64bit version of office this out of memory error will go away.
    Tuesday, August 25, 2015 2:58 AM
  • Hi, thanks for quickly answer, how can I change my office 365 suscriptio to 64 bits?

    Why I didn't get an error before?

    Thanks

    Tuesday, August 25, 2015 3:01 AM
    • Marked as answer by CWFCleber Tuesday, August 25, 2015 2:51 PM
    • Unmarked as answer by CWFCleber Tuesday, August 25, 2015 2:51 PM
    Tuesday, August 25, 2015 3:05 AM
  • 2013 (Office 365) 32 bit on windows 7

    • Edited by CWFCleber Tuesday, August 25, 2015 12:35 PM
    Tuesday, August 25, 2015 12:34 PM
  • Can you please give me the office version too?
    Tuesday, August 25, 2015 2:50 PM
  • 2013 (Office 365) 32-bit
    Tuesday, August 25, 2015 2:52 PM
  • Thanks, I didn't understand why before it works, and why not with the new version of Power Query. I had to update/change my Office 365 from 32 bits to 64 bits, now works, but cannot use my 32bit version of Project!!! :-(

    Tuesday, August 25, 2015 3:02 PM
  • Ok, can you try this.

    1. Uninstall PowerQuery

    2. Repair Office

    3. Install PowerQuery

    Tuesday, August 25, 2015 5:44 PM
  • No change, still crashes with no error message when trying to use Power Query on an existing or new file
    Tuesday, August 25, 2015 6:02 PM
  • Any other ideas?
    Thursday, August 27, 2015 2:26 PM
  • Yes, very sorry about the delay.  Can you try this to see if we can get a crash dump

    • Edit the registry and add the
           key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error
           Reporting\LocalDumps”
    • Reproduce the crash
    • Look under
           %LOCALAPPDATA%\CrashDumps for any crash dumps.


    Thursday, August 27, 2015 3:55 PM
  • Hmmm, maybe I must not understand or I am not doing something correct.   I went to the registry entry there and added DumpType = 2

    Reproduced the error, and went to the location and found nothing.  I even restarted my computer, and tried again, and still no crash dump.


    Tuesday, September 1, 2015 6:36 PM
  • Ok, thought that may happen, in that case can you try this instead

    • Edit the registry, open the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting and change the DWORD value ForceQueue to 1
    • Open %LOCALAPPDATA%\Microsoft\Windows\WER\ReportQueue in Windows Explorer to monitor it
    • Reproduce the crash – at this point something should appear briefly in the ReportQueue folder

    Tuesday, September 1, 2015 7:59 PM
  • I added the registry entry, reproduced, and got nothing in the new location.
    Wednesday, September 2, 2015 1:23 PM
  • Argghh, sorry, hope you are not frustrated.  I am checking with folks on some other way to get a crash dump.  Thank you for your patience.
    Wednesday, September 2, 2015 11:25 PM
  • Are you seeing any entries in the event log now?  Also is there any kind of error message, or is it just disappearing?
    Thursday, September 3, 2015 8:30 PM
  • I looked through the event log and nothing popped out as being remotely related to office. I am not getting an error message, the screen disappears when it tries to load a file with power query stuff in it.  I had systematically disabled add-ins until I found that it was the power query add-in.
    Friday, September 4, 2015 1:49 PM
  • Ok, lets see if PQ is starting up enough to get any tracing. Can you try this

    • Find this registry value: [HKEY_CURRENT_USER\Software\Microsoft\Microsoft Power Query for Excel]
    • Set TracingEnabled = 1 (REG_DWORD)
    • Note: Traces (log files) will be saved under the path %LOCALAPPDATA%\Microsoft\Power Query\Traces
    • Please remember to set TracingEnabled = 0 when you wish to disable traces

    Friday, September 4, 2015 4:10 PM
  • I had Malware on my machine, and after wiping my machine everything is working again.  However, I suspect the malware had infected SilverLight because Power Query apparently uses it.
    • Marked as answer by CWFCleber Monday, September 14, 2015 8:38 PM
    Monday, September 14, 2015 8:36 PM
  • So glad to hear that it is working for you!
    Monday, September 14, 2015 8:45 PM