Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
I downloaded and installed the Power BI Desktop app last night but am unable to load data into it. The example error below is from attempting to load a small .csv file. I get similar errors regardless of the type of data source I use. I do see errors in the event log regarding MSOLAP$AnalysisServicesWorkspace but have not found anything referencing this error either. Any suggestions? Any pre-req that might not be getting checked by the installer?
Error Message:
Cannot create process.
Stack Trace:
Microsoft.Mashup.Evaluator.Interface.ErrorException: Cannot create process. ---> Microsoft.Mashup.Evaluator.Interface.ErrorException: Cannot create process. ---> System.InvalidOperationException: Cannot create process. ---> System.ComponentModel.Win32Exception: %1 is not a valid Win32 application
--- End of inner exception stack trace ---
at Microsoft.Mashup.Evaluator.ContainerProcess.Start()
at Microsoft.Mashup.Evaluator.ContainerFactory.Container..ctor(String exePath, String exitMutexName, Int32 containerId, Int32 maxWorkingSetInMB)
at Microsoft.Mashup.Evaluator.ContainerFactory.CreateContainer()
at Microsoft.Mashup.Evaluator.ContainerPoolContainerFactory.CreateContainer()
at Microsoft.Mashup.Evaluator.RemoteEvaluationContainerFactory.CreateContainer()
at Microsoft.Mashup.Evaluator.RemoteDocumentEvaluator.BeginGetResult[T](RemoteEvaluation`1 evaluation)
--- End of inner exception stack trace ---
at Microsoft.Mashup.Evaluator.RemoteDocumentEvaluator.BeginGetResult[T](RemoteEvaluation`1 evaluation)
at Microsoft.Mashup.Evaluator.LimitedDocumentEvaluatorFactory.Evaluation`1.BeginEvaluation()
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.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
--- End of inner exception stack trace ---
at Microsoft.Mashup.Host.Document.Analysis.PackageDocumentAnalysisInfo.PackagePartitionAnalysisInfo.SetPreviewValue(EvaluationResult2`1 result, Func`1 getStaleSince, Func`1 getSampled)
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.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 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.Mashup.Client.ClientShared.WindowManager.ShowDialog[T](T form, IWin32Window owner)
at Microsoft.PowerBI.Client.Program.<>c__DisplayClass8.<Main>b__1()
at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)
at Microsoft.PowerBI.Client.Program.Main(String[] args)
Solved! Go to Solution.
The root cause turns out to have been the presence of an unrelated file in the root of my C drive. I renamed the file I had called "Program", did a repair on Power BI desktop just to be sure, and then everything is working fine. It took a little longer than I would have liked but the MS Power BI team is definitely looking at the feedback they receive through the "send a frown" process.
What OS are you on?
Here is a similar issue with Power Query and the suggestion was to uninstall and reinstall.
I'm using Win 7 x64 Enterprise. I've just uninstalled power bi desktop, unistalled power query, re-downloaded BI desktop just to be sure, and then re-installed but the same issue exists.
Can you please use "Send a Frown" to report this?
I did that Sunday evening and heard from Minh on Tuesday morning. I very quickly answered the basic question on whether or not the error was reproduceable and will hopefully have a follow up soon.
Thanks,
Jason
The root cause turns out to have been the presence of an unrelated file in the root of my C drive. I renamed the file I had called "Program", did a repair on Power BI desktop just to be sure, and then everything is working fine. It took a little longer than I would have liked but the MS Power BI team is definitely looking at the feedback they receive through the "send a frown" process.
TigerDawg,
Where did u see this program file? I do not have any program file that i know of and have windows 7 enterprise 64 bit
Priyab,
The file with no extension, not a folder/directory, was right on the root of C, so C:\Program. I have no idea how it was created but removing it allowed Power BI to work normally.
Same problem but no file by that name on C drive. Microsoft really needs to step up their QA efforts before releasing new versions. This app is terribly buggy and I've recently told my senior management to suspend their dependency on the Power BI dashboards because apparenly it is not ready for a production environment.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
25 | |
12 | |
11 | |
11 | |
8 |
User | Count |
---|---|
45 | |
28 | |
14 | |
13 | |
13 |